commit-changes

Commits changes with semantic messages, security and code review gates, then pushes the branch.

Updated Jul 14, 2026
One-click install
npx skills add https://github.com/quanthubbr/tron-claude-config --skill commit-changes-quanthubbr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-changes
Source: https://github.com/quanthubbr/tron-claude-config/tree/main/managed/skills/commit-changes
Command: npx skills add https://github.com/quanthubbr/tron-claude-config --skill commit-changes-quanthubbr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It enforces a disciplined Git workflow so that no commit reaches a branch without semantic commit messages, a secret-leak scan, a security review, and a code review, preventing raw or unsafe changes from being pushed. ## Core Features & Use Cases - Semantic commit grouping: Splits changes into cohesive Conventional Commits, creates a feature branch automatically when on main/master, and keeps planning artifacts in a separate final docs commit. - Mandatory review gates: Runs /security-review and /code-review on the staged diff and blocks the bypass token until no CRITICAL or HIGH findings remain. - Leak scanning and safe push: Verifies no .env files, credentials, or PII are staged, then creates the .claude/.commit-authorized token required by the pre-commit and pre-push hooks before pushing. - Use Case: After finishing a feature, invoke the skill to have your changes grouped into clean commits, scanned for leaked secrets, reviewed, and pushed to a properly named branch ready for a pull request. ## Quick Start Ask the AI to commit and push the current working tree changes using the commit-changes workflow.

Frequently Asked Questions about commit-changes

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

FAQPage Schema
How do I commit changes with semantic commit messages in Git?▼

Group changes into cohesive units and commit each with a Conventional Commits message like "feat: add login form", keeping subjects under 100 characters. Stage only the files for each unit with git add <paths> rather than git add -A.

How to scan Git commits for leaked secrets before pushing?▼

Run a secret scanner such as gitleaks on the staged diff and verify no real .env files, tokens, API keys, or credentials appear in the changes. If anything leaks, unstage or amend the commit and never push the exposed data.

Why is my git commit blocked by the pre-commit hook?▼

The hook blocks commits unless the .claude/.commit-authorized bypass token exists. Create it with touch .claude/.commit-authorized only after security review and code review pass, and recreate it before each commit since the hook deletes it.

Can I commit directly to the main or master branch?▼

No, the workflow refuses to commit on main or master. It creates a new branch first using the pattern type/short-kebab-description, such as fix/null-pointer-crash, then commits and pushes there.

What are the limitations of automated commit workflows?▼

The workflow depends on the bypass token and review skills being present, so commits fail without them. It also forbids force-push, --author overrides, and AI attribution trailers, which may conflict with some team conventions.