メニュー
Create or update a GitHub pull request for the current branch. Use when the user invokes `$pr-create`, asks to create/open a PR, or wants the current branch pushed and described as a draft PR.
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-create |
| description | Create or update a GitHub pull request for the current branch. Use when the user invokes `$pr-create`, asks to create/open a PR, or wants the current branch pushed and described as a draft PR. |
Create a GitHub PR for the current branch. If a PR already exists, use $pr-update-desc to refresh its description instead.
Use the pr-style skill for title format, body template, labels, assignment, and draft policy. Follow those rules for the PR title, body, and label handling.
Run:
remote=$(git remote | head -1)
branch=$(git branch --show-current)
default_branch=$(git symbolic-ref refs/remotes/${remote}/HEAD 2>/dev/null | sed "s|refs/remotes/${remote}/||" || echo "main")
echo "remote=${remote} branch=${branch} default=${default_branch}"
If branch equals default_branch, stop and report:
Cannot create a PR from the default branch (`<default_branch>`).
Run:
gh pr list --head "${branch}" --state open --json number,url,title --jq '.[0] | "\(.number)|\(.title)|\(.url)"'
PR #<number> already exists, use $pr-update-desc to update the description, then stop.Check whether the remote branch exists:
git ls-remote --heads "${remote}" "${branch}"
If no remote branch exists, push with an explicit refspec:
git push -u "${remote}" "${branch}:${branch}"
If the remote branch exists, push the current local branch to it:
git push "${remote}" "${branch}:${branch}"
Get branch commits:
git log --oneline "${default_branch}..HEAD"
Get the high-level diff:
git diff --stat "${default_branch}...HEAD"
Use these outputs with pr-style to generate the PR title and body.
Map conventional commit prefixes in the branch log using the pr-style label table. Validate candidate labels against the repo:
gh label list --json name --jq '.[].name'
Apply only labels that exist. If no valid labels exist, omit label flags.
Create a draft PR assigned to the current GitHub user:
gh pr create --draft --assignee @me --title "<title>" --body "$(cat <<'EOF'
<generated description>
EOF
)"
If valid labels were detected, include them with repeated --label "<label>" flags.
Output:
Created PR #<number> (draft)
<pr_url>
Labels: <applied labels or none>
Assigned: @me