メニュー
Mark the current branch's draft PR as ready for review
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | pr-open-for-review |
| description | Mark the current branch's draft PR as ready for review |
Use this skill when the user asks to run the migrated command pr-open-for-review or invokes $pr-open-for-review.
Take the current branch's PR out of draft mode and mark it ready for review.
gh pr view --json number,url,title,isDraft \
--jq '"\(.number)|\(.isDraft)|\(.title)|\(.url)"'
If no PR exists for the current branch, stop and report: "No open PR found for branch $(git branch --show-current)."
isDraft is false, report that the PR is already open for review and stop.isDraft is true, proceed.gh pr ready <number>
✅ PR #<number> is now ready for review
<pr_url>
To reverse — convert a ready PR back to draft — run gh pr ready <number> --undo.
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.