be-commit

Create git commits from staged changes with validated messages and security scanning.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/ohmyhotelco/hare-cc-plugins --skill be-commit-ohmyhotelco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: be-commit
Source: https://github.com/ohmyhotelco/hare-cc-plugins/tree/main/backend-webflux-plugin/skills/be-commit
Command: npx skills add https://github.com/ohmyhotelco/hare-cc-plugins --skill be-commit-ohmyhotelco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, convention-compliant commit messages is tedious, and committing unreviewed or unverified code can break a team's review pipeline. This Skill automates commit creation from staged changes while enforcing message standards, scanning for secrets, and checking pipeline status before anything lands in history. ## Core Features & Use Cases - Validated Commit Messages: Drafts subject and body following strict rules (imperative mood, 50-char subject, 72-char body lines, no prefixes), then validates against a checklist before committing. - Security Scanning: Runs a pre-commit script that scans staged changes for secrets and dangerous files, aborting the commit if issues are found. - Pipeline Status Guards: Warns when features are in unreviewed or unverified states, and verifies the staged tree matches the tree that was actually reviewed. - Use Case: After finishing a backend feature and staging your changes, invoke the skill to get a convention-compliant commit with an optional topic hint, knowing secrets and stale review states are checked automatically. ## Quick Start Stage your changes with git add, then ask the assistant to create a commit from the staged changes with an optional topic hint.

Frequently Asked Questions about be-commit

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

FAQPage Schema
How do I create a git commit with a validated message?▼

Stage your changes with git add, then invoke the skill with an optional topic hint. It analyzes the staged diff, drafts a message following project conventions, validates it against a checklist, and commits via git commit -F with a heredoc.

How to scan staged changes for secrets before committing?▼

The skill runs a pre-commit-check script in security mode that scans staged changes for secrets and dangerous files. If the scan reports issues, the findings are shown and the commit is aborted before any message is drafted.

Can I generate a short commit message with subject only?▼

Yes, pass the short argument to generate only the subject line and skip the body. The subject still follows all rules: imperative mood, maximum 50 characters, no prefix, and uppercase start.

What happens if a pre-commit hook rejects the commit?▼

If git commit exits non-zero, the skill treats the commit as failed, rolls back the progress-file updates it made, shows the command output verbatim, and stops. No commit is reported and the staging area is left untouched.

Does the skill stage files automatically before committing?▼

No, it never runs git add on paths the user has not staged. The only exception is refreshing an already-staged progress file with its own updated fields; all other staging remains under user control.