commit

Run a pre-commit checklist for documentation, tests, and linting.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/cirne/zmail --skill commit-cirne
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/cirne/zmail/tree/main/.cursor/skills/commit
Command: npx skills add https://github.com/cirne/zmail --skill commit-cirne

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-commit checks ensure code quality and documentation standards are met before changes are committed, reducing post-commit defects and review cycles.

Core Features & Use Cases

  • Pre-commit documentation review: Verify updated docs align with changes.
  • Test coverage assurance: Ensure tests exist and pass for new/modified code.
  • Linting and formatting: Enforce style and syntax consistency across the codebase.
  • Change validation guidance: Provide a clear workflow for addressing failures and resubmitting.

Quick Start

Run the full commit checklist to verify documentation, tests, linting, and quality gates before committing.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I enforce a pre-commit checklist for documentation, tests, and linting?

You can enforce a pre-commit checklist by automating quality gates that verify documentation updates, test coverage, and linting before changes are committed, ensuring unresolved issues are flagged with clear guidance.

What is the best way to ensure test coverage and documentation standards before committing code?

The best way to ensure test coverage and documentation standards is to run an automated pre-commit validation workflow that checks if tests exist and pass, and whether updated docs align with the code changes.

Can I enforce code quality gates without setting up complex pre-commit dependencies?

Yes, this pre-commit quality gate enforcement requires no external dependencies and operates independently to validate linting, tests, and documentation alignment before each commit.

How do I handle change validation failures when my pre-commit checks fail?

When pre-commit checks fail, the validation workflow provides clear guidance on unresolved issues, outlining the specific steps needed to address failures before resubmitting your commit.

Why should I automate pre-commit checks instead of reviewing code quality manually?

Automating pre-commit checks reduces post-commit defects and review cycles by systematically enforcing style consistency, test coverage, and documentation alignment before changes enter the repository.

Does the commit quality gate workflow enforce linting and formatting across the entire codebase?

Yes, the pre-commit checklist enforces linting and formatting to maintain style and syntax consistency across the codebase, preventing inconsistent code from being committed.