km:commit

Create Conventional Commits-style git commits with staged file selection and secret checks.

Updated Jan 24, 2026

Search Tags:#automation #git #security #commit #version-control #conventional-commits

Ready to run

npx skills add https://github.com/koumatsumoto/agent-config --skill km-commit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: km:commit
Source: https://github.com/koumatsumoto/agent-config/tree/main/templates/skills/commit
Command: npx skills add https://github.com/koumatsumoto/agent-config --skill km-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It automates the creation of clean, conventional‑style git commits while preventing accidental inclusion of sensitive files.

Core Features & Use Cases

Selective Staging: Adds only the intended files using individual git add commands.
Secret Detection: Stops the commit if potential credentials or secret patterns are found.
Conventional Commit Formatting: Generates a structured commit message with title, background, plan, and details.
Use Case: When you finish a feature or bug fix and want to record the work safely, this skill prepares and executes the commit in one flow.

Quick Start

Use the commit skill to record your changes with a concise conventional commit message.

Frequently Asked Questions about km:commit

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

FAQPage Schema

How do I create a conventional commit without accidentally exposing secrets?▼

To create a conventional commit safely, this skill checks staged files for potential credential patterns and stops the commit if secrets are detected. It then formats the message using the conventional commit structure.

How to automate git staging for specific files before generating a commit message?▼

You can automate selective git staging by prompting the skill to record your work. It uses individual git add commands to stage only the intended files from your working tree status before generating the commit message.

What is the best way to format git commit messages for version control automation?▼

The best way to format git commit messages for version control is using the conventional commits standard. This skill generates a structured message with title, background, plan, and details sections automatically.

Does this commit automation tool require any special git permissions or dependencies?▼

This commit automation tool requires access to standard git commands and the ability to read the working tree status. It has no external dependencies and respects existing repository security rules.

Why does my automated commit stop before finishing when sensitive files are present?▼

Your automated commit stops because the secret detection feature identifies potential credentials or sensitive file patterns in the staged changes. This precaution prevents accidental inclusion of sensitive data in version control.