Commits

Commits stance: commit as you go

For repos without a review gate — planning repos, knowledge bases, dotfiles — commit incrementally as logical units finish, not once at the end and not line by line, and push after committing so the work is durable. Conventional Commits still apply. Hold off on secrets, on content the user called throwaway, and mid-edit of a file within one turn. Application repos with a review gate are different: branch, open a PR, and let the gate do its job.

Commits stance: Conventional Commits, gated pushes, attributed

Conventional Commits for every commit, in every repo: type(scope): summary. Before pushing, run the repo’s quality gate on HEAD in the exact checkout you will push — whatever its agent instructions name, or what CI runs if they name nothing. Never push to a default branch directly: branch, open a PR, merge through it, unless a repo without a review gate says otherwise. Keep the tool’s Co-Authored-By and generated-with lines. AGENTS.md and CLAUDE.md are one file, symlinked — check which side is real before editing.

Commits stance: Conventional Commits, gated pushes

Conventional Commits for every commit, in every repo: type(scope): summary. Before pushing, run the repo’s quality gate on HEAD in the exact checkout you will push — whatever its agent instructions name, or what CI runs if they name nothing. Never push to a default branch directly: branch, open a PR, merge through it, unless a repo without a review gate says otherwise. No attribution trailers. AGENTS.md and CLAUDE.md are one file, symlinked, so different agents cannot drift.

Commits stance: off

No standing commit convention is in force. Follow whatever the repo you are in specifies, and ask before pushing to a default branch.

An off variant still links a one-line file, so /context shows the stance is set and silent rather than missing.