Menu
Create a well-formatted git commit with conventional commit messages
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
Debug issues using E2E tests, log analysis, and dev server management
Query ClickHouse observability logs over HTTP API
Iterate on bug hypotheses using Playwright repro scripts, structured logs, and source code analysis
Address unresolved inline diff comments and mark them resolved
Run a long task across multiple agent contexts using breadcrumb progress files
Recursively decompose a task into sub-plans with dependency ordering, then execute in topological waves
| name | commit |
| description | Create a well-formatted git commit with conventional commit messages |
| argument-hint | [message] |
When creating commits:
Stage only relevant changes (use git add -p for partial staging if needed)
Write clear, conventional commit messages following the format:
feat: for new featuresfix: for bug fixesdocs: for documentation changesrefactor: for code refactoringtest: for test additions/changeschore: for maintenance tasksIf $ARGUMENTS is provided, use it as the commit message
Otherwise, analyze staged changes and generate an appropriate message
Always show the user the proposed commit before executing