code-audit
/code-audit
Use when reviewing or asked to review code quality, a codebase or pasted code for DevOps readiness, security issues and missing best practices (secrets, containers, Kubernetes, CI/CD, IaC, observability)
- Author
- nikospavlopoulos ↗
- Repository
- devops-mutant-powers ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when reviewing or asked to review code quality, a codebase or pasted code for DevOps readiness, security issues and missing best practices (secrets, containers, Kubernetes, CI/CD, IaC, observability)
Original author description
Use when reviewing or asked to review code quality, a codebase or pasted code for DevOps readiness, security issues and missing best practices (secrets, containers, Kubernetes, CI/CD, IaC, observability)
How it works
- Works In Both Modes
- Audit Categories
- Reporting Format
SKILL.md preview
--- name: code-audit description: Use when reviewing or asked to review code quality, a codebase or pasted code for DevOps readiness, security issues and missing best practices (secrets, containers, Kubernetes, CI/CD, IaC, observability) --- # Code Audit ## Works In Both Modes - **Repo mode** — scan actual files in the working directory - **Chat mode** — audit pasted code snippets or configs ## Audit Categories Run through each category. Report findings as: **CRITICAL**, **WARNING**, or **INFO**. --- ### 1. Secrets & Security - [ ] Hardcoded API keys, passwords, tokens, or credentials in code - [ ] `.env` files committed to git (check `.gitignore`) - [ ] Secrets passed as plain environment variables in CI configs - [ ] Insecure base images (e.g., `FROM ubuntu:latest` without pinned version) - [ ] Running containers as root when not needed - [ ] World-readable file permissions on sensitive configs ### 2. Container Readiness - [ ] Dockerfile present - [ ] `.dockerignore` present (prevents leaking local files into image) - [ ] Base image pinned to a specific version (not `latest`) - [ ] Multi-stage build used to minimize final image size - [ ] Health check defined (`HEALTHCHECK` in Dockerfile or K8s `livenessProbe`) - [ ] Non-root user defined in Dockerfile ### 3. Kubernetes / Orchestration - [ ] Resource `requests` and `limits` set for CPU and memory - [ ] `livenessProbe` and `readinessProbe` defined - [ ] `replicas` > 1 for production workloads - [ ] Namespace defined (not running in `default`) - [ ] Secrets stored in K8s Secrets, not ConfigMaps - [ ] `imagePullPolicy: Always` for mutable tags ### 4. CI/CD - [ ] CI config present (`.github/workflows/`, `.gitlab-ci.yml`, `Jenkinsfile`) - [ ] Tests run in CI before deploy - [ ] Linting/formatting check in CI - [ ] Secrets injected via CI secret store, not hardcoded - [ ] Deployment gated on test pass ### 5. Infrastructure as Code - [ ] IaC files present (Terraform, Ansible, Pulumi, etc.) - [ ] State backend configured (not local state for production) - [ ] Variables used instead of hardcoded values - [ ] Least-privilege IAM/RBAC roles - [ ] Resource tagging for cost tracking ### 6. Observability - [ ] Application logs written to stdout/stderr (not to files inside container) - [ ] Structured logging (JSON preferred) - [ ] Health check endpoint exposed (`/health`, `/ready`) - [ ] Metrics endpoint exposed if applicable (`/metrics`) --- ## Reporting Format For each finding: ``` [SEVERITY] Category — Description File: path/to/file (or "pasted code") Why it matters: ... Fix: ... ``` End with a summary count: X critical, Y warnings, Z info items.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · nikospavlopoulos/devops-mutant-powers | 100 | MIT |
| Nubaeon/empirica | 100 | MIT |
| EpicenterHQ/epicenter | 100 | MIT |
| tspry/superpowers-devops | 100 | MIT |
| glnds/glnds-cc-marketplace | 100 | Apache-2.0 |
| omexit/claude-skills-pack | 100 | MIT |
| JasonAiassist/public-skills | 100 | MIT |
| zhaoxuya520/reverse-skill | 100 | MIT |
| arcasilesgroup/ai-engineering | 90 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version 044a0b06aaae (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100infrastructure-coder
Infrastructure-as-Code: Terraform, Kubernetes, Docker. Generate, review, cost-compare, security-scan. Use for IaC work. NOT for CI/CD (devops-engineer), application code, or actual pricing. - 90devops-cloud
Design, implement, secure, and operate cloud infrastructure and delivery pipelines. Use for CI/CD, containers, deployment platforms, Kubernetes, infrastructure as code, release engineering, secrets, monitoring, and incident response. - 90check-devops
Audits the current project against a 312-item backend, database, security, DevOps and distributed-systems checklist and writes an evidence-backed status report. Use when the user says "check-devops", types /check-devops, or asks for a production-readiness / DevOps / backend audit of the project. - 90ck:devops
Deploy to Cloudflare (Workers, R2, D1), Docker, GCP (Cloud Run, GKE), Kubernetes (kubectl, Helm). Use for serverless, containers, CI/CD, GitOps, security audit. - 100kubernetes-secrets-manager
Manage kubernetes secrets manager operations. Auto-activating skill for DevOps Advanced. Triggers on: kubernetes secrets manager, kubernetes secrets manager Part of the DevOps Advanced skill category. Use when working with kubernetes secrets manager functionality. Trigger with… - 100devops-deployment
CI/CD, containers and infrastructure as code: GitHub Actions, Docker, Kubernetes, Helm, Terraform. Use when setting up pipelines or deployments.