From propel-code-review
Help address Propel Code AI review/issue comments on the open GitHub PR for the current branch using gh CLI, with mode-based execution and agent triage defaults.
How this skill is triggered — by the user, by Claude, or both
Slash command
/propel-code-review:propel-address-pr-commentsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Guide to find the open PR for the current branch and address its comments with gh CLI. Run all `gh` commands with elevated network access.
Guide to find the open PR for the current branch and address its comments with gh CLI. Run all gh commands with elevated network access.
Paths below are relative to this skill directory:
scripts/fetch_comments.py fetches PR conversation comments, reviews, and
inline review threads via gh api graphql.addressable subset that already excludes:
gh pr view --json, for inline review discovery.
gh pr view does not expose reviewThreads.If your client supports prefix-based trust/approval, approve these once before running this skill:
scripts/fetch_comments.pypython3 scripts/fetch_comments.pypython scripts/fetch_comments.pygh auth statusgh pr viewgh api graphqljqExecution order:
addressable subset.Supported modes:
ALL_COMMENTS: Address all eligible Propel-authored comments.AGENT_DECIDES: Let this coding agent triage and implement comments using internal triage rules.HUMAN_SELECTS: Human chooses numbered comments to implement.Eligibility scope:
Internal triage policy (used only for AGENT_DECIDES):
error, warning, info internally.error and warning commentsinfo by default unless user explicitly asks to include it, or the fix is clearly high-value and low-riskWhen no structured severity is present in fetched GitHub comments:
error: security, data loss, crashes, major correctness bugswarning: correctness risks, reliability/performance concerns, maintainability problemsinfo: style, naming, docs, non-blocking suggestionsPrerequisites:
gh is authenticated (for example, run gh auth login once), then run gh auth status with escalated permissions (include workflow/repo scopes) so gh commands succeed. If sandboxing blocks gh auth status, rerun it with sandbox_permissions=require_escalated.PROPEL_API_KEY environment variable is set (for example, run if [ -n "$PROPEL_API_KEY" ]; then echo "PROPEL_API_KEY is set"; else echo "PROPEL_API_KEY is not set"; fi). If it is not set, tell the user to open https://app.propelcode.ai/administration/settings?tab=review-api-tokens&token_name=Claude+Code&scopes=reviews:read,reviews:write, generate a token (scopes are pre-filled), and paste it back. Then export it for the session: export PROPEL_API_KEY="<token>".scripts/fetch_comments.py (or python3 scripts/fetch_comments.py). This defaults to addressable-only output.gh pr view --json to fetch inline comments; it does not expose reviewThreads.--all-comments only when you explicitly need the full raw payload.addressable payload only.addressable.excluded.I found <N> Propel comments.[<severity>] <file-or-thread-location> - <very concise summary>How should I handle Propel comments for this PR?
1. Fix all actionable Propel comments
2. Let this coding agent triage and implement comments
3. I'll choose comments manually by number
Reply with 1, 2, or 3.
mode, and that user can reply change mode to override.ALL_COMMENTSAGENT_DECIDESHUMAN_SELECTSAGENT_DECIDES)Notes:
gh auth login, then retry.npx claudepluginhub propel-gtm/propel-code-skills --plugin propel-code-reviewReads open GitHub PR review comments, triages by severity, applies code fixes, and drafts replies. Use when addressing PR feedback or code review.
Fetches and addresses GitHub PR review/issue comments on current branch using gh CLI. Lists threads via script, summarizes fixes, applies user-selected changes, with auth handling.
Fetches and guides the user through addressing review/issue comments on the open GitHub PR for the current branch using gh CLI.