Menü
Create a conventional commit for the current changes.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
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.
Run the following commands to understand the current state:
git status
This shows staged, unstaged, and untracked files.
git diff
This shows unstaged changes.
git diff --staged
This shows changes that are already staged.
git log --oneline -10
This shows recent commits so you can match the existing style.
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.
Stage the files to be committed. Prefer adding specific files by name rather than using git add . or git add -A,
which can accidentally include sensitive files or large binaries:
git add <file1> <file2> ...
Create the commit with the approved message:
git commit -m "<approved message>"