Write commits that explain the reasoning behind changes, not just what changed. Use when committing code that involves architectural decisions, tradeoffs, or non-obvious choices that future developers need to understand.
When to use this skill
- Committing an architectural change
- Documenting a design decision
- Explaining why a tradeoff was made
Core concepts
This skill provides guidance on contextual commits best practices, patterns, and common pitfalls. It is designed to be loaded on demand when a relevant task is detected.
Installation
curl -LO https://opencode-skills.example/downloads/workflow/contextual-commits.zip
unzip contextual-commits.zip -d ~/.config/opencode/skills/Restart OpenCode — the skill loads automatically.
When it triggers
- committing an architectural change
- documenting a design decision
- explaining why a tradeoff was made