infra-review
Skill1 starsChanged 2 days agoLicence not identifiedView on GitHub
Read-only review of a repo's infrastructure, that is IaC, environments, Docker and compose, Kubernetes, CI/CD and deploy, config and secrets management, backups and restore (including dev data in local volumes), monitoring and alarms, platform limits, infrastructure single points, pinned versions and cost. Cites path:line and proposes the lightest fix first. Never runs terraform plan/apply or deploy. Reports and stops. Use it for "review my infra", "is my deploy reproducible?", "do we have backups", "is my docker-compose ok?", "review my K8s manifests", "is my CI secure?", "why does nobody notice when it goes down?", "is my Terraform ok", "check my Dockerfile", "are our alerts set up", even without the word "infra". Not for system design (architecture-review), measuring performance (perf-diagnosis) or the security detail of a secret or permission (api-security-review). Also triggers on Spanish requests such as "revisa la infraestructura", "¿tengo backups?" or "¿mi CI es seguro?".
- Reads credentials
In this repository10 other files it gives its agents.
- api-security-reviewSkill
- apply-remediationSkill
- architecture-reviewSkill
- code-structureSkill
- correctness-reviewSkill
- data-consistencySkill
- implicit-state-machinesSkill
- llm-app-reviewSkill
- perf-diagnosisSkill
- repo-audit-swarmSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.