Git Discipline
Never let agentic speed destroy repository hygiene.
Mandatory Steps
- Stage intentionally — only the files that belong in this logical change.
- Write a Conventional Commit message:
feat:,fix:,refactor:,docs:,test:,chore:,perf:- Scope when useful:
feat(api): ... - Body that explains why, not just what.
- Create or update branch following
feature/,fix/, etc. - Never commit directly to main.
- Rebase or merge cleanly before opening PR.
- PR description should reference the plan or relevant skills used.
Agent Behavior
- After edits, offer to run
git diff --stagedand propose a commit. - If history is messy, propose a rebase plan (never force-push without confirmation).
- When multiple logical changes are staged together, split them.
Verification
git log --oneline -10should tell a clear story.- Each commit should be buildable/testable in isolation where practical.