Shared review workflow
Severity definitions, approval gate protocol, and fix constraints shared across all review and test skills.From its SKILL.md
npx -y skills add edfenton/claude-skills --skill shared-review-workflowAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.2 KB, 217 tokens by cl100k_base, as published. Nobody here has run it
Purpose
Define the common review workflow shared by code-review, design-review, and unit-test skills across all platforms.
Severity definitions
| Severity | Meaning |
|---|---|
| must-fix | Security vulnerability, broken functionality, blocks deployment or App Store submission |
| should-fix | Standards violation, maintainability concern, tech debt |
| nice-to-have | Style preference, minor improvement, optional optimization |
Approval gate
If issues are found and --no-fix is not set:
"Found X issues (Y must-fix). Approve fixes? (yes/no)"
Do not modify code before approval.
Fix and confirm (if approved)
- Apply fixes
- Re-run automated gates (lint, format, typecheck)
- Run unit tests to confirm no regressions
- Report final status
Fix constraints
- Don't add dependencies unless required
- Don't weaken assertions to make tests pass
- Prefer targeted fixes over broad refactors
- Don't disable or skip tests to make them pass
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.