agentleFS
StosanStosan/Claude-Skills-for-engineering-teams/skills/staff-engineer-production-review/SKILL.md

staff-engineer-production-review

Skill2 starsChanged 5 days agoNo licenceView on GitHub

Review code the way a staff engineer reviews for production readiness: a severity-ranked findings report (Ship/Block verdict, Blocker/High/Medium/Nit) plus a scored rubric across correctness, design, security, reliability, observability, testing, and operability. Use this skill whenever the user asks to "review this code", "is this production ready", "review my PR", "audit this before we ship", "staff engineer review", "senior engineer review", "code review", "can this go to prod", "harden this service", or shares a diff, branch, file, or codebase and wants to know if it is safe to deploy. Also use it when the user asks what would break in production, what a senior reviewer would flag, or whether a change meets engineering standards — even if they don't say the word "review".

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — 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 364,980 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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.