receiving-code-review
Skill0 starsChanged 3 months agoMITView on GitHub
Use when 리뷰 피드백 수령, 리뷰 지적 반영 직전, 피드백이 불명확하거나 기술적으로 의심스러울 때.
187 other projects use a version of this.
Adopted by
Most recently taken up by
- DemonDamon/AgenticXtheir own version, first seen Nov 9, 2026
- roundpilot/superpowers-antigravitytheir own version, first seen Nov 8, 2026
- REPOZY/superpowers-optimizedtheir own version, first seen Nov 8, 2026
- lingyired/status-triotheir own version, first seen Nov 8, 2026
- afawfawffaf/my-skillstheir own version, first seen Nov 8, 2026
- supermorkat/qawa-arenatheir own version, first seen Nov 8, 2026
Used with
Projects with it also use chinese-code-review, chinese-commit-conventions and 7 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
- Leodorareluctant259Skill
chinese-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
OpenAISkillfinishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
Also in 144 projects that use this
- OpenAISkill
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Also in 183 projects that use this
- +3 more from Leodorareluctant259
- +1 more from openai
Other versions187 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 187
- obra/superpowers★ 314ksame name
- cloudflare/workerd★ 9.1ksame name
- jnMetaCode/superpowers-zh★ 8.4ksame name
- openai/plugins★ 7.8ksame name
- farm-fe/farm★ 5.6ksame name
- microsoft/FluidFramework★ 4.9ksame name
- lingyired/status-trio★ 1.8ksame name
- GanyuanRan/Aegis★ 1.4ksame name
- pcvelz/superpowers★ 1.3ksame name
- DemonDamon/AgenticX★ 1ksame name
177 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 repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- design-reviewSkill
- dispatching-parallel-agentsSkill
- executing-designSkill
- finding-unknownsSkill
- finishSkill
- managing-repo-standard-docsSkill
- requesting-code-reviewSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- using-git-worktreesSkill
- using-groundworkSkill
- verification-before-completionSkill
- writing-for-juniorSkill
- writing-skillsSkill
The file
Files
receiving-code-review
Resolve the feedback
입력은 받은 리뷰 피드백이다. 구현자가 사용자 지시는 이해 후 반영하고, 봇·서브에이전트·PR 리뷰 등 외부 피드백은 코드·테스트·기존 계약과 대조해 수용하거나 근거로 반박한다. 출처가 불명확하면 외부 피드백으로 다룬다.
불명확한 항목이 있으면 먼저 해소한다. 실제 사용처와 필요한 계약을 확인하고, 쓰이지 않는 기능을 리뷰를 만족시키려고 추가하지 않는다.
사용자의 앞선 결정과 충돌하는 제안은 임의 반영하지 않는다. 정책 재검토에 새 근거가 있으면 groundwork:finding-unknowns로 영향과 선택을 설명한다.
차단 문제부터 수정하고 변경에 맞는 검증을 실행한다. 형식적 동의·감사·긴 사과 대신 변경 내용과 기술 근거로 답한다. 출력은 반영한 변경·검증 결과와 항목별 수용·반박 근거다. 해소되지 않은 판단은 근거와 함께 사용자에게 보고한다. 수정 후 재리뷰는 호출한 실행 스킬의 게이트를 따른다.
Reply in the review thread
GitHub 인라인 코멘트에 답하는 작업이 요청됐으면 해당 스레드에 답한다. 아래 블록은 대상 리포 루트에서 실행하고 OWNER, REPO, PR은 대상 소유자·이름·PR 번호, COMMENT_ID는 조회한 코멘트 ID로 치환한다.
gh api "repos/OWNER/REPO/pulls/PR/comments" --jq '.[] | "\(.id)\t\(.path):\(.line)\t\(.body[0:60])"'
gh api --method POST "repos/OWNER/REPO/pulls/PR/comments/COMMENT_ID/replies" -f body='<답글 본문>'Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.