Graphite Stacked PRs with Conventional Commits

Use this skill to turn local changes into well-scoped conventional commits inside Graphite stacked pull requests. In a Graphite or stacked-PR workflow, it replaces a generic git commit workflow by combining diff analysis, staging, commit message generation, Graphite branch creation, stack updates, PR submission, and recovery guidance.

Safety Rules

• Inspect the worktree before changing git state: git status --short.
• Preserve user changes. Do not revert, discard, or overwrite changes you did not make unless the user explicitly asks.
• Never commit secrets such as .env, credentials, tokens, private keys, or generated private config.
• Never update git config unless the user explicitly asks.
• Never skip hooks with --no-verify unless the user explicitly asks.
• Never force push to main, master, or trunk.
• Treat git reset, git rebase, gt delete -f, and force pushes as destructive or high-risk. Use them only when they are necessary and the user intent is clear.
• If hooks fail, fix the issue and update the Graphite branch with gt modify; do not bypass hooks.

Quick Reference