Menu
Create a well-formed Conventional Commit. Use when the user says "commit", "commit my changes", or asks you to save progress.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | commit |
| description | Create a well-formed Conventional Commit. Use when the user says "commit", "commit my changes", or asks you to save progress. |
| disable-model-invocation | true |
git status
git diff --stat
If the tree is clean, tell the user and stop.
Before committing, verify:
.env or secret files stagedconsole.log, TODO, or FIXME in staged filesnode_modules stagedIf violations found, list them and stop. Do not commit.
Run the project's lint and type-check commands (from BOOTSTRAP_FORM.md tooling section).
If they fail, stop and report.
Choose the correct type from .claude/rules/commit-rules.md.
Draft the commit message and show it to the user for confirmation before committing.
Format:
<type>(<scope>): <description>
[body if needed]
git add -p # stage interactively if multiple logical changes
git commit -m "<message>"
Print the commit hash and subject line. Ask if the user wants to push.
Onboard an existing codebase into the starter kit. Use when the user says "adopt this project", "add the kit to my existing repo", or "set up the kit on existing code".
Close a feature group as a milestone. Writes docs, proposes E2E tests, and runs a go/no-go gate. Use when the user says "/milestone", "this group is done", or the agent detects all items in a group are complete.
Scaffold a new project from BOOTSTRAP_FORM.md. Use when the user says "bootstrap the project", "set up the project", or runs /bootstrap for the first time.
Pick and build features from SPEC.md by priority. Use when the user says "build the next feature", "/new-feature", "work on X", or "build the <group> group".
Plan and execute a code refactor with preserved behaviour. Use when the user asks to refactor, clean up, simplify, extract, or reorganise existing code without changing what the app does.
Update SPEC.md and docs/DECISIONS.md to reflect recent code changes. Use after completing a feature, or when the user says "sync docs", "update the spec", or "log this decision".