Stage local changes and create conventional commit messages with prefixes.
npx skills add https://github.com/heyAyushh/stacc --skill commit-heyayushh
Please help me install this Agent Skill. Skill: commit Source: https://github.com/heyAyushh/stacc/tree/main/configs/commands/skills/commit Command: npx skills add https://github.com/heyAyushh/stacc --skill commit-heyayushh
This Skill commits local changes on the current branch using the conventional commit message format.
Review changes with git status, stage with git add -A, and commit with git commit -m "<prefix>: <summary>"
High-intent search queries and answers about installing and using this skill.
To format conventional commit messages, you stage local changes and apply a standardized prefix like feat, fix, or docs followed by a summary. This ensures your git history adheres to standardized team formatting.
Supported conventional commit prefixes for your version control workflow include feat, fix, refactor, perf, docs, build, chore, and style, allowing you to categorize staged changes accurately.
Yes, you can stage all local changes with a single command and commit them without pushing to a remote branch. This workflow prepares your local commits for review before any remote synchronization.
Yes, Git tooling is required to create conventional commits on your current branch. The process relies on standard Git commands to stage changes and generate the formatted commit messages locally.
The best way to automate standard commit prefixes for team workflows is using a tool that applies conventional formats like feat or fix automatically. This enforces consistent version control messages across the team.
GLaDO8Generates concise Git commit messages and commits staged or unstaged changes.
JasonLoAutomate version bumping, Git tagging, and pushing to remote repositories.
AnveioAutomate GitHub pull request creation, reviews, feedback, and merges via gh CLI.
SeloraHomesCreate git commits with conventional type prefixes and lowercase subjects.
