Git Workflow and Versioning

Use this skill when

Operating rules

1. Confirm the current branch and working tree.
2. Keep the branch scope aligned with the approved change.
3. Group related changes into atomic commits.
4. Write commit messages that explain behavior and intent.
5. Review the diff and tests before committing.
6. Use version changes that match user-visible compatibility impact.
7. Record why a meaningful engineering rule changed.

MUST

• Do not discard user changes.
• Do not use destructive Git commands without explicit authorization.
• Keep unrelated formatting and cleanup out of the task branch.
• Make commits reviewable and internally coherent.
• Ensure the changelog describes meaningful behavior and reasons.

SHOULD

• Prefer one behavior or migration step per commit.
• Keep generated artifacts out of source unless the project requires them.
• Use patch, minor, and major version changes consistently.
• Preserve a clean diff before handoff.
• Mention verification in the commit or handoff summary.

Versioning

• PATCH: wording, examples, ambiguity removal, or non-decision-changing corrections.
• MINOR: new rules, references, eval cases, or capabilities that preserve the philosophy.
• MAJOR: a change to a core engineering principle or a breaking public workflow.

Routing

Verification