AgentSkillsCN

17th-pr-handler

当用户希望分析GitHub PR反馈或未解决的对话时,可使用此技能。 利用GPT-5.2-Codex通过GitHub MCP,分析评审者评论的有效性。 自动触发条件: “PR反馈”“未解决”“评审评论”“确认反馈” 适用场景:PR评审处理、反馈有效性核查、评审者回复准备。 不适用于:创建PR、合并PR、直接编写代码。

SKILL.md
--- frontmatter
name: 17th-pr-handler
description: |
  Use this skill when user wants to analyze GitHub PR feedback or unresolved conversations.
  Analyzes validity of reviewer comments using GPT-5.2-Codex via GitHub MCP.
  Auto-triggers on: "PR 피드백", "unresolved", "리뷰 코멘트", "피드백 확인"
  Appropriate for: PR review handling, feedback validity check, reviewer response preparation.
  Not appropriate for: creating PRs, merging PRs, writing code directly.

PR Handler

Analyze GitHub PR unresolved feedback and judge validity using GPT-5.2-Codex.

Usage

code
/pr-feedback 183              → Codex high, PR #183
/pr-feedback 183 deep         → Codex xhigh, PR #183

Argument Parsing

Required:

  • PR number (numeric)

Keywords (reserved):

  • deep → Use xhigh effort instead of high

Parsing Logic

code
args = split(input)
pr_number = null
effort = "high"

for arg in args:
    if arg == "deep":
        effort = "xhigh"
    elif arg.isdigit():
        pr_number = arg

if pr_number is null:
    error("PR number required")

Result Mapping

InputPReffort
183183high
183 deep183xhigh
deep 183183xhigh

Analysis Output

VerdictMeaningAction
VALIDFeedback is correctShould apply
INVALIDFeedback is wrongShould not apply
NEEDS_DISCUSSIONSubjective/unclearDiscuss with reviewer

Implementation

Invoke the 17th-pr-handler subagent:

code
Task(
    description="Analyze PR #{pr_number} feedback ({effort})",
    subagent_type="17th-pr-handler",
    prompt="""
Analyze unresolved feedback for PR #{pr_number}.

Configuration:
- PR number: {pr_number}
- Effort: {effort}  (high or xhigh)
- Project root: {project_root}
""",
    run_in_background=true
)

Workflow After Analysis

  1. Subagent returns analysis report
  2. Main Agent presents to user:
    • Valid feedbacks → "Apply these?"
    • Invalid feedbacks → "Decline with reason?"
    • Needs discussion → "How to respond?"
  3. User decides → Main Agent executes

Output

  • Report: .kkachi/{branch_name}/completed/pr-feedback-{pr_number}-{epoch_timestamp}.md
  • Summary: X valid, Y invalid, Z needs discussion
  • Detailed reasoning for each judgment

Examples

Inputpr_numbereffort
183183high
183 deep183xhigh
456 deep456xhigh

Notes

  • Uses GPT-5.2-Codex with GitHub MCP
  • Read-only analysis (no code modifications)
  • Feedback can be wrong → careful judgment
  • Main Agent handles actual code changes with user
  • Ensure .kkachi/ is in .gitignore