Stage Git changes by intent and propose conventional commit messages.
npx skills add https://github.com/hve4638/hve-cc-marketplace --skill stage-hve4638
Please help me install this Agent Skill. Skill: stage Source: https://github.com/hve4638/hve-cc-marketplace/tree/main/common/skills/stage Command: npx skills add https://github.com/hve4638/hve-cc-marketplace --skill stage-hve4638
Stage changes by intent and propose consistent commit messages without performing the commit.
Review your changes with git status and git diff, then stage by intent using explicit git add <path> commands.
High-intent search queries and answers about installing and using this skill.
You can stage changes by intent using explicit git add <path> commands instead of bulk adds, which prevents unintended modifications from entering your Git workflow and keeps multi-file changes organized.
Yes, the tool inspects your repository history to enforce conventional commit style and proposes 1–3 candidate commit messages aligned with your repo's conventions without executing the commit.
The best way to maintain consistent commit messages is to validate against existing repository history, enforcing conventional commit style and proposing aligned message candidates before any actual commit occurs.
No, this staging workflow does not execute the commit automatically; it stops before committing to present candidate messages, giving you full control over the final repository history.
Handle multi-file changes by staging with explicit git add <path> commands, avoiding bulk adds to ensure only intended modifications are staged and proposed for your commit message.
GLaDO8Generates concise Git commit messages and commits staged or unstaged changes.
mhattingpeteStage, commit, and push code changes with conventional commit messages.
sunLeeeValidate Git commit messages against Conventional Commits rules.
mattstrubleAnalyze git history and staged changes to craft conventional commit messages.
