メニュー
Create a Graphite branch with staged changes. Use when the user mentions Graphite, gt create, stacked PRs, or wants to create a branch for review using Graphite's workflow. Runs gt create with appropriate flags and commit message.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | gt-create |
| description | Create a Graphite branch with staged changes. Use when the user mentions Graphite, gt create, stacked PRs, or wants to create a branch for review using Graphite's workflow. Runs gt create with appropriate flags and commit message. |
Graphite is a CLI tool and web platform for managing stacked pull requests. It wraps git and provides commands like gt create, gt submit, and gt sync to make working with stacks of dependent PRs easier. Stacked PRs help break large changes into smaller, reviewable pieces while maintaining dependencies between them.
git statusgit diff HEADgit branch --show-currentgit log --oneline -5Create a new Graphite branch with the current changes using gt create.
Run gt create with:
-a flag to stage all changes (no need for separate git add)--no-interactive flagNote: When surgically staging specific files or hunks, use git add manually instead of -a.
Use bash's $'...' syntax to embed literal newlines in the commit message. This properly interprets \n as actual newlines:
gt create -a --no-interactive -m $'Short summary of changes\n\nLonger explanation of why this change was made, any relevant context, etc.\n\n- Bullet points work too'
To skip pre-commit hooks, use --no-verify. Note that Graphite uses --no-verify, not -n (which is what git commit uses).
# Stage all changes
gt create -a --no-interactive --no-verify -m $'summary\n\noptional body'
# Or stage specific files first
git add src/foo.ts src/bar.ts && gt create --no-interactive --no-verify -m $'summary'
If the user provided specific instructions via $ARGUMENTS, incorporate them into the commit message. Otherwise, derive an appropriate message from the changes.
User instructions: $ARGUMENTS
An Electric Monk engine — two subagents believe fully committed positions on the user's behalf while the orchestrator performs structural contradiction analysis and synthesis. By outsourcing belief work to agents, the user operates from a belief-free position where they can analyze the structure of the contradiction rather than being inside either side. Use when the user wants to stress-test an idea, resolve a genuine tension, build a deeper mental model, or make a high-stakes decision where the tradeoffs are unclear. Works across any domain — technical architecture, product strategy, philosophy, personal decisions, risk analysis, policy, creative direction.
Read a web page as clean markdown using defuddle. Use when the user asks to read a URL, fetch documentation, look up a web page, or when you need to reference online content for the current task.
This skill should be used when the user asks to "create AGENTS.md", "update AGENTS.md", "maintain agent docs", "set up CLAUDE.md", or needs to keep agent instructions concise. Enforces research-backed best practices for minimal, high-signal agent documentation.
Create a detailed handoff document for continuing work in a new session. Use when the user says handoff, wants to save their progress, needs to continue later, or is ending a session with unfinished work. Writes a comprehensive summary to .claude/handoffs/ for pickup by a future agent.
Resume work from a previous handoff session. Use when the user says pickup, wants to continue previous work, or mentions a handoff file. Lists available handoffs from .claude/handoffs/ or loads a specific one to continue where the previous session left off.
General Graphite knowledge and reference. Use when the user asks about Graphite concepts, stacking workflows, CLI commands, troubleshooting, or how Graphite differs from vanilla git. Not for specific actions like creating branches (use gt-create for that).