One-click install
npx skills add https://github.com/lgzarturo/codeconductor --skill commit-lgzarturo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/lgzarturo/codeconductor/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/lgzarturo/codeconductor --skill commit-lgzarturo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It automates the creation of English commit messages that follow the Conventional Commits spec based on the currently staged changes, reducing manual effort and ensuring consistency across the project.

Core Features & Use Cases

  • Generate a concise, standardized commit message from the diff of staged changes.
  • Support Conventional Commits prefixes and types (feat, fix, docs, chore) with appropriate scope handling.
  • Improve changelog generation and team code review by enforcing a predictable message format.

Quick Start

Ask the assistant to generate a commit message in English following Conventional Commits based on the staged changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commit messages automatically from staged changes?

Yes, Conventional Commits automation supports feature, fix, documentation, and chore workflows. It infers the staged diff and applies the correct prefix and scope, ensuring your commit messages satisfy standardized version-control practices across projects.

Can I use this to automate commit messages for Git workflows enforcing Conventional Commits?

Yes, Conventional Commits automation supports feature, fix, documentation, and chore workflows. It infers the staged diff and applies the correct prefix and scope, ensuring your commit messages satisfy standardized version-control practices across projects.

What's the best way to write conventional commits for staged changes without manual effort?

This automated commit generation handles standard types including feat, fix, docs, and chore. It analyzes your staged diff to determine the appropriate type, applies the correct prefix with scope handling, and produces a compliant English message.

Does conventional commit automation work with different types like feat, fix, docs, and chore?

This automated commit generation handles standard types including feat, fix, docs, and chore. It analyzes your staged diff to determine the appropriate type, applies the correct prefix with scope handling, and produces a compliant English message.

Do I need to manually stage changes before generating a conventional commit message?

Enforcing standardized conventional commit messages improves changelog generation and team code review. By applying a predictable message format with correct prefixes and scope handling, it ensures consistent version-control history across automated workflows.

How does enforcing conventional commits improve changelog generation and code review?

Enforcing standardized conventional commit messages improves changelog generation and team code review. By applying a predictable message format with correct prefixes and scope handling, it ensures consistent version-control history across automated workflows.