Agent skill
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 this agent skill to your Project
npx add-skill https://github.com/yurake/skills/tree/main/.curated/gh-address-comments
Metadata
Additional technical details for this skill
- short description
- Address comments in a GitHub PR review
SKILL.md
PR Comment Handler
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.
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.
1) Inspect comments needing attention
- Run scripts/fetch_comments.py which will print out all the comments and review threads on the PR
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
3) If user chooses comments
- Apply fixes for the selected comments
Notes:
- If gh hits auth/rate issues mid-run, prompt the user to re-authenticate with
gh auth login, then retry.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
issue-create
GitHub Issue を作成する手順。依頼を受けたとき、.github/ISSUE_TEMPLATE の内容に応じてテンプレを選び、必須項目を埋めて GitHub MCP(issue_write/create)で Issue を作成する。
ci-fail-followup
PR 作成後に .github/workflows/ci.yml が失敗したときの対応手順。ローカルで pytest 全ケースを実行し、エラー有無で分岐。エラーがあれば修正して commit-push スキルでコミット・プッシュ、無ければ GitHub Actions のログを確認して原因を特定する。
review-rules
セッションの会話から恒久的な振る舞いルールを抽出し、AGENTS.md と突き合わせて追加すべきものを提示する。出力は rules と agents_md_patch の二部構成。
pr-create
PR 作成手順を自動化するためのガイド。依頼を受けたとき、または 参照しているTODOファイル の「PR 作成」以外が完了したタイミングでタイトル・本文整形、テンプレ適用、MCP での PR 作成を行う。
architecture-patterns
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.
test-risk-analyzer
あらゆる言語/スタックで潜在バグリスクを洗い出し、追加すべきテストケースを提案する。未テストのエッジケース探索や安全性確認、カバレッジ強化のテスト案提示を求められたときに使用する。
Didn't find tool you were looking for?