review-design
Skill3 starsChanged 10 days agoMITView on GitHub
Read-only evaluator for one bounded design brief. Return evidence-backed boundary findings; direct review requests belong to review-change, and final adjudication stays with the calling agent.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- dorian-akhs/skillstheir own version, first seen Nov 8, 2026
- alo-exp/silver-bullettheir own version, first seen Nov 1, 2026
- timholy/claude_configtheir own version, first seen Oct 20, 2026
- WhorideChicken/first-playabletheir own version, first seen Oct 11, 2026
- fpindej/netrocktheir own version, first seen Oct 8, 2026
- mgiovani/cc-arsenaltheir own version, first seen Sep 25, 2026
Used with
Projects with it also use review-pr.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
DockerSkillreview-pr
Review one or more incoming Docker documentation pull requests as a maintainer. Independently validate technical claims, assess editorial fit and information architecture, choose a verdict, and draft exact inline or PR-wide feedback behind a confirmation gate. Use for requests such as "review PR 123", "is this PR correct?", "does this information belong here?", "validate this PR", or "help review backlog PRs". Do not use to maintain or fix a PR you own; use maintain-pr for that.
Also in 3 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- fpindej/netrock★ 234same name
- timholy/claude_config★ 75same name
- gtrabanco/agentic-workflow★ 23same name
- mgiovani/cc-arsenal★ 8same name
- alo-exp/silver-bullet★ 7same name
- WhorideChicken/first-playable★ 3same name
- dirkkok101/skills★ 2same name
- herohua/skills★ 1same name
- dorian-akhs/skills★ 0same name
- Jagoda11/the-jagoda-toolkit★ 0same 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 repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- analyze-projectSkill
- api-contract-strategySkill
- architecture-patternsSkill
- close-changeSkill
- design-changeSkill
- development-standardsSkill
- docker-multiarch-buildSkill
- error-patternsSkill
- go-guidelinesSkill
- herdr-implementSkill
- implement-changeSkill
- logging-standardsSkill
- lua-guidelinesSkill
- organize-docsSkill
- output-stylesSkill
- plan-changeSkill
- powershell-guidelinesSkill
- python-guidelinesSkill
- review-changeSkill
- review-implementationSkill
- review-planSkill
- routeros-scripting-guidelinesSkill
- runtime-diagnosisSkill
- security-guardrailsSkill
- shell-guidelinesSkill
- skill-authoringSkill
- skill-minerSkill
- skills-routingSkill
- smart-commitSkill
- sops-age-guardrailsSkill
- sync-truthSkill
- testing-strategySkill
The file
Files
Review Design
Evaluate only the supplied design target and brief under the finding rules, causal scope, and verdict in review-change. For a whole-design target, defects anywhere in the artifact are in scope; for a diff-scoped target, a blocking candidate is caused or newly activated by that diff.
Design-Specific Checks
- Scope and ownership: one bounded change surface with a named owner, a sane dependency direction, and durable truth boundaries that stay put; material rollout or recovery risk the design does not own.
- Decisions versus means: a material unresolved decision, or an omitted main goal, necessary condition, specified technical choice, or inviolable boundary. Local choices an executor can investigate stay with the executor.
- Acceptance and cutover: success is verifiable without turning every acceptance condition into a prerequisite for switching; coexistence, qualification environments, rollback systems, and observation windows cite a concrete protected interest, per the replacement-and-cutover reference in
development-standards. - Delivery intent: delivery intent, existing authority, and actual capability stay separate; facts material to feasibility or protected boundaries are preserved in the design or an accessible owner record, with supplied facts distinct from assumptions.
- Secondary space: authorized best-effort secondary work is recorded without an exhaustive failure catalog; commitments that would force item-by-item reapproval are flagged.
- Architecture tradeoff: demand, constraints, ownership, and practical evidence support the choice; recovery or reconsideration detail appears where a concrete risk or unsettled premise needs it.
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.

