commit

Inspect git state and create conventional commits with safe staging.

8|1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/mrclrchtr/skills --skill commit-mrclrchtr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/mrclrchtr/skills/tree/main/skills/commit
Command: npx skills add https://github.com/mrclrchtr/skills --skill commit-mrclrchtr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, git, and includes scripts (resource) components.

What problem does it solve?

Commit hygiene and consistency in a project across teams by ensuring commits follow the repository's conventional style.

Core Features & Use Cases

  • Conventional-commit style enforcement: guides and enforces commit messages to match the project's conventions.
  • Repo-state snapshot: uses a dedicated script to generate a JSON snapshot of the current git state for informed staging.
  • Guardrails and safety: prevents dangerous options like --no-verify, --amend, or unintended pushes without confirmation.

Quick Start

Stage your changes and create a conventional commit using the commit skill.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create conventional commits automatically with git?

To create conventional commits automatically, this Skill inspects your repository state and guides staging and commit messaging to align with the project's conventions. It enforces guardrails to prevent dangerous git options like --no-verify.

How does this git commit workflow handle staging multiple files?

This git commit workflow handles multiple files by generating a JSON snapshot of the current repository state. This snapshot provides the context needed for careful grouping before staging and committing changes.

Can I use git amend or push without verification when committing?

You cannot use git amend or push without verification within this workflow. The Skill enforces safety guardrails that prevent dangerous options like --no-verify and --amend without explicit confirmation.

Do I need jq installed to enforce conventional commit styles?

Yes, you need jq installed alongside git to enforce conventional commit styles. The Skill relies on jq to process the JSON repository state snapshot used for informed staging and commit generation.

What is the best way to commit changes across multiple branches safely?

The best way to commit changes safely across multiple branches is to use a workflow that inspects the repository state and applies safety guardrails. This Skill prevents unintended pushes and enforces conventional commit styles for multi-branch work.