Menu
Create a conventional commit for the current changes.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Take an iteration and execute it: dispatch /implement agents per phase, always sequentially (e.g. /orchestrate <iteration-id>).
Take an iteration and execute it: dispatch /implement agents per phase with git worktree isolation for parallel work (e.g. /orchestrate <iteration-id>).
Take an iteration and execute it: dispatch /implement agents per phase with jj workspace isolation for parallel work (e.g. /orchestrate <iteration-id>).
Promote a gest task to a GitHub Issue (e.g. /promote-task <id>).
Explore a rough idea with the user, clarify requirements, and draft a spec. Also decomposes large specs into smaller ones (e.g. /brainstorm "offline mode", /brainstorm <gest-id>).
Implement a single issue: write code, verify, review, format, and commit (e.g. /implement <gest-id>).
| name | commit |
| description | Create a conventional commit for the current changes. |
Create a commit following project conventions using Git Butler.
Run the following commands to understand the current state:
git status
This shows working tree status (read-only git command, safe to use).
git diff
This shows all working directory changes (read-only git command, safe to use).
git log --oneline -10
This shows recent commits so you can match the existing style (read-only git command, safe to use).
git-butler branch list
This shows all virtual branches and their status. Identify which branch owns the changes you want to commit.
Follow the conventions in docs/dev/commits.md:
<type>(<scope>): <description>
[optional body]
[optional footer(s)]
Types: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert
Rules:
! after type/scope for breaking changesGitHub Issue references:
If the current work relates to a gest task, check whether the task has github-issue metadata:
cargo run -- task show <id> --json
If the metadata object contains a github-issue key, include a footer referencing that issue (e.g. Closes #42). If
there is no github-issue metadata, do not add an issue reference.
Present the draft commit message to the user for approval. Do not commit without confirmation.
Commit the changes on the target virtual branch using Git Butler:
git-butler branch commit <branch-name> -m "<approved message>"
Never use git commit directly -- it can desync Git Butler's state. All commits must go through git-butler branch commit.