メニュー
Address GitHub PR review comments by fetching, evaluating, fixing, committing, and resolving feedback. Use when invoked as `$pr-resolve-feedback` or when the user asks to resolve PR feedback.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
End-of-day — draft and post daily comments for tracked tickets missing a comment
Morning startup workflow for daily notes, yesterday summary, agenda, status comments, meeting sections, and daily branch setup. Use when invoked as `$work-start` or when the user asks to start the work day.
Track a Linear ticket or GitHub PR in today's daily note with fields and timestamped activity. Use when invoked as `$work-track` or when the user asks to track a work item.
Start work on a Linear ticket by gathering context, planning, creating a branch/worktree, implementing, testing, opening a draft PR, and updating Linear. Use when invoked as `$linear-plan` or when the user asks to start a Linear ticket.
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.
| name | pr-resolve-feedback |
| description | Address GitHub PR review comments by fetching, evaluating, fixing, committing, and resolving feedback. Use when invoked as `$pr-resolve-feedback` or when the user asks to resolve PR feedback. |
Address GitHub PR review feedback.
Use the existing resolve-feedback skill for the detailed implementation workflow.
If the user provided a PR URL or comment URL, pass that target through to resolve-feedback.
If no target is provided, detect the current branch's PR first:
gh pr view --json url --jq '.url'
Then process unresolved comments for that PR.