commit

Enforce conventional commits and pre-commit checks for local and CI workflows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/fyodoriv/agentbrew --skill commit-fyodoriv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/fyodoriv/agentbrew/tree/main/skill-plugins/dev/commit
Command: npx skills add https://github.com/fyodoriv/agentbrew --skill commit-fyodoriv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commits changes following conventional commits format with pre-commit checks (tests, type check, lint, format). Enforces 72-char headers, ticket numbers, and small self-contained units. Don't use for creating PRs (use pr) or pushing (use pr iterate).

Core Features & Use Cases

  • Enforces conventional commits across the codebase
  • Runs pre-commit checks, including tests, type checks, lint, and format
  • Guides branch naming and updates lockfiles when package.json changes (if applicable)

Quick Start

Run the pre-commit suite and ensure your commit message adheres to the conventional-commits standard.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I enforce conventional commits with pre-commit checks like lint and type validation?

To enforce conventional commits with pre-commit checks, you can use a skill that automatically validates commit messages, runs tests, executes type checks, and applies lint and formatting rules before changes are committed.

What is the conventional commits format requirement for commit headers?

Conventional commits format requires headers to be 72 characters or fewer. The validation process also mandates including ticket references and keeping commits as small, self-contained units to maintain a clean project history.

How do I run pre-commit checks for tests and type checking in a local git workflow?

Running pre-commit checks in a local git workflow involves executing a validation suite that runs tests, type checks, lint, and formatting. This ensures code quality standards are met before changes are committed to the repository.

Does this conventional commits validation work in CI pipelines and team projects?

Yes, conventional commits validation applies to local git workflows, CI pipelines, and team projects. It enforces consistent commit message formatting and pre-commit checks across all development environments and collaborative codebases.

When should I not use a conventional commits enforcement tool?

You should not use conventional commits enforcement tools for creating pull requests or pushing code. These tools are specifically designed for validating commit messages and running pre-commit checks, not for managing remote branch interactions.

Can I automatically update lockfiles when package.json changes during a commit?

Yes, when package.json changes, the commit validation process can automatically update lockfiles if applicable. It also guides branch naming conventions to ensure repository consistency before the pre-commit checks are executed.