Menu
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/macro-inc/macro --skill qcThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Wrap a new backend endpoint in the TypeScript SDK (packages/sdk), or record it as skipped. Use when `just coverage` fails, or after adding an endpoint to a Rust service.
Debug local Rust services in this repository by starting the crate's binary with debug logging, tailing service logs, and using those logs to answer runtime questions. Use when Codex needs to investigate service startup, runtime behavior, errors, or logs for a Rust binary in a crate.
Validate Rust work after substantial Rust code changes by running `just check`, `just clippy`, then `just format`. Use before the final response after a significant Rust implementation or cleanup task; batch edits first instead of running after every small change.
Based on SOC occupation classification
Showing SKILL.md
| name | qc |
| description | Quality gate. 5 parallel agents review changes. All must pass. |
| allowed-tools | Task, Bash, Read, Grep, Glob |
DIFF=$(git diff main)
FILES=$(git diff main --name-only)
TASK="{task description or 'general changes'}"
Read 1-2 unmodified files from same directories for pattern context.
Spawn all 5 in parallel. All output raw JSON only, no markdown.
DIFF: ${DIFF}
- Descriptive naming?
- Errors caught with useful messages?
- No hardcoded values, commented code, debug statements?
- No TODO without ticket ref?
- No obvious bugs?
- No useless comments?
{"pass": bool, "issues": [...]}
DIFF: ${DIFF}
- Is this overcomplicated? Can I solve the same problem in a simpler manner?
- Can I reduce indirection?
- Can I reduce surface area?
- Premature abstraction? Premature Optimization? YAGNI violations?
- Dead code?
- Three similar lines > one abstraction
{"pass": bool, "issues": [...]}
DIFF: ${DIFF}
PATTERNS: ${PATTERN_FILES}
- Matches existing codebase patterns?
- Proper types, no any, no unsafe casts?
- Idiomatic error handling?
- Changes internally consistent?
- Is logic isolated and composable?
- Are there existing tests if neccesary?
{"pass": bool, "issues": [...]}
TASK: ${TASK}
DIFF: ${DIFF}
- Actually solves the problem?
- Edge cases: empty, null, zero, negative, boundaries, concurrency?
- Regression risk: changed signatures, shared state, removed exports?
- Maintains API contracts?
{"pass": bool, "issues": [...]}
TASK: ${TASK}
FILES: ${FILES}
DIFF: ${DIFF}
- Solved the problem or just the symptom?
- Changes unrelated to task?
- Unnecessary refactoring?
{"pass": bool, "issues": [...]}
| Check | Verdict | Issues |
|---|---|---|
| Code Review | ✓/✗ | ... |
| Simplification | ✓/✗ | ... |
| Consistency | ✓/✗ | ... |
| Robustness | ✓/✗ | ... |
| Scope | ✓/✗ | ... |
ALL PASS: Ready to commit.
ANY FAIL: List issues, fix them, run /qc again.
Same issue 3x: Escalate to user.