commit
Create a conventional commit using chez_commit. Use when the user asks to commit changes. Do not EVER use
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Create a commit using chez_commit, which stages the specified files and commits them.
Usage
chez_commit ...
Valid Tags (in order of preference)
- feat - New feature, feature improvement, or feature removal
- fix - User-facing bug fix (not linting errors unless they caught a real bug)
- ref - Refactor/restructure production code without changing external behavior. IMPORTANT: Only use 'ref' when there are ZERO user-facing changes. If users would notice any difference in behavior, use 'feat' or 'fix' instead.
- chore - Other changes (build scripts, CI/CD, deps, linting, formatting, documentation) not modifying production code
Instructions
- Run
chez_commit <tag> "<message>" <file>... - The specified files will be staged automatically
- The message can contain newlines for multi-line commits
- NEVER mention "Claude" or "Claude Code" in commit messages - write as if a human authored the commit
Example
chez_commit feat "Add user authentication
This adds login and logout functionality." src/auth.py src/login.py
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-01-26
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!