git-workflow

Installation
SKILL.md

Git Workflow

Commit conventions

Always use conventional commit format:

type(scope): short imperative subject

Optional body explaining WHY, not what (the diff already shows what).

Subject rules (all mandatory):

  • Imperative mood: fix:, not fixed: or fixes:
  • Lowercase first word after the colon, no trailing period
  • Max ~72 characters — if it doesn't fit, the subject is doing the body's job
  • Say what changed and why it matters: fix: correct off-by-one in keyframe lookup beats both fix bug (vague) and a paragraph (belongs in the body)

Types: feat (new feature), fix (bugfix), refactor, perf, docs, test, chore, build, ci, revert. Scope is optional but required in multi-package repos — fix(interpolator): ... beats bare fix: ... when several areas exist. Omit it in single-purpose repos rather than inventing noise.

Installs
1
Repository
phenpen/perski
First Seen
Oct 31, 2026