skills.rest
led8
led8COMMUNITY
Explore all skills by this author →
GitHub

commit

Generate Conventional Commit messages with type(scope): summary format for git changes.

Updated Aug 23, 2026
Search Tags:#git#push#pre-commit#version-control#commit-message#conventional-commits
One-click install
npx skills add https://github.com/led8/.codex --skill commit-led8
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/led8/.codex/tree/main/skills/commit
Command: npx skills add https://github.com/led8/.codex --skill commit-led8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Poorly formatted, vague, or inconsistent git commit messages that make code review, tracing, and automation harder, and accidental pushes or skipped pre-commit fixes that introduce noise or security issues.

Core Features & Use Cases

  • Conventional Commits guidance: Prescribes type(scope): summary structure and examples for common commit types (feat, fix, docs, chore, etc.).
  • Scope selection & message quality: Helps infer appropriate scopes and concise imperative summaries to keep history readable and actionable.
  • Pre-commit and push workflow: Advises how to stage files, respond to pre-commit hook failures, amend commits, and when to push versus commit-only; useful for feature work, bug fixes, and release prep.

Quick Start

Commit staged changes using a Conventional Commits message like feat(auth): add OAuth2 support and do not push unless I explicitly ask.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I write a conventional commit message for my git changes?▼

To write a conventional commit message, use the type(scope): summary format, such as feat(auth): add OAuth2 support, to ensure clear and consistent commit subjects for code review and tracing.

What should I do when pre-commit hooks fail during a git commit?▼

When pre-commit hooks fail during a git commit, you should handle hook auto-fixes and resolve linter or security failures before amending the commit to avoid introducing noise or security issues.

Can I stage specific files and generate a conventional commit without pushing?▼

Yes, you can stage specified files and generate a conventional commit without pushing, as the workflow only pushes branches when explicitly requested by the user.

How do I choose the right scope and summary for a conventional commit?▼

To choose the right scope and summary for a conventional commit, infer an appropriate scope from the changed module and write a concise imperative summary to keep the git history readable and actionable.

Why use conventional commits for version control?▼

Use conventional commits for version control to solve the problem of poorly formatted or vague commit messages, making code review, tracing, and automation significantly easier.

Does this workflow support amending commits after fixing pre-commit failures?▼

Yes, the workflow supports amending commits after addressing pre-commit hook failures and auto-fixes, ensuring your staged changes are committed correctly without accidental pushes.

Related Skills

Explore More Software Engineering Skills→
bughqbughq
2

stacks-git

Standardize Git commit conventions and automate changelog generation in Stacks applications.

Official
Intermediate
yaronshereryaronsherer

smart-push

Automate Git commits, pushes, and GitHub Actions CI monitoring with auto-fixes.

Community
Advanced
eliottbusinesseliottbusiness

requesting-code-review

Automate pre-commit code review with static analysis and security scanning.

Community
Advanced
deferreddeferred

git-commit

Executes Git commits with conventional messages and intelligent file staging using Git CLI and Bash shell.

Community
Advanced