requesting-code-review
Skill1 starsChanged 3 days agoMITView on GitHub
Structures code review requests with context, commit hashes, and requirements. Facilitates early and frequent review cycles.
187 other projects use a version of this.
Adopted by
Most recently taken up by
- Floppa2003/skillstheir own version, first seen Nov 16, 2026
- Badhon-00/MDCPtheir own version, first seen Nov 16, 2026
- roronoazoroshao369/vibe-coding-ostheir own version, first seen Nov 15, 2026
- mintunitish/tandemtheir own version, first seen Nov 15, 2026
- FimawLLC/fimaw-skillstheir own version, first seen Nov 15, 2026
- mdiri-ai/SoduWorktheir own version, first seen Nov 15, 2026
Used with
Projects with it also use chinese-code-review, chinese-commit-conventions and 10 more.
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.
Leodorareluctant259Skillchinese-code-review
中文代码审查规范——在保持专业严谨的同时,用符合国内团队文化的方式给出有效反馈
Also in 8 projects that use this
Leodorareluctant259Skillchinese-commit-conventions
中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化
Also in 8 projects that use this
obraSkilldiagnosing-superpowers
Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.
Also in 20 projects that use this
math-incSkillheartmula
Set up and run HeartMuLa, the open-source music generation model family (Suno-like). Generates full songs from lyrics + tags with multilingual support.
Also in 9 projects that use this
Tommy-ywSkillwebhook-subscriptions
Create and manage webhook subscriptions for event-driven agent activation, or for direct push notifications (zero LLM cost). Use when the user wants external services to trigger agent runs OR push notifications to chats.
Also in 5 projects that use this
john-data-chenSkilltouchdesigner-mcp
Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.
Also in 7 projects that use this
- +3 more from Leodorareluctant259
Other versions187 projects use a version of this.
Word for word · 1
- LucasCooperBey/claude-skills★ 1100% same
Edited · 0
None found.
Wrote their own version · 186
- obra/superpowers★ 314ksame name
- NousResearch/hermes-agent★ 264ksame name
- jnMetaCode/superpowers-zh★ 8.5ksame name
- openai/plugins★ 7.8ksame name
- farm-fe/farm★ 5.6ksame name
- lingyired/status-trio★ 1.8ksame name
- GanyuanRan/Aegis★ 1.4ksame name
- pcvelz/superpowers★ 1.3ksame name
- math-inc/OpenGauss★ 1.3ksame name
- DemonDamon/AgenticX★ 1ksame name
176 more not listed
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 repository53 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/deep-recon/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- adversarial-researchSkill
- algorithmic-artSkill
- api-integrationSkill
- breakdownSkill
- c4-architectSkill
- canvas-designSkill
- coding-agentsSkill
- compound-engineeringSkill
- context-budgetSkill
- counterfactualSkill
- critiqueSkill
- d3js-visualizationSkill
- data-analyst-agentSkill
- database-migrationsSkill
- deep-reconSkill
- design-tasteSkill
- e2b-sandboxSkill
- ecosystem-auditSkill
- executing-plansSkill
- frontend-designSkill
- fullstack-agentSkill
- grillSkill
- kickoffSkill
- mcp-builderSkill
- model-migrationSkill
- naming-the-machineSkill
- full-output-enforcementSkill
- package-researchSkill
- pdf-generationSkill
- pp2pSkill
- pp3pSkill
- prompt-engineerSkill
- prompt-groundingSkill
- redesignSkill
- reverse-engineer-to-learnSkill
- review-changesSkill
- scratchpadSkill
- shipSkill
- slack-gif-creatorSkill
- sprint-architectSkill
- techdebtSkill
- test-and-fixSkill
- threat-modelSkill
- verification-before-completionSkill
- visual-verdictSkill
- webapp-testingSkill
- web-asset-generatorSkill
- whatdidimissSkill
- wiki-writeSkill
- writing-plansSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 173 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 131
If feedback seems incorrect:
- Distinctive: line 133
Don't dismiss it immediately
“Common” is measured: kept by at least 6 in 10 of the 173 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Requesting Code Review
Structure code review requests for effective feedback.
Core Principle
Review early, review often. Prevents issues from compounding.
When Reviews Are Required
| Scenario | Priority |
| After each task in subagent workflow | Required |
| Upon finishing major features | Required |
| Before merging to main | Required |
| When stuck | Optional |
| Before refactoring | Optional |
| After fixing complex bugs | Optional |
Request Process
1. Gather Context
# Get commit range
BASELINE=$(git merge-base HEAD main)
CURRENT=$(git rev-parse HEAD)
echo "Baseline: $BASELINE"
echo "Current: $CURRENT"
# Show what changed
git log $BASELINE..$CURRENT --oneline
git diff $BASELINE..$CURRENT --stat2. Dispatch Review Request
Task({
prompt: `
Code review request.
## What Was Built
[Brief description of feature/fix]
## Requirements
[Original requirements or task description]
## Commits
- Baseline: ${BASELINE}
- Current: ${CURRENT}
## Description
[What changed and why]
## Areas of Concern
[Specific things to look at closely]
Please review for:
- Spec compliance
- Code quality
- Test coverage
- Potential issues
`,
subagent_type: "general-purpose"
})3. Act on Findings
| Severity | Action |
| Critical | Fix immediately |
| Important | Fix before proceeding |
| Minor | Document for later |
Request Template
## Code Review Request
### Summary
[One sentence describing what this code does]
### Requirements Fulfilled
- [x] Requirement 1
- [x] Requirement 2
### Changes
**Files modified:**
- `src/feature.ts` - Added validation logic
- `src/feature.test.ts` - Added tests
**Commits:**abc123 - Add user validation def456 - Add error handling
### How to Test
```bash
bun test src/feature.test.tsConcerns
- Performance of X might be an issue with large data
- Not sure if Y pattern is idiomatic
Questions
- Should we also handle edge case Z?
## Reviewer Categories
Reviewers will categorize feedback:
| Category | Meaning | Your Action |
|----------|---------|-------------|
| Critical | Blocks merge | Fix now |
| Important | Should fix | Fix before continuing |
| Minor | Nice to have | Schedule for later |
| Question | Clarification | Answer promptly |
## Handling Disagreement
If feedback seems incorrect:
1. Don't dismiss it immediately
2. Provide technical evidence
3. Explain your reasoning
4. Be open to being wrong
I hear your concern about X. Here's why I chose this approach:
- [Technical reason]
- [Evidence from testing]
- [Alternative considered and why rejected]
If you still think Y is better, I'm happy to change it.
## Post-Review
After receiving feedback:
```bash
# Fix issues
# ...
# Verify fixes
bun test
# Commit fixes
git commit -m "Address review feedback: [summary]"
# Re-request if changes were significantSource
Adapted from https://github.com/obra/superpowers (MIT, Copyright (c) 2025 Jesse Vincent). Changed for this repo by Lucas Cooper-Bey in 2026: wording rewritten into tables.
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.

