ワンクリックで
github
Use this skill when addressing GitHub PR comments.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use this skill when addressing GitHub PR comments.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | github |
| description | Use this skill when addressing GitHub PR comments. |
| allowed-tools | Bash(*scripts/get-unresolved-comments.sh) |
| compatibility | Requires gh CLI to work |
DO NOT resolve review threads. The user will resolve them manually.
When addressing review feedback:
The user maintains control over comment resolution to ensure proper review workflow.
Run the script to fetch unresolved review comments for the current branch's PR:
This script automatically:
gh api repos/OWNER/REPO/pulls/PR_NUMBER/comments --jq '.[] | {path, line, body}'
gh pr view PR_NUMBER --json title,body,comments,reviews
Use when starting feature work that needs isolation from current workspace, before executing implementation plans, or when reviewing an existing branch (e.g. a PR) without switching away from the current branch. It creates isolated git worktrees under `.worktrees/`.
Use this skill when working on terminal UI rendering, interactive CLI prompts, ANSI color output, terminal screenshots, Bubble Tea/Lip Gloss/Huh/Glamour, curses-style apps, or CLI tests that depend on TTY behavior.
Use this skill when you're working with golang code.
Use whenever asked to create GitHub Pull Request.
Use when writing, rewriting, or updating a pull request description. Use this skill's explicit PR template unless the user provides a different template for the current task, keep the result concise and human-readable, explain why the change exists, and ask the user for motivation before updating the PR when the user has not explicitly provided it.
Use this skill whenever writing, editing, reviewing, or deciding whether to add code comments, docstrings, inline comments, or internal function documentation in any programming language. Use it even when the task only mentions "comments", "docs in code", "docstrings", "document this function", or "explain this helper".