gh-address-comments
Help address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.
Install
mkdir -p .claude/skills/gh-address-comments-twlongzai && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13667" && unzip -o skill.zip -d .claude/skills/gh-address-comments-twlongzai && rm skill.zipInstalls to .claude/skills/gh-address-comments-twlongzai
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Help address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.About this skill
PR Comment Handler (Axum/Cargo/SQLx/GitHub Actions)
Guide to find the open PR for the current branch and address its comments with gh CLI. This variant is tailored for Axum, Cargo, SQLx, and GitHub Actions workflows. Run all gh commands with elevated network access.
Prereq: ensure 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.
When drafting responses, use the reply template at .codex/skills/gh-address-comments/templates/pr_reply.md for consistency.
1) Inspect comments needing attention
- Run
scripts/fetch_comments.pywhich will print out all the comments and review threads on the PR - Identify comments related to:
- Axum handlers, routing, extractors, middleware, or error handling
- Cargo features, workspace setup, or dependency versions
- SQLx queries, migrations, and compile-time checking
- GitHub Actions workflows, caches, or CI steps
2) Ask the user for clarification
- Number all the review threads and comments and provide a short summary of what would be required to apply a fix for it
- Ask the user which numbered comments should be addressed
- Call out when a fix might require running
cargo test,cargo sqlx prepare, or updating CI
3) If user chooses comments
- Apply fixes for the selected comments
- Keep changes aligned with Axum idioms and SQLx best practices
- If CI changes are needed, update GitHub Actions workflows accordingly
Notes:
- If gh hits auth/rate issues mid-run, prompt the user to re-authenticate with
gh auth login, then retry.