Stats
Actions
Tags
From devloop
Guides on creating reviewable atomic commits with principles like one logical change per commit, size guidelines (XS-L), splitting large changes, hygiene best practices, and devloop integration. Useful when preparing or reviewing commits.
How this skill is triggered — by the user, by Claude, or both
Slash command
/devloop:atomic-commitsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Creating reviewable commits that capture logical units of work.
Creating reviewable commits that capture logical units of work.
Plan tasks map to commits:
When using /devloop:ship, you can choose:
Example plan:
- [x] Task 1.1: Create config skill
- [x] Task 1.2: Add parsing script
- [x] Task 1.3: Update session hook
Atomic commits would create:
feat(devloop): create local-config skill
feat(devloop): add config parsing script
feat(devloop): update session-start hook
| Size | Lines | When to Commit |
|---|---|---|
| XS | <50 | Single fix, config change |
| S | 50-200 | One feature, one refactor |
| M | 200-500 | Feature with tests |
| L | >500 | Consider splitting |
Devloop tasks typically align with S-M size commits.
Instead of one large commit:
Or with devloop: One commit per phase.
/devloop:freshnpx claudepluginhub zate/cc-plugins --plugin devloopOrganizes git workspace changes into clean, atomic commits following conventional formats. Activates after features, refactors, or explicit commit requests.
Guides git commit strategies emphasizing small, frequent atomic commits that narrate development history. Use for planning commits, timing decisions, and message patterns.
Manages Git commit workflow using Conventional Commits format with safety protocols. Creates, validates, executes commits; handles hooks, PRs, and safety checks before operations.