Attach contextual decisions and learnings to code changes during commits.
npx skills add https://github.com/ActiveMemory/ctx --skill ctx-commit
Please help me install this Agent Skill. Skill: ctx-commit Source: https://github.com/ActiveMemory/ctx/tree/main/internal/tpl/claude/skills/ctx-commit Command: npx skills add https://github.com/ActiveMemory/ctx --skill ctx-commit
Commit messages often lose the reasoning behind design choices. This skill attaches contextual decisions and learnings to code changes so future teammates understand the context.
ctx add decision and ctx add learning to persist rationale alongside the code.Invoke ctx-commit after meaningful work to capture decisions and learnings alongside the code.
High-intent search queries and answers about installing and using this skill.
To preserve decisions and learning with every git commit, use automated workflow checks that prompt you to record rationale after a successful commit. This ensures the context trail accompanies meaningful code changes across feature, bugfix, and refactor workflows.
Yes, you can enforce pre-commit validations to verify staged changes align with the intended context. Pre-commit checks ensure builds pass when code changes occur, preventing invalid commits before prompting for decision or learning documentation.
The best way to document design rationale alongside code changes is to attach contextual decisions after a successful commit. Post-commit prompts offer commands to persist decisions and learnings, ensuring future teammates understand the reasoning behind the work.
Yes, this workflow automation supports bugfix and refactor contexts. It covers feature development, bugfixes, and refactors, ensuring the context trail accompanies meaningful commits and deployments across all standard development workflows.
You record a decision after a successful commit by responding to the after-commit prompt. The automation offers specific commands to add decisions and learnings, persisting the rationale directly alongside the newly committed code changes.
You should attach context to commit messages because they often lose the reasoning behind design choices. Attaching contextual decisions and learnings ensures future teammates understand the context and rationale accompanying the code changes.
SteveGJonesAutomates pre-commit validation checks including tests, static analysis, and conventional commit enforcement.
techygargCreate and append per-feature context docs capturing decisions and constraints.
ivyStage intended files and write conventional, why-focused commit messages.
rseGenerate a concise commit message from `git diff --cached` output.