| name | commit |
| description | Use this skill when the user asks to commit, save, or persist their code changes to version control and describe current changes. |
| metadata | [object Object] |
Please follow the steps below to commit your changes with jj (describe current changes).
Run jj log -n 5 to see working copy changes and all current changes.
For each non-empty change without a description (shows as "(no description set)"):
- Run
jj diff -r <change_id> --gitto view the diff - Read related files if needed to understand the context
- Use
jj describe -r <change_id>to add a meaningful description
If changes were made during this conversation, use conversation context to write accurate descriptions.
Commit Message Format
In order to ensure good formatting, ALWAYS pass the commit message via a HEREDOC:
jj describe -m "$(cat <<'EOF'
Commit message here.
EOF
)"
Message Style
Follow the Conventional Commits specification:
<type>(<scope>): <description>
Types:
feat: New featurefix: Bug fixdocs: Documentation changesstyle: Code style changes (formatting, no logic change)refactor: Code refactoring (no feature or fix)test: Adding or updating testschore: Build process, dependencies, or tooling changes
Examples:
feat(cli): add --verbose flag for debug outputfix(llm): handle API timeout errors gracefullydocs(readme): update installation instructionsrefactor(core): simplify session state management