Menu
Commit the current changes with a Conventional Commits message.
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
Record an architecture/design decision as an ADR (Architecture Decision Record) in the target repository's docs/adr/. Use when the user wants to document a design decision, its alternatives and consequences, or says "record this decision" / "write an ADR".
Generate a self-contained HTML manual-testing guide for an implemented change — environment setup, a visual test-flow diagram, step-by-step scenarios with expected results, and interactive pass/fail checkboxes with a Markdown results export. Use when the user wants to verify an implementation by hand, asks "how do I test this", or wants a verification document for a feature/branch/PR.
Generate a self-contained HTML onboarding tour of a repository — architecture diagram, directory map, key flow walkthroughs, and a recommended reading order — for new team members. Use when the user wants onboarding material, asks for a codebase overview/architecture tour, or wants to explain a repo to someone new.
Generate a self-contained HTML code-review guide for the current changes — big-picture overview, architecture diagram of affected modules, a file/class responsibility map, and an annotated change walkthrough — so a reviewer can grasp the whole implementation before diving into the diff. Use when the user wants review material for a branch/PR, asks to "explain the changes for review", or wants a visual summary of what was implemented where.
Investigate a reported bug to its root cause — reproduce, trace the code path, identify the defect with evidence, assess blast radius, and propose fix candidates without changing code. Use when the user reports or pastes a bug/defect/unexpected behavior and wants it diagnosed, or asks "why is X happening".
Capture a reusable, non-obvious project insight into the rules home where it will auto-inject in future sessions. Use when investigation or implementation surfaces knowledge worth persisting (a gotcha, a convention, the "why" behind a decision), or when the user asks to remember a project learning.
| description | Commit the current changes with a Conventional Commits message. |
| disable-model-invocation | true |
| name | commit-changes |
Commit the current changes with a Conventional Commits message.
Assess the working tree. Run git status --short and git diff (or git diff --staged if changes are already staged) to see what changed and why.
Stage changes. If nothing is staged, run git add ..
Draft the message. Pick a Conventional Commits prefix based on the diff:
feat — new featurefix — bug fixdocs — documentation onlystyle — formatting, missing semicolons, etc.refactor — code change that neither fixes a bug nor adds a featuretest — adding or correcting testschore — build process or auxiliary tool/library changes
Then write a short imperative description in <type>: <description> format. Use English unless the user requested another language.Commit. Run git commit -m "<message>".
git not in a repository: stop and report.