Menu
Creates atomic, well-formatted conventional commits with automatic type and scope detection. Invoke with /commit.
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
Performs a review of recent commits to a branch and looks for meaningful gaps in test coverage.
Generates comprehensive PR descriptions and creates pull requests with proper context from git history. Invoke with /pr.
Apply BaseCode practices to improve the readability of code — naming, dead code, nested code, comments, and more.
Apply the BaseCode Dead Code practice — remove commented-out code, unused code, unreachable code, and abandoned feature branches to reduce noise and improve readability.
Apply the BaseCode Naming practice — avoid abbreviations, follow conventions, leverage context, and use domain vocabulary to maximize human signal in names.
Apply the BaseCode Nested Code practice — flatten structure using guard clauses, conditional boolean returns, and higher-order functions to bring the primary action to the top level.
| name | commit |
| description | Creates atomic, well-formatted conventional commits with automatic type and scope detection. Invoke with /commit. |
You create atomic, well-formatted conventional commits with automatic type and scope detection.
git status --porcelain
If no changes, report "No changes to commit" and exit.
Run git status --short and git diff --stat. Determine files modified, change nature, and logical grouping.
| Pattern | Type |
|---|---|
| New functionality | feat |
| Bug fix | fix |
| Restructuring without behaviour change | refactor |
| Documentation only | docs |
| Test files only | test |
| Build/config/tooling | chore |
| Performance improvement | perf |
| Formatting/whitespace | style |
Detect from changed files: domain folder name, component name, api, db, tests, config, or omit if multiple areas.
Only include files changed within the coding session. Files created or modified outside of the session must not be included in the commit scope.
Never include files within a repository's .ai/ directory unless explicitly requested by the user.
Stage each file by full path. NEVER use git add ., git add -A, or directory-level staging.
Format: {type}({scope}): {description} (max 72 chars, imperative mood, no capitalisation, no period).
Optional body: blank line after subject, bullet points for multiple changes, explain what and why. No more than 3-4 short sentences if required.
git commit -m "$(cat <<'EOF'
{type}({scope}): {description}
- {change 1}
- {change 2}
EOF
)"
Return commit hash, type, scope, description, and files committed.