commit

Generate conventional git commit messages for staged changes and commit them.

1|1|Updated Feb 9, 2026

Search Tags:#git #version control #commit #conventional commits #repository #staged changes

Ready to run

npx skills add https://github.com/przbadu/skills-factory --skill commit-przbadu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/przbadu/skills-factory/tree/main/skills/commit
Command: npx skills add https://github.com/przbadu/skills-factory --skill commit-przbadu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of turning staged code changes into a clear, conventional git commit message while keeping the commit scoped and safe.

Core Features & Use Cases

Conventional Commit Formatting: Produces concise messages that follow a standard type(scope): summary structure with issue references.
Staged-Only Safety: Commits only already staged changes, helping prevent accidental inclusion of unfinished files.
Developer Workflow Fit: Useful for feature work, bug fixes, refactors, docs updates, and quick save-point commits when you need a polished message fast.

Quick Start

Ask the assistant to generate a conventional commit message for your staged changes and then commit only the staged files with git commit.

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 for staged git changes?▼

To generate conventional commit messages, the Skill analyzes your staged git changes and creates a type(scope): summary structure with issue references, then commits only those staged files safely.

What is the conventional commits format for local repository changes?▼

The conventional commits format follows a type(scope): summary structure, incorporating standard types like bug fixes, features, refactors, and documentation updates alongside relevant issue references.

How do I commit only staged files without including unfinished changes?▼

Committing only staged files is enforced by requiring staged-only commits, which prevents accidental inclusion of unfinished files by strictly limiting the git commit to already staged changes.

Does this conventional commit generator require any specific git sub-agent setup?▼

Yes, it requires a git sub-agent for task execution and uses the Claude Haiku model, operating with no external dependencies to process staged changes and print the message before running git commit.

Can I include issue numbers in conventional commit messages for feature work?▼

Yes, issue-number inclusion is applied when available, allowing you to reference tracking issues directly within the conventional commit message for features, bug fixes, and refactors.

What are the limitations of using staged-only commits for version control?▼

The limitation is that it commits strictly staged-only changes, so you must manually stage all desired files via git add beforehand, as it will not automatically include unstaged or untracked repository files.