contextual-commit

What problem does it solve?

Commits and diffs document what changed but rarely capture why decisions were made, what constraints existed, or which alternatives were rejected. This Skill helps preserve the development reasoning — intent, decisions, rejections, constraints, and learnings — directly in commit messages so future maintainers and agents understand the rationale behind code changes.

Core Features & Use Cases

• Structured Commit Bodies: Enforces a Conventional Commit subject plus typed, scoped action lines (intent, decision, rejected, constraint, learned) in the body.
• Context-Aware Guidance: Advises when to write action lines based on staged vs unstaged changes and when context is missing to avoid fabrication.
• Use Case: When finishing a feature or fixing a bug, produce a commit that records the user's intent, chosen approach, discarded alternatives, and important constraints so replaying or reflecting on the session is easier.

Quick Start

Use the contextual-commit skill to write a commit for staged changes that captures intent, decisions, and constraints.