receiving-code-review
Skill1 starsChanged 9 months agoNo licenceView on GitHub
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
217 other projects use a version of this, 103 of them edited; 79 of 103 edited versions we compared changed its rules; 10 new projects in the last 4 weeks, against 13 the 4 before.
How people change it
79 of 103 edited versions changed its rules, and some changes recur.
Of the 103 edited versions we compared: 21 keep every rule, 3 are an older text, 79 made changes of their own.
Not in older versions
- When replying to inline review comments on GitHub, reply in the comment thread (
gh api repos/{owner}/{repo}/pulls/{pr}/comments/{id}/replies), not as a top-level PR comment.missing from 2 of 3 - Verify. Question. Then implement.missing from 1 of 3
- No performative agreement. Technical rigor always.missing from 1 of 3
Rules people drop
- Verify. Question. Then implement.dropped by 65 of 79
- No performative agreement. Technical rigor always.dropped by 64 of 79
- When replying to inline review comments on GitHub, reply in the comment thread (
gh api repos/{owner}/{repo}/pulls/{pr}/comments/{id}/replies), not as a top-level PR comment.dropped by 18 of 79 - If you catch yourself about to write "Thanks": DELETE IT. State the fix instead.dropped by 17 of 79
- When feedback IS correct:dropped by 11 of 79
- If you pushed back and were wrong:dropped by 10 of 79
- Still ask if scope uncleardropped by 9 of 79
- Use technical reasoning, not defensivenessdropped by 9 of 79
Rules people add
- Test each fix individuallyadded by 3 of 79
- If unused: "This endpoint isn't called. Remove it (YAGNI)?"added by 2 of 79
- If ANY item is unclear: STOP. Do not implement anything yet.added by 2 of 79
- A rule we can't quote: its licence doesn't allow itadded by 2 of 79
- A rule we can't quote: its licence doesn't allow itadded by 2 of 79
- A rule we can't quote: its licence doesn't allow itadded by 2 of 79
- WHEN receiving code review feedback:added by 2 of 79
- READ: Complete feedback without reactingadded by 2 of 79
We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.
Adopted by
Cooling: 10 new projects took it in the last 4 weeks, 0.8× the 4 weeks before.
Most recently taken up by
- Floppa2003/skillsedited, first seen Nov 16, 2026
- Badhon-00/MDCPedited, first seen Nov 16, 2026
- b-mendoza/agent-skillsedited, first seen Nov 16, 2026
- Binbin-miao/workbuddy-expert-teamtheir own version, first seen Nov 15, 2026
- roronoazoroshao369/vibe-coding-ostheir own version, first seen Nov 15, 2026
- mintunitish/tandemedited, first seen Nov 15, 2026
Used with
Projects with it also use chinese-code-review, chinese-commit-conventions and 4 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
- +3 more from Leodorareluctant259
Other versions217 projects use a version of this.
Word for word · 85
- farm-fe/farm★ 5.6k100% same
- DemonDamon/AgenticX★ 1.1k100% same
- derHaken/SuperAntigravity★ 439100% same
- oasm-platform/open-asm★ 277100% same
- julianromli/ai-skills★ 222100% same
- totvs/engpro-advpl-tlpp-skills★ 166100% same
- haojing8312/WorkClaw★ 141100% same
- ARounder-183/HiFiShifter★ 93100% same
- cooker/wxHm★ 70100% same
- roman01la/skills-agents★ 48100% same
75 more not listed
Edited · 103
- obra/superpowers★ 314k96% same
- cloudflare/workerd★ 9.2k98% same
- openai/plugins★ 7.8k96% same
- microsoft/FluidFramework★ 4.9k20% same
- lingyired/status-trio★ 1.8k96% same
- GanyuanRan/Aegis★ 1.4k98% same
- pcvelz/superpowers★ 1.3k96% same
- mdiri-ai/SoduWork★ 93094% same
- coco-research/coco★ 79798% same
- koaning/wigglystuff★ 46396% same
93 more not listed
Wrote their own version · 29
- jnMetaCode/superpowers-zh★ 8.5ksame name
- REPOZY/superpowers-optimized★ 146same name
- shibit-net/xuanji-community★ 90same name
- GEd520/legados★ 75same name
- tranhieutt/software_development_department★ 71same name
- drvoss/everything-copilot-cli★ 49same name
- iliaal/ai-skills★ 45same name
- bostonaholic/rpikit★ 19same name
- ovargas/virtual-team★ 14same name
- JUNERDD/skills★ 6same name
19 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 repository704 other files it gives its agents.
- postgres-best-practices/AGENTS.mdAGENTS.md
- react-best-practices/AGENTS.mdAGENTS.md
- loki-mode/CLAUDE.mdCLAUDE.md
- 3d-web-experienceSkill
- ab-test-setupSkill
- accessibility-compliance-accessibility-auditSkill
- activecampaign-automationSkill
- Active Directory AttacksSkill
- address-github-commentsSkill
- agent-evaluationSkill
- agent-manager-skillSkill
- agent-memory-mcpSkill
- agent-memory-systemsSkill
- agent-orchestration-improve-agentSkill
- agent-orchestration-multi-agent-optimizeSkill
- agent-tool-builderSkill
- ai-agents-architectSkill
- ai-engineerSkill
- ai-productSkill
- airflow-dag-patternsSkill
- airtable-automationSkill
- ai-wrapper-productSkill
- algolia-searchSkill
- algorithmic-artSkill
- amplitude-automationSkill
- analytics-trackingSkill
- angular-best-practicesSkill
- angular-migrationSkill
- angularSkill
- angular-state-managementSkill
- angular-ui-patternsSkill
- anti-reversing-techniquesSkill
- api-design-principlesSkill
- api-documentation-generatorSkill
- api-documenterSkill
- API Fuzzing for Bug BountySkill
- api-patternsSkill
- api-security-best-practicesSkill
- api-testing-observability-api-mockSkill
- app-builderSkill
- application-performance-performance-optimizationSkill
- app-store-optimizationSkill
- architect-reviewSkill
- architecture-decision-recordsSkill
- architecture-patternsSkill
- architectureSkill
- arm-cortex-expertSkill
- asana-automationSkill
- async-python-patternsSkill
- attack-tree-constructionSkill
- audio-transcriberSkill
- auth-implementation-patternsSkill
- automate-whatsappSkill
- autonomous-agent-patternsSkill
- autonomous-agentsSkill
- avalonia-layout-zafiroSkill
- avalonia-viewmodels-zafiroSkill
- avalonia-zafiro-developmentSkill
- AWS Penetration TestingSkill
- aws-serverlessSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. 6 are common, 2 are distinctive, and 1 is very specific to this project.
6
Common
Most of the 124 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
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 measured: kept by at least 6 in 10 of the 124 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.
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.

