commit

Automate pre-commit quality checks and semantic commits across multi-language repositories.

6|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/maschad/my-claude --skill commit-maschad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/maschad/my-claude/tree/main/skills/commit
Command: npx skills add https://github.com/maschad/my-claude --skill commit-maschad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating pre-commit quality checks across multiple languages can be error-prone and time-consuming. This skill automates repository detection, runs build, test, lint, and format steps, and then creates semantic commits to ensure code quality and changelog clarity.

Core Features & Use Cases

  • Automatic repository detection to select appropriate build/test workflows for Node.js, Python, Go, Rust, and Java projects.
  • Deterministic quality pipeline: build, test, lint, and format in a fixed order to catch issues early.
  • Semantic commit creation: generate conventional-commit-style messages with optional scopes to standardize history.
  • Pre-commit guardrails: block or guide commits when failures occur, ensuring stable releases.

Quick Start

Run the commit skill on a repository to automatically validate changes and generate a semantic 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 pre-commit quality checks across a multi-language repository?

Automating pre-commit quality checks across multiple languages requires detecting the repository environment and orchestrating build, test, lint, and format steps in a deterministic pipeline to catch issues before creating semantic commits.

How do I generate semantic commit messages automatically after running tests and formatting?

To generate semantic commit messages automatically, a pre-commit pipeline runs build and lint validations, then formats changes into conventional-commit-style messages with optional scopes to standardize repository history and changelog clarity.

Does this pre-commit automation tool support Node.js, Python, Go, Rust, and Java projects?

Yes, this pre-commit automation tool supports Node.js, Python, Go, Rust, and Java projects by performing automatic repository detection to select and apply the appropriate build, test, lint, and format workflows for each language.

What is the best way to enforce conventional commits and prevent broken code from being merged?

The best way to enforce conventional commits is by applying pre-commit guardrails that block commits when build, test, lint, or format failures occur, ensuring only validated code changes proceed with standardized semantic messages.

Why should I use an automated quality pipeline instead of manually running build and lint commands?

Using an automated quality pipeline prevents human error by executing build, test, lint, and format steps in a fixed deterministic order, ensuring consistent pre-commit validation and semantic commit formatting across multi-language repositories.