skills.rest
kaneshin
kaneshinCOMMUNITY
Explore all skills by this author →
Website𝕏@kaneshin0120GitHub

Commit Discipline

Validates tests, lint warnings, and conventional commit messages before git commit.

Updated Jan 11, 2026
Search Tags:#git#workflow#commit#quality#pre-commit#lint#tests
One-click install
npx skills add https://github.com/kaneshin/incubator --skill commit-discipline
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Commit Discipline
Source: https://github.com/kaneshin/incubator/tree/main/plugins/dev-methodology/skills/commit-discipline
Command: npx skills add https://github.com/kaneshin/incubator --skill commit-discipline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps ensure every git commit adheres to quality standards by enforcing tests pass, lint cleanliness, and clear, focused messages.

Core Features & Use Cases

  • Pre-commit checks that all tests pass across JavaScript/TypeScript, Python, Rust, and Go projects.
  • Enforces single logical unit of work per commit with clear, conventional messages.
  • Guides users through a repeatable process before committing, including addressing warnings.

Quick Start

Use the commit discipline skill to validate changes and generate a compliant commit before saving to version control.

Frequently Asked Questions about Commit Discipline

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

FAQPage Schema
How do I enforce quality standards before committing code?▼

Commit discipline enforces quality standards by validating that tests pass, lint warnings are addressed, and commit messages are clear and conventional. It guides you through pre-commit checks across JavaScript, TypeScript, Python, Rust, and Go projects before changes are saved to version control.

Can I use pre-commit hooks to validate tests and lint in my workflow?▼

Pre-commit hooks validate tests and lint compliance automatically during commit preparation. This skill enforces those checks as a repeatable process, catching issues before they reach version control and ensuring a single logical unit of work per commit.

What's the best way to write clear, focused commit messages?▼

Conventional commit messages paired with single logical units of work improve clarity and maintainability. This skill enforces proper formatting and guides you to structure commits so each one represents one cohesive change, making history readable and reversible.

Do I need to set up commit validation separately for each language?▼

No. This skill applies commit discipline across languages and toolchains with standard test suites, including JavaScript, TypeScript, Python, Rust, and Go. It works with existing test infrastructure without language-specific configuration overhead.

How do pre-commit checks prevent broken code from reaching version control?▼

Pre-commit validation runs tests and lint checks before commits are accepted, blocking changes that fail quality gates. This ensures only tested, lint-clean code with clear messages reaches the repository, reducing downstream issues in PRs and branches.

When should I enforce commit discipline in my development workflow?▼

Commit discipline applies during commit preparation on feature branches and PRs before pushing to version control. It's most effective as an early gate, catching quality issues locally rather than in code review or CI pipelines.

Related Skills

Explore More Software Engineering Skills→
motlinmotlin
14

precommit

Run precommit checks on code changes and report failures.

Community
Intermediate
cbleckercblecker
5

creating-pull-request

Automate GitHub pull request creation with branch pushing and PR metadata.

Community
Basic
cbbkrd-techcbbkrd-tech

ln-742-precommit-setup

Configure Git hooks with Husky, lint-staged, commitlint, and pre-commit.

Community
Advanced
arpitnatharpitnath
86

code-review

Automate pre-commit code reviews with structured feedback and blocking commits.

Community
Advanced