commit

Create git commits with Conventional Commits and structured bodies.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes git commits to follow Conventional Commits with a structured body, ensuring clear intent, changelog readability, and an AI review. It also enables decomposed multi-commit changesets via OneFlow Option 3 to preserve a clean, linear history while grouping related changes.

Core Features & Use Cases

  • Enforce Conventional Commits format for subject and scope
  • Generate a structured body including an intent paragraph, a [--- Changes ---] section, and a [--- AI Review ---] section
  • Support OneFlow Option 3 for decomposed multi-commit workflows to group related changes
  • Enforce preflight rules (no pushes without explicit authorization, branch naming conventions, and safety checks)
  • Offer retroactive grouping of related commits into a single feature bubble when appropriate

Quick Start

Draft a conventional-commit message with a structured body for the latest change.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate git commit messages with conventional commits format?

Automating git commit messages with conventional commits format involves enforcing a structured subject and scope, alongside a three-part body containing an intent paragraph, a changes section, and an AI review section to ensure clear history.

What is the best way to group related git commits into a clean linear history?

Grouping related git commits into a clean linear history uses OneFlow Option 3 to decompose multi-commit changesets, preserving auditable history while grouping related changes into a single feature bubble when appropriate.

How does an AI review section work inside a conventional commit body?

An AI review section inside a conventional commit body automatically generates an AI review of the staged changes, appending it to the structured commit body to provide an auditable assessment alongside the intent and changes sections.

Can I enforce preflight rules for git pushes and branch naming conventions?

Enforcing preflight rules for git pushes and branch naming conventions is supported, applying strict safety checks that block pushes without explicit authorization and validate branch names before committing changes.

Do I need specific dependencies to generate structured conventional commits?

Generating structured conventional commits requires no specific external dependencies, as the automation manages the three-part commit body and preflight checks natively within the existing development workflow.

Why use a structured commit body for conventional commits?

Using a structured commit body for conventional commits standardizes intent and changelog readability, ensuring every change includes an intent paragraph, a detailed changes section, and an AI review for clear auditability.