commit-discipline

Enforce conventional commit formatting and diff constraints before git push.

Updated May 14, 2024
One-click install
npx skills add https://github.com/wagnerra23/oimpresso.com --skill commit-discipline-wagnerra23
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-discipline
Source: https://github.com/wagnerra23/oimpresso.com/tree/main/.claude/skills/commit-discipline
Command: npx skills add https://github.com/wagnerra23/oimpresso.com --skill commit-discipline-wagnerra23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

commit-discipline prevents messy pull requests by enforcing a strict, predictable commit/PR standard before any git commit or push.

Core Features & Use Cases

  • One PR = one intent to avoid mixing refactors, features, fixes, and docs into the same change.
  • Diff and content guardrails to keep changes small (≤300 lines when possible) and block PII/secrets from being added to commit messages, logs, or code.
  • Conventional commits + task references to improve downstream automation (including MCP task updates) using consistent PR titles and bodies.

Quick Start

Ask your AI assistant to help you format your next change as a single intent PR with a conventional commit message, a ≤300-line diff goal, and task refs like Refs: COPI-21, with no PII or secrets included.

Frequently Asked Questions about commit-discipline

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

FAQPage Schema
How do I enforce conventional commit formatting and PII redaction in git pull requests?▼

Conventional commit formatting and PII redaction are enforced before git commit and push operations. The commit-discipline guardrails ensure each PR maps to a single intent and block secrets from entering commit messages, logs, or code.

What is the best way to keep pull request diffs under 300 lines?▼

Keeping pull request diffs under 300 lines is achieved by enforcing strict diff guardrails before pushing. This ensures each change maps to a single intent, preventing mixed refactors and features from inflating the diff size.

How does MCP task reference handling work with conventional commit messages?▼

MCP task reference handling works by requiring task references like Refs: COPI-21 in conventional commit messages and PR bodies. This consistency improves downstream automation and enables automatic MCP-compatible task status updates.

Can I use pull request hygiene rules for both feature development and documentation updates?▼

Yes, pull request hygiene rules can be used for both feature development and documentation updates. The standard applies uniformly across features, fixes, docs, tests, and sprint-linked work to maintain predictable PR standards.

Why should I avoid mixing refactors and feature fixes in the same git commit?▼

Mixing refactors and feature fixes in the same git commit should be avoided because it violates the one PR equals one intent principle. Separating them maintains focused, review-ready changes and ensures downstream automation processes correctly.

Does commit-discipline work with GitHub CLI gh PR operations?▼

Commit-discipline works with GitHub CLI gh PR operations. It enforces its hygiene checks and conventional commit standards before any gh PR operations execute in development workflows.