fix-pr-comments
Fetch PR review comments and implement all requested changes
- License 许可
- MIT
- 所属仓库
- zuzu59/z-skills
- 最近更新
- 2026-09-30
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- fix-pr-comments
- description
- Fetch PR review comments and implement all requested changes
- allowed-tools
- Bash(gh :*), Bash(git :*), Read, Edit, MultiEdit
- disable-model-invocation
- true
- allow_implicit_invocation
- false
02 资源文件 2
- 参考文档agents/openai.yaml343 B
- 资产文件assets/codex-icon.svg441 B
03 SKILL.md 正文
Fix PR Comments
Systematically address ALL unresolved review comments until PR is approved.
Context
- Current branch: !
git branch --show-current - Working tree status: !
git status --short - Recent commits: !
git log --oneline -3
Workflow
-
FETCH COMMENTS:
- Identify PR:
gh pr status --json number,headRefName - Get reviews:
gh pr review list --state CHANGES_REQUESTED - Get inline:
gh api repos/{owner}/{repo}/pulls/{number}/comments - Capture BOTH review comments AND inline code comments
- STOP if no PR found - ask user for PR number
- Identify PR:
-
ANALYZE & PLAN:
- Extract exact file:line references
- Group by file for MultiEdit efficiency
- STAY IN SCOPE: NEVER fix unrelated issues
- Create checklist: one item per comment
-
IMPLEMENT FIXES:
- BEFORE editing: ALWAYS
Readtarget file first - Batch changes with
MultiEditfor same-file modifications - Make EXACTLY what reviewer requested
- Check off each resolved comment
- BEFORE editing: ALWAYS
-
COMMIT & PUSH:
- Stage:
git add -A - Commit:
fix: address PR review comments - Push:
git push - NEVER include co-author tags
- Stage:
Rules
- Every unresolved comment MUST be addressed
- Read files BEFORE any edits - no exceptions
- FORBIDDEN: Style changes beyond reviewer requests
- On failure: Return to ANALYZE phase, never skip comments
User: $ARGUMENTS
04 同仓库更多 Skills
writing-great-skills
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
use-style
Apply named visual style guides to landing pages, app shells, and UI. Use for $use-style, /useskill, list styles, or styles like ios-app, grid, vercel, black-grid, stripe, linear, raycast, gumroad, dusk, or luma.
use-goal
Use when the user asks to create, draft, set, start, or refine a Codex or Claude Code `/goal` objective for persistent multi-turn work.
use-fable
Orchestrator mode for Fable: Fable thinks, plans, and reviews while Codex CLI and subagents execute all heavy work. Use when the user invokes /use-fable, says 'use fable', 'fable mode', 'orchestrator mode', or wants to save Fable tokens/rate limits.
use-delegate
Delegation mode: the host agent (Claude or Codex) plans and reviews while heavy work runs on cheap executors: OpenCode Kimi K3, Codex GPT-5.6 terra/sol. Use when the user invokes /use-delegate, says 'use delegate', 'delegate mode', 'orchestrator mode', or wants to save tokens/rate limits.
use-artifacts
Create Claude-style local HTML artifacts under ~/.agents/artifacts. Use for plans, prototypes, visualizations, dashboards, diagrams, options, or substantial reusable content, with a portable local runtime and no Anthropic API.