Commit Changes
Create commits following the Conventional Commits specification.
Format
code
<type>(<scope>): <subject> <body>
Types
- •
feat: New feature - •
fix: Bug fix - •
docs: Documentation only - •
style: Formatting, no code change - •
refactor: Code change that neither fixes a bug nor adds feature - •
test: Adding or updating tests - •
chore: Build process, auxiliary tools, libraries
Rules
- •Subject line: imperative mood, lowercase, no period, max 50 chars
- •Body: explain why not what (the diff shows what)
- •Wrap body at 72 characters
- •Reference issues when relevant: "Fixes #123"
- •Do NOT add "Generated by Claude", co-author lines, or any AI attribution
Process
- •Run
git statusandgit diff --stagedto understand changes - •If nothing staged, stage relevant files with
git add - •Determine appropriate type and scope from the changes
- •Write commit message following the format
- •Execute the commit
Examples
code
feat(speech): add wake word detection node Enable voice activation with configurable wake phrase. Defaults to "Hey Ross" for the ROS2 pun.
code
fix(audio): handle missing microphone gracefully Previously crashed when USB mic disconnected. Now logs error and waits for device reconnection.
code
chore: update dependencies for Python 3.12 Faster-whisper 1.0 requires updated numpy. Also pins silero-vad to stable version.