commit-craft

Craft atomic commits and PR descriptions following Conventional Commits conventions.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/lgili/skillex --skill commit-craft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-craft
Source: https://github.com/lgili/skillex/tree/main/skills/commit-craft
Command: npx skills add https://github.com/lgili/skillex --skill commit-craft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Atomic and well-described commits, together with clear PR descriptions, reduce review time and improve code history quality across teams.

Core Features & Use Cases

  • Create atomic commits that map to a single logical change with a clear scope.
  • Enforce Conventional Commits style for commit messages and provide guidance for PR descriptions.
  • Generate concise PR descriptions that explain the rationale, impact, and test plan for reviews.

Quick Start

Provide a concise, atomic commit message that captures the change and rationale.

Frequently Asked Questions about commit-craft

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

FAQPage Schema
How do I write conventional commits for atomic Git changes?

To write conventional commits for atomic Git changes, craft a concise commit message that captures a single logical change and its rationale. This enforces pre-commit checks and ensures clear scope mapping for code reviews.

What is the best way to generate PR descriptions for code reviews?

The best way to generate PR descriptions is to automatically create concise summaries that explain the rationale, impact, and test plan for reviews. This reduces review time and improves code history quality across teams.

Can I enforce pre-commit checks for feature and refactor branches?

Yes, you can enforce pre-commit checks for feature, fix, refactor, and chore changes across branches. The checks apply Conventional Commits conventions and PR description guidance to maintain code history quality.

How do I structure atomic commits that map to a single logical change?

To structure atomic commits, provide a clear scope for each commit so it maps to a single logical change. This approach follows Conventional Commits conventions and improves pull request workflows.

Does this work for branch management and pull request workflows?

Yes, this applies to branch management and pull request workflows by enforcing pre-commit checks and generating concise PR descriptions that explain rationale, impact, and test plans for feature, fix, refactor, and chore changes.

Why use conventional commits for Git workflow and code review?

Use conventional commits for Git workflow and code review to reduce review time and improve code history quality. Atomic and well-described commits provide clear scope mapping and concise rationale for teams.