commit

Creates conventional commits from staged git changes with a confirmation gate.

3|Updated May 2, 2026
One-click install
npx skills add https://github.com/JuanTrujilloDev/agent-config-template --skill commit-juantrujillodev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/JuanTrujilloDev/agent-config-template/tree/main/cursor/.claude/skills/commit
Command: npx skills add https://github.com/JuanTrujilloDev/agent-config-template --skill commit-juantrujillodev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, well-structured commit messages is repetitive and error-prone, and accidental commits on protected branches can disrupt a team's workflow. This Skill inspects staged changes, drafts a conventional commit message, and enforces a confirmation step before committing. ## Core Features & Use Cases - Conventional Commit Drafting: Analyzes git diff --staged and recent history to produce messages like feat(scope): description or fix(scope): description. - Confirmation Gate: Asks the user to approve the message before committing in gated mode; in autonomous mode it commits only after judge review, while push and PR confirmations are never skipped. - Protected Branch Safety: Refuses to commit on the default branch and instructs the user to check out a typed branch first. - Use Case: After staging a bug fix, invoke the skill to review the diff, get a properly scoped conventional commit message, confirm it, and commit in one guided flow. ## Quick Start Ask the assistant to commit the staged changes with a conventional commit message and confirm the proposed message before it runs git commit.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I write a conventional commit message for staged changes?▼

Stage your changes with git add, then invoke the commit skill. It runs git diff --staged and git log to match your repo's style, drafts a message like feat(scope): description, and asks for your confirmation before committing.

How to enforce one logical change per commit in git?▼

The skill inspects the staged diff and flags mixed unrelated changes before committing. If it detects multiple concerns, it offers to split the staging so each commit contains a single logical change.

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

No. The skill never commits on the default branch. If you are on it, the skill stops and tells you to check out a typed branch first, protecting the mainline from accidental commits.

Does the commit confirmation get skipped in autonomous mode?▼

In autonomous mode the message confirmation is skipped and micro-commits proceed after judge review passes. However, push and pull request confirmations are never skipped in any mode.

Why did my commit stop with a protected branch warning?▼

The skill detected you are on the repository's default branch, where direct commits are forbidden. Create and check out a typed feature or fix branch, re-stage your changes, and run the commit flow again.