Automates Git commits with confirmation and project-style messages.
npx skills add https://github.com/n0an/VivaDicta --skill commit-to-git
Please help me install this Agent Skill. Skill: commit-to-git Source: https://github.com/n0an/VivaDicta/tree/main/.claude/skills/commit-to-git Command: npx skills add https://github.com/n0an/VivaDicta --skill commit-to-git
This Skill ensures changes are committed to Git following project guidelines with a proper confirmation flow, reducing risky or misformatted commits.
Ask for confirmation, then commit the staged changes following the project guidelines.
High-intent search queries and answers about installing and using this skill.
To commit changes with a confirmation prompt, this guided flow reviews your repository status and diff, stages selected files, formats the commit message, and requires explicit confirmation before finalizing the commit to Git.
Yes, you can stage specific files for a partial commit. The guided flow supports selective file staging and scope control, allowing you to review the diff of individual changes and confirm only the files you want to include in the commit.
To enforce commit message guidelines, this flow applies project-style formatting and attribution rules to your messages. It structures the commit message during the staging process to ensure hygiene before final confirmation.
Yes, you can push immediately after committing changes. Once the commit is confirmed and finalized in your local development workflow, the tool optionally offers to push the updates directly to your remote Git repository.
The best way to review a Git diff before staging is using an automated workflow that displays your current repository status and file changes. This guided process enforces reviewing the diff and prompts for confirmation prior to any staging or commit action.
You should review repository status before a Git commit to prevent risky or misformatted updates. Reviewing the status and diff ensures you only stage intended changes, enforcing project guidelines and reducing the likelihood of accidental commits.
gittowerCreate convention-compliant Git commits from staged or unstaged changes.
AndrewDrygaCreate semantic version tags from changelogs and push them to Git.
sitharaj88Generate and execute conventional Git commit messages from staged changes.
74nu5Generate conventional commit messages from diffs and stage files.
