Generate a conventional-commit plan for pending git changes in COMMITS.md.
npx skills add https://github.com/ajbarea/techne --skill auto-commit-ajbarea
Please help me install this Agent Skill. Skill: auto-commit Source: https://github.com/ajbarea/techne/tree/main/plugins/techne/skills/auto-commit Command: npx skills add https://github.com/ajbarea/techne --skill auto-commit-ajbarea
It solves the problem of turning a messy working tree into a clean, reviewable set of conventional commits without guessing how to group related changes or losing track of what should land together.
Run the skill to generate a plan in COMMITS.md, then say go when you want it to execute the branch → commits → push → PR workflow.
High-intent search queries and answers about installing and using this skill.
To group pending git changes into conventional commits, this skill analyzes your working tree diffs and writes a structured commit plan into COMMITS.md, allowing you to review coherent commit batches before anything is executed.
Yes, you can automatically create a branch and pull request from a dirty working tree by approving the generated commit plan with an explicit go command, which triggers the branch, commit, push, and PR workflow.
Conventional commit planning works by analyzing both staged and unstaged file diffs, grouping related changes by appropriate types like feat or fix, and assigning realistic scopes based on file paths and recent repo history.
The best way to review commit batches before shipping is generating a plan-only COMMITS.md file that structures your pending changes into reviewable conventional commits without immediately modifying your repository state.
No, regenerating a commit plan does not lose your custom notes. The skill performs state-aware regeneration by comparing HEAD and a tree fingerprint, specifically preserving your ## Notes section when updating the plan.
The commit plan excludes the COMMITS.md file from git diffs to prevent circular commits, ensuring the generated plan file itself is never included as a tracked change in its own proposed commit batches.
asermaxAnalyze git status and diffs to propose grouped conventional commit messages.
eriknovakCreate a conventional commit, push the branch, and open a GitHub pull request.
eroslifestyleAutomate Git branch lifecycle, semantic commits, and pull request workflows.
indexnetworkCommit staged code changes in logical chunks using Conventional Commits.
