Enforce atomic conventional commits after each verified development step.
npx skills add https://github.com/ashwnn/agent-config --skill commit-often
Please help me install this Agent Skill. Skill: commit-often Source: https://github.com/ashwnn/agent-config/tree/main/skills/commit-often Command: npx skills add https://github.com/ashwnn/agent-config --skill commit-often
Atomic, traceable git history is often neglected in multi-step work, leading to large, brittle commits and difficult rollbacks.
Create a new commit immediately after each completed step to preserve an atomic history.
High-intent search queries and answers about installing and using this skill.
Enforce atomic commits by staging only changes related to the current step and committing immediately after verification to maintain a clean, reversible history. This process targets multi-step implementations by requiring per-step verification and incremental commits.
Conventional commits provide automatic messaging guidance to standardize commit history, ensuring traceable and structured version control. They isolate each step's changes in its own commit to facilitate quick reversions and minimize noise.
Keep your Git history clean and reversible by enforcing step-level commits after each completed, verified step. This isolates changes in their own commits, facilitating quick reversions and preventing large, brittle commits.
Yes, you can selectively stage files for each step to improve Git traceability. Only changes related to the current step are committed, which minimizes noise and maximizes traceability across the version control history.
Your Git rollback fails because large, unstructured commits bundle multiple changes, making them brittle. Enforcing atomic, step-level commits isolates each step's changes, facilitating quick and safe reversions.
wwsunAnalyze git changes and propose atomic Conventional Commit plans for user approval.
AndrewDrygaCreate semantic version tags from changelogs and push them to Git.
whincInspect working tree changes, stage them selectively, and generate Conventional Commits messages.
maggitPlan and execute non-interactive git rebase operations with safety checks.
