Analyze Changes: Run git diff --staged, git diff, and git status
Stage All: Use git add -A if needed
Understand Context: What changed, why, type, scope, patterns
Check Branch: If on main/master, create descriptive branch first
Generate Message: Subject ≤72 chars, imperative, conventional type
Execute: git commit -m "<message>"
Commit Message Format
<type>(<scope>): <subject>
<body>
Types
Type
Use Case
feat
New feature
fix
Bug fix
docs
Documentation only
style
Formatting, no code change
refactor
Code restructuring
test
Adding/fixing tests
chore
Build, config, dependencies
Rules
Imperative mood ("Add feature" not "Added feature")
No trailing period
Subject ≤72 characters
Body explains what/why, not how
No co-author credits or "Generated with..." tags
Quality Standards
Meaningful to someone reading git log months later
Avoid generic: "fix bug", "update code"
Group related changes conceptually
Flag if changes too diverse for single message
Edge Cases
Situation
Action
No changes
Inform user nothing to commit
Incomplete changes
Flag observation to user
On main/master
Create feature branch first
Too diverse
Note to user, suggest splitting
Examples
Example 1: Feature Commit
feat(auth): add JWT token refresh mechanism
- Implement automatic token refresh before expiration
- Add refresh token storage in secure cookie
- Include retry logic for failed refresh attempts
Example 2: Bug Fix Commit
fix(api): prevent null pointer on empty response
Handle case where API returns empty body instead of
throwing unhandled exception in response parser.
Example 3: Refactor Commit
refactor(streamer): extract common mock to shared helper
- Move mockGRPCStreamClient to mock_query.go
- Consolidate 4 duplicate mock implementations
- Reduce test file coupling
Example 4: Multi-scope Commit
test(streamer): consolidate redundant tests
- Remove TestRemoteStream_Success (duplicate of Recv_EventDelivery)
- Merge Close_Idempotent into TestRemoteStream_Close
- Delete tests with no real assertions
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: syntrixbase-syntrix-commit-changes3description: Commit Changes4---5# Commit Changes67## Instructions891. **Analyze Changes**: Run `git diff --staged`, `git diff`, and `git status`102. **Stage All**: Use `git add -A` if needed113. **Understand Context**: What changed, why, type, scope, patterns124. **Check Branch**: If on main/master, create descriptive branch first135. **Generate Message**: Subject ≤72 chars, imperative, conventional type146. **Execute**: `git commit -m "<message>"`1516## Commit Message Format1718```19<type>(<scope>): <subject>2021<body>22```2324### Types2526| Type | Use Case |27|------|----------|28| `feat` | New feature |29| `fix` | Bug fix |30| `docs` | Documentation only |31| `style` | Formatting, no code change |32| `refactor` | Code restructuring |33| `test` | Adding/fixing tests |34| `chore` | Build, config, dependencies |3536### Rules3738- Imperative mood ("Add feature" not "Added feature")39- No trailing period40- Subject ≤72 characters41- Body explains **what/why**, not how42- No co-author credits or "Generated with..." tags4344## Quality Standards4546- Meaningful to someone reading git log months later47- Avoid generic: "fix bug", "update code"48- Group related changes conceptually49- Flag if changes too diverse for single message5051## Edge Cases5253| Situation | Action |54|-----------|--------|55| No changes | Inform user nothing to commit |56| Incomplete changes | Flag observation to user |57| On main/master | Create feature branch first |58| Too diverse | Note to user, suggest splitting |5960## Examples6162### Example 1: Feature Commit6364```65feat(auth): add JWT token refresh mechanism6667- Implement automatic token refresh before expiration68- Add refresh token storage in secure cookie69- Include retry logic for failed refresh attempts70```7172### Example 2: Bug Fix Commit7374```75fix(api): prevent null pointer on empty response7677Handle case where API returns empty body instead of78throwing unhandled exception in response parser.79```8081### Example 3: Refactor Commit8283```84refactor(streamer): extract common mock to shared helper8586- Move mockGRPCStreamClient to mock_query.go87- Consolidate 4 duplicate mock implementations88- Reduce test file coupling89```9091### Example 4: Multi-scope Commit9293```94test(streamer): consolidate redundant tests9596- Remove TestRemoteStream_Success (duplicate of Recv_EventDelivery)97- Merge Close_Idempotent into TestRemoteStream_Close98- Delete tests with no real assertions99```100101---102> Converted and distributed by [TomeVault](https://tomevault.io/claim/syntrixbase) — claim your Tome and manage your conversions.103<!-- tomevault:4.0:skill_md:2026-04-14 -->
Run npx skillmds@latest add tomevault-io/syntrixbase-syntrix-commit-changes in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Commit Changes It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.
tomevault-io