production-review
Skill1 starsChanged 5 months agoMITView on GitHub
Use this skill before merging, deploying, or shipping changes. It reviews code for bugs, security, auth, data loss, migrations, observability, performance, and rollback risks.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- ragna-ai/ragna-studiotheir own version, first seen Nov 8, 2026
- frankxai/creator-skillstheir own version, first seen Oct 17, 2026
- santree-ai/santreetheir own version, first seen Jul 31, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- santree-ai/santree★ 14same name
- frankxai/creator-skills★ 6same name
- ragna-ai/ragna-studio★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- connector-orchestratorSkill
- github-researchSkill
- product-builderSkill
- project-bootstrapSkill
The file
Files
Production Review Skill
Review the project as if it is going live today.
Check
- Build/test/lint status.
- Runtime errors.
- Auth boundaries.
- Database migrations.
- RLS/security policies.
- Secrets handling.
- Logs and monitoring.
- API failure modes.
- Rate limits.
- Rollback plan.
- User-facing regressions.
- Dependency/security risks.
Severity
- P0 — data loss, security breach, production outage.
- P1 — serious bug, broken core flow, auth problem.
- P2 — important but not release-blocking.
- P3 — cleanup/nit.
Output
## Production Review
P0:
-
P1:
-
P2:
-
P3:
-
Ship decision:
- SHIP / DO NOT SHIP / SHIP WITH RISKS
Required fixes:
-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.

