commit

SKILL.md

Commit changes in atomic steps, then finalise and clean up the feature branch when requested.

Use a different emoji only if it more precisely matches the change.

Include both a concise change summary and the decision rationale. Include:

Create atomic commits with explicit user approval, using emoji-prefixed titles and `feat`/`fix`/`chore` commit types. Use when staging changes, proposing commit batches, writing high-signal commit messages in imperative mood, committing iteratively, finalising a feature branch by merging/closing/deleting it, and capturing durable memory updates during commit/finalise decisions. Source: kelvinz/cobb.

View raw