git-toolkit

Purpose

Governs the structure, format, and accuracy of how changes are described across git commits and pull requests. Routes each task to the right capability.

When to trigger

Activation cues live in two places only: the frontmatter description (lifecycle intent — about to commit, opening or updating a PR, preparing a release — plus explicit asks) and the Trigger cells of the six lifecycle tables under Capability routing. Match the task against those tables; this file keeps no separate trigger list.

Architecture

Two layers:

• Router (this SKILL.md): triggers, principles, capability routing. Loads always.
• Capabilities (capabilities/<name>/capability.md): one per operation. Each is self-sufficient — load just the one whose trigger matches.

Shared references at this skill's root hold the canonical format spec, trailer rules, merge-policy semantics, etc. Every capability links to them via ../../references/<file>.md rather than duplicating.