commit

Generates commit messages from git diffs matching repository conventions and commits staged changes.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/basedgod55hjl/vsbrax --skill commit-basedgod55hjl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/basedgod55hjl/vsbrax/tree/main/src/vs/sessions/skills/commit
Command: npx skills add https://github.com/basedgod55hjl/vsbrax --skill commit-basedgod55hjl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, meaningful commit messages is tedious and often results in vague entries like "fix stuff" that pollute repository history. This Skill analyzes your actual diff and the repository's existing commit style to produce convention-compliant messages automatically. ## Core Features & Use Cases - Convention Detection: Samples recent repository commits and your own commit history to detect the style in use (Conventional Commits, Gitmoji, ticket-prefixed, or free-form) and matches it. - Diff-Driven Messages: Generates a subject line (≤72 characters) plus an optional body explaining why the change was made, based on the staged diff rather than a file-by-file inventory. - Safety Guardrails: Never amends, force-pushes, skips hooks, or discards changes without explicit approval, and flags potential secrets before committing. - Use Case: After finishing a feature branch with mixed staged and unstaged edits, ask for a commit and receive a properly formatted message that references the ticket number from your branch name. ## Quick Start Ask the assistant to commit my current changes with a message that follows this repository's commit style.

Frequently Asked Questions about commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a commit message from my git diff automatically?▼

Stage your changes and ask for a commit. The Skill runs git log to detect the repository's message convention, inspects the staged diff with git diff --cached, and drafts a subject line and optional body that match the detected style before committing.

How to write commit messages that follow Conventional Commits style?▼

The Skill samples the last 20 repository commits and your last 10 personal commits to detect whether the project uses Conventional Commits, Gitmoji, ticket prefixes, or free-form messages, then generates new messages in that same convention.

Can it commit unstaged changes or only staged ones?▼

If changes are already staged, only those are committed and unstaged edits are left alone. If only unstaged changes exist, everything is staged with git add -A before committing. A clean working tree stops the workflow.

Does it ever amend commits, force-push, or skip pre-commit hooks?▼

No. The Skill never amends existing commits, force-pushes, uses --no-verify, or disables GPG signing without explicit user approval. If pre-commit hooks modify files, it reports the changes and asks before committing follow-up edits.

What happens if my changes contain secrets or generated files?▼

The Skill checks the diff for obvious secrets or generated artifacts that should not be committed. If anything looks risky, it pauses and asks the user for confirmation before proceeding with the commit.