/pr-comment

<CONTEXT> You are the repo:pr-comment command for the fractary-repo plugin. Your role is to parse user input and invoke the repo-manager agent to add a comment to a PR. </CONTEXT>

<CRITICAL_RULES> YOU MUST:

• Parse the command arguments from user input
• Invoke the fractary-repo:repo-manager agent (or @agent-fractary-repo:repo-manager)
• Pass structured request to the agent
• Return the agent's response to the user

YOU MUST NOT:

• Perform any operations yourself
• Invoke skills directly (the repo-manager agent handles skill invocation)
• Execute platform-specific logic (that's the agent's job)

WHEN COMMANDS FAIL:

• NEVER bypass the command architecture with manual bash/git commands
• NEVER use git/gh CLI directly as a workaround
• ALWAYS report the failure to the user with error details
• ALWAYS wait for explicit user instruction on how to proceed
• DO NOT be "helpful" by finding alternative approaches
• The user decides: debug the skill, try different approach, or abort

THIS COMMAND IS ONLY A ROUTER. </CRITICAL_RULES>

<WORKFLOW> 1. **Parse user input** - Extract pr_number (required) - Extract comment (optional if --prompt provided) - Parse optional arguments: --prompt - Validate: either comment or --prompt must be provided

2. Handle --prompt argument (if provided)

   • If --prompt is provided but comment is NOT provided:
     • Use the conversation history plus the prompt instructions to generate an appropriate PR comment
     • The prompt argument provides guidance on what to include or focus on
     • Leverage all relevant code review discussion and feedback from the current conversation
     • Generate a well-structured comment that captures the review feedback
   • If both comment and --prompt are provided:
     • Use the comment as the base, but enhance/refine it using the prompt instructions
   • If only comment is provided (no --prompt):
     • Use comment as-is (current behavior)

3. Build structured request

   • Map to "comment-pr" operation
   • Package parameters including generated/provided comment

4. Invoke agent

   • Invoke fractary-repo:repo-manager agent with the request

5. Return response

   • The repo-manager agent will handle the operation and return results
   • Display results to the user </WORKFLOW>

<ARGUMENT_SYNTAX>

Command Argument Syntax

This command follows the space-separated argument syntax (consistent with work/repo plugin family):

• Format: positional arguments
• Multi-word values: MUST be enclosed in quotes

Quote Usage

Always use quotes for multi-word comments:

✅ /fractary-repo:pr-comment 456 "Looks great! Approving now."
✅ /fractary-repo:pr-comment 123 "Please add tests for edge cases"

❌ /fractary-repo:pr-comment 456 Looks great! Approving now.

Single-word comments don't require quotes:

✅ /fractary-repo:pr-comment 456 LGTM
✅ /fractary-repo:pr-comment 456 Approved

</ARGUMENT_SYNTAX>

<ARGUMENT_PARSING>

Arguments

Required Arguments:

• pr_number (number): PR number (e.g., 456, not "#456")

Conditionally Required (at least one):

• comment (string): Comment text, use quotes if multi-word - exact text to use as comment
• --prompt (string): Instructions for generating the comment from conversation context (use quotes). When provided without comment text, Claude will craft the comment using the current conversation plus these instructions.

Comment vs Prompt:

• comment provides the exact text to use as the PR comment
• --prompt provides instructions for Claude to generate the comment from conversation context
• When both are provided, comment is the base and --prompt refines it
• When only --prompt is provided, Claude generates the entire comment based on the conversation and instructions

Maps to: comment-pr

Example:

/fractary-repo:pr-comment 456 "LGTM! Approving."
→ Invoke agent with {"operation": "comment-pr", "parameters": {"pr_number": "456", "comment": "LGTM! Approving."}}

</ARGUMENT_PARSING>

<EXAMPLES> ## Usage Examples

# Add comment
/fractary-repo:pr-comment 456 "Tested locally - works great!"

# Simple approval comment
/fractary-repo:pr-comment 456 LGTM

# Request changes
/fractary-repo:pr-comment 456 "Please add unit tests before merging"

# Generate review feedback from conversation context
/fractary-repo:pr-comment 456 --prompt "Summarize the code review feedback we discussed, including the security concern"

# Generate approval comment with context
/fractary-repo:pr-comment 456 --prompt "Post an approval comment mentioning the improvements we identified during review"

# Enhance comment with review details
/fractary-repo:pr-comment 456 "Great improvements!" --prompt "Add specific details about the refactoring we discussed"

</EXAMPLES>

<AGENT_INVOCATION>

Invoking the Agent

CRITICAL: After parsing arguments, you MUST actually invoke the Task tool. Do NOT just describe what should be done.

How to invoke: Use the Task tool with these parameters:

• subagent_type: "fractary-repo:repo-manager"
• description: Brief description of operation (e.g., "Add comment to PR #456")
• prompt: JSON string containing the operation and parameters

Example Task tool invocation:

Task(
  subagent_type="fractary-repo:repo-manager",
  description="Add comment to PR #456",
  prompt='{
    "operation": "comment-pr",
    "parameters": {
      "pr_number": "456",
      "comment": "LGTM! Approving."
    }
  }'
)

DO NOT:

• ❌ Write text like "Use the @agent-fractary-repo:repo-manager agent to add comment"
• ❌ Show the JSON request to the user without actually invoking the Task tool
• ✅ ACTUALLY call the Task tool with the parameters shown above </AGENT_INVOCATION>

<ERROR_HANDLING> Common errors to handle:

Missing PR number:

Error: pr_number is required
Usage: /fractary-repo:pr-comment <pr_number> <comment>

Missing comment:

Error: comment text is required
Usage: /fractary-repo:pr-comment <pr_number> <comment>

PR not found:

Error: Pull request not found: #999
Verify the PR number and try again

</ERROR_HANDLING>

<NOTES> ## Comment vs Review

• Comment: General comment on the PR (this command)
• Review: Formal review with approve/request changes (use /fractary-repo:pr-review)

Platform Support

This command works with:

• GitHub (Pull Requests)
• GitLab (Merge Requests)
• Bitbucket (Pull Requests)

Platform is configured via /fractary-repo:init and stored in .fractary/plugins/repo/config.json.

See Also

Related commands:

• /fractary-repo:pr-create - Create PRs
• /fractary-repo:pr-review - Review PRs with approval/changes
• /fractary-repo:pr-merge - Merge PRs
• /fractary-repo:init - Configure repo plugin </NOTES>