fix-pr
Skill14 starsChanged 37 days agoMITView on GitHub
PR 리뷰 코멘트를 자동 수집하고, 해당 코드를 수정하여 재커밋합니다. GitHub PR 피드백 루프를 자동화합니다.
- Commits and pushes
15 other projects use a version of this.
Adopted by
Most recently taken up by
- pytorch/heliontheir own version, first seen Nov 8, 2026
- theam/claude-dev-kittheir own version, first seen Nov 1, 2026
- bjcoombs/ai-native-toolkittheir own version, first seen Oct 13, 2026
- grove/promise-to-prooftheir own version, first seen Oct 12, 2026
- tbhb/vale-ai-tellstheir own version, first seen Oct 11, 2026
- sgomez/developer-skillstheir own version, first seen Oct 9, 2026
Used with
Projects with it also use rebase, review-pr and 3 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.
raineSkillrebase
Rebase the current branch with smart conflict resolution.
Also in 3 projects that use this
DockerSkillreview-pr
Review one or more incoming Docker documentation pull requests as a maintainer. Independently validate technical claims, assess editorial fit and information architecture, choose a verdict, and draft exact inline or PR-wide feedback behind a confirmation gate. Use for requests such as "review PR 123", "is this PR correct?", "does this information belong here?", "validate this PR", or "help review backlog PRs". Do not use to maintain or fix a PR you own; use maintain-pr for that.
Also in 4 projects that use this
SentrySkilldeslop
Strip AI-generated noise from the diff before pushing — extra comments a human wouldn't write, defensive try/catch in trusted code paths, casts to any, inline imports in Python, and other style inconsistencies with the surrounding file. Use this immediately before commit so the diff stays clean.
Also in 3 projects that use this
SentrySkillcommit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
Also in 4 projects that use this
MicrosoftSkillrelease
Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).
Also in 3 projects that use this
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- questdb/questdb★ 18ksame name
- pytorch/helion★ 979same name
- deadlock-mod-manager/deadlock-mod-manager★ 584same name
- spiriMirror/libuipc★ 351same name
- tbhb/vale-ai-tells★ 118same name
- GiggleLiu/cryochamber★ 34same name
- bjcoombs/ai-native-toolkit★ 32same name
- Codagent-AI/agent-skills★ 31same name
- theam/claude-dev-kit★ 17same name
- kbarendrecht/orchestrator★ 11same name
5 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 repository44 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adaptSkill
- animateSkill
- auditSkill
- bolderSkill
- brainstormSkill
- build-fixSkill
- business-panelSkill
- checkpointSkill
- clarifySkill
- colorizeSkill
- composition-patternsSkill
- confidence-checkSkill
- config-doctorSkill
- critiqueSkill
- delightSkill
- design-auditSkill
- devils-advocateSkill
- distillSkill
- eval-harnessSkill
- feature-plannerSkill
- frontend-designSkill
- gap-analysisSkill
- grill-with-docsSkill
- hardenSkill
- impeccableSkill
- layoutSkill
- learnSkill
- optimizeSkill
- overdriveSkill
- polishSkill
- pytest-runnerSkill
- python-best-practicesSkill
- quieterSkill
- react-best-practicesSkill
- sc-helpSkill
- security-auditSkill
- shapeSkill
- tddSkill
- typesetSkill
- ui-ux-pro-maxSkill
- uv-packageSkill
- verifySkill
- web-design-guidelinesSkill
The file
Files
Fix PR
Purpose
GitHub PR의 리뷰 코멘트를 수집하고, 코멘트에 따라 코드를 자동 수정하여 재커밋합니다.
Dynamic Context
Current branch:
!git branch --show-current 2>/dev/null
Open PR comments:
!gh pr view --json number,title,reviewDecision 2>/dev/null || echo "No PR found for current branch"
Usage
/fix-pr # 현재 브랜치의 PR 코멘트 수정
/fix-pr 123 # PR #123의 코멘트 수정Workflow
Step 1: Collect Comments
# PR의 모든 미해결 리뷰 코멘트 수집
gh api repos/{owner}/{repo}/pulls/{pr}/comments \
--jq '.[] | select(.position != null) | {path: .path, line: .line, body: .body}'
# 리뷰 쓰레드의 미해결 항목
gh api repos/{owner}/{repo}/pulls/{pr}/reviews \
--jq '.[] | select(.state == "CHANGES_REQUESTED") | {body: .body}'Step 2: Categorize
각 코멘트를 분류:
- Must Fix: 변경 요청 (CHANGES_REQUESTED)
- Should Fix: 제안 (suggestion, consider)
- Optional: 질문, 의견
Step 3: Apply Fixes
각 Must Fix / Should Fix 코멘트에 대해:
- 해당 파일과 라인 위치 파악
- 코멘트 의도에 맞게 코드 수정
- 수정 내용 요약
Step 4: Verify & Commit
# 빌드/테스트 확인
/verify quick
# 수정 커밋
git add -A
git commit -m "fix: address PR review comments
- [comment 1 summary]
- [comment 2 summary]
..."
# 푸시
git pushStep 5: Report
## PR Fix Report
### Fixed (N items)
| # | File | Line | Comment | Fix |
|---|------|------|---------|-----|
| 1 | src/api.ts | 45 | Missing error handling | Added try-catch |
### Skipped (N items)
| # | Reason | Comment |
|---|--------|---------|
| 1 | Optional/Opinion | "Consider using X" |
### Action Required
- [ ] Re-request review
- [ ] Resolve conversations on GitHubConstraints
- 코드 수정만 -- PR 설정, 라벨, 할당 등은 변경하지 않음
- Must Fix 항목은 모두 처리
- 불확실한 코멘트는 스킵하고 보고
- 푸시 전 반드시 /verify 실행
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.

