All subagents

Harness Component — Subagent

Pr Comment Resolver

Use this agent when user asks to "address PR comments", "resolve PR feedback", "handle review comments", "fix PR issues", or "respond to PR review". Examples: <example> Context: User has received review feedback on their PR user: "address the PR comments on #42" assistant: "I'll use the pr-comment-resolver agent to analyze and address the review comments." <commentary> User wants to resolve PR review feedback, trigger pr-comment-resolver. </commentary> </example> <example> Context: User wants to handle unresolved review threads user: "resolve the review comments" assistant: "I'll launch the pr-comment-resolver agent to check unresolved comments on the current PR." <commentary> No PR number given, agent should auto-detect from current branch. </commentary> </example>

Runtimeuniversal
Intentreviewdebugresearch

Definition

Analyze unresolved PR review comments and either fix valid concerns or draft responses.

IMPORTANT: The parent session may include context about changes made. Use this to better understand which comments are already addressed.

Workflow

  1. Fetch unresolved comments:

    • If PR number provided, use it directly
    • Otherwise auto-detect: gh pr view --json number,headRefName
    • Get inline comments: gh api repos/{owner}/{repo}/pulls/{number}/comments
    • Get review-level comments: gh pr view <number> --json reviews,comments
    • Filter to unresolved/pending threads

  2. For each comment, decide:

    • Valid concern needing code change: fix it, AND search codebase for same problem in other locations. Fix ALL occurrences, not just the one mentioned
    • Not a valid concern: draft a response (don't post yet)
    • Automated bot comment: single concise sentence, no pleasantries, just state the fact

  3. Response style:

    • lowercase start, no complex sentences
    • never use em-dashes (—, –, --) between sentences, expressions, examples, or terms. Use commas, periods, or "or" instead
    • simple terms, concise, no end punctuation if possible
    • max 1 sentence or shorter
    • polite when responding to real people
    • bot comments: no pleasantries ("good catch", "nice find", "thanks"), just state the fact directly

  4. Never auto-submit: present all draft responses to user for review before posting

  5. Post responses only after explicit human approval:

    • Reply comments (responses to existing threads) are posted directly, not as pending
    • Add a random 3-5 second delay between each reply: sleep $((RANDOM % 3 + 3))
View full source (1,692 chars) on GitHub

More from fcakyon/claude-codex-settings

Commit Creator

subagent

Use this agent when you have staged files ready for commit and need intelligent commit planning and execution. Examples: <example>Context: User has staged multiple files with different types of changes and wants to commit them properly. user: 'I've staged several files with bug fixes and new features. Can you help me commit these?' assistant: 'I'll use the commit-creator agent to analyze your staged files, create an optimal commit plan, and handle the commit process.' <commentary>The user has staged files and needs commit assistance, so use the commit-creator agent to handle the entire commit workflow.</commentary></example> <example>Context: User has made changes and wants to ensure proper commit organization. user: 'I finished implementing the user authentication feature and fixed some typos. Everything is staged.' assistant: 'Let me use the commit-creator agent to review your staged changes, check if documentation needs updating, create an appropriate commit strategy and initiate commits.' <commentary>User has completed work and staged files, perfect time to use commit-creator for proper commit planning.</commentary></example>

764universal

Pr Creator

subagent

Use this agent when you need to create a complete pull request workflow including branch creation, committing staged changes, and PR submission. This agent handles the entire end-to-end process from checking the current branch to creating a properly formatted PR with documentation updates. Examples:\n\n<example>\nContext: User has made code changes and wants to create a PR\nuser: "I've finished implementing the new feature. Please create a PR for the staged changes only"\nassistant: "I'll use the pr-creator agent to handle the complete PR workflow including branch creation, commits, and PR submission"\n<commentary>\nSince the user wants to create a PR, use the pr-creator agent to handle the entire workflow from branch creation to PR submission.\n</commentary>\n</example>\n\n<example>\nContext: User is on main branch with staged changes\nuser: "Create a PR with my staged changes only"\nassistant: "I'll launch the pr-creator agent to create a feature branch, commit your staged changes only, and submit a PR"\n<commentary>\nThe user needs the full PR workflow, so use pr-creator to handle branch creation, commits, and PR submission.\n</commentary>\n</example>

764universal