commit

Create conventional commits with pre-flight formatting, linting, and secret checks.

4|Updated Dec 31, 2025
One-click install
npx skills add https://github.com/Taketo-Yoda/uv-sbom --skill commit-taketo-yoda
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Taketo-Yoda/uv-sbom/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/Taketo-Yoda/uv-sbom --skill commit-taketo-yoda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of creating high-quality commits by embedding automated checks and standardized messages.

Core Features & Use Cases

  • Enforces English commit messages for consistency across the codebase.
  • Runs mandatory pre-flight checks (formatting, static analysis, and secret scans) before a commit is created.
  • Generates Conventional Commits compliant messages and appends Co-Authored-By trailers when requested.
  • Enforces branch policies to prevent direct commits to protected branches and suggests using feature branches for development workflows.

Quick Start

Run the commit workflow to automatically perform pre-flight checks and produce a conventional commit message.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate conventional commit messages and pre-commit checks?

To automate conventional commit messages and pre-commit checks, this Skill runs mandatory pre-flight validations including formatting, static analysis, and secret scans before generating a compliant commit message for your feature branch or hotfix.

What are conventional commits and how do pre-flight checks work?

Conventional commits are a standardized message format for codebase consistency. Pre-flight checks work by running formatting, linting, and secret scans automatically before a commit is created, ensuring code quality and preventing sensitive data leaks.

Can I enforce English commit messages and branch policies in my git workflow?

Yes, you can enforce English commit messages and branch policies in your git workflow. This Skill validates branch policies to prevent direct commits to protected branches and suggests using feature branches for development.

Does this conventional commit workflow support Co-Authored-By trailers?

Yes, this conventional commit workflow supports Co-Authored-By trailers. It generates compliant commit messages and automatically appends the Co-Authored-By trailers when requested as part of the commit workflow.

What happens if pre-commit secret scans or linting checks fail?

If pre-commit secret scans or linting checks fail, the commit workflow is designed to halt. These mandatory pre-flight checks must pass successfully before a conventional commit message is generated and the commit is created.