메뉴
Take an open PR from draft to merge-ready through conflict resolution, review feedback, and quality passes. Use when the user says "polish PR", "fix PR", "make PR merge-ready", "address review comments", or has an open PR with issues.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Generate protocol-compliant adapter stubs for Bucket 3 operations requiring external services. Use when the user requests "adapter stub", "dry run", "Bucket 3", "Linear ticket stub", "Kafka stub", or needs a fail-soft fallback for unavailable services.
Refine rough ideas into validated design docs through collaborative dialogue. Use when the user says "brainstorm", "help me design", "explore a feature", "let's think about", or has a vague idea that needs structure before coding.
Add multi-layer validation to fix bugs caused by invalid data. Use when debugging data corruption, invalid input reaching deep execution, "defense in depth", or when a bug needs structural prevention at every layer.
Capture session context for seamless continuity. Use when the user says "handoff", "wrap up", "end session", "pass the baton", "save progress", or needs to preserve working state for the next session.
Adversarial code review that iterates to convergence. Use when the user says "hostile review", "adversarial review", "tear this apart", "find all issues", or needs a thorough skeptical review of code or design.
Convert analysis results or review findings into actionable implementation plans. Use when the user says "turn insights into a plan", "prioritize findings", "action items from review", or has unstructured observations that need to become executable tasks.
| name | pr-polish |
| description | Take an open PR from draft to merge-ready through conflict resolution, review feedback, and quality passes. Use when the user says "polish PR", "fix PR", "make PR merge-ready", "address review comments", or has an open PR with issues. |
Use this skill when a PR exists but is not yet merge-ready. The goal is to take an open PR through conflict resolution, review feedback, and iterative quality passes until it is clean enough to merge.
Bring an existing PR from "open with issues" to "merge-ready" through a structured three-phase workflow. This prevents the common pattern of fixing one issue while introducing another.
gh CLI for PR data and pushingResolve merge conflicts (Phase 0).
Run git status to check for unmerged paths. If conflicts exist, resolve each file by reading both sides, choosing the correct resolution, then staging and committing. Skip this phase if no conflicts are found.
Address review comments and CI failures (Phase 1).
Fetch all open review comments with gh pr view <number> --json reviews,reviewThreads. For each unresolved thread:
Iterative local review (Phase 2). Review the full diff yourself. Fix any CRITICAL, MAJOR, or MINOR issues found. Re-review after fixing. Repeat until two consecutive passes find nothing above NIT severity. Cap at 10 iterations to prevent infinite loops.
Push and report. Push all fixes. Report a summary of each phase: files resolved, issues fixed, iterations needed, and final merge readiness status.
A phase-by-phase status report: