kanso-commit

Analyze the working tree and create atomic git commits with imperative messages.

2|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/blakecyze/kanso --skill kanso-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kanso-commit
Source: https://github.com/blakecyze/kanso/tree/main/skills/kanso-commit
Command: npx skills add https://github.com/blakecyze/kanso --skill kanso-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of messy, unclear commit histories by enforcing atomic changes and requiring commit messages that explain the reasoning behind code changes rather than just describing the diff.

Core Features & Use Cases

  • Atomic Splitting: Automatically identifies logical groupings in your working tree and helps you split them into separate, clean commits.
  • Convention Enforcement: Detects and adheres to your repository's existing commit style, whether it is Conventional Commits, Django-style, or custom patterns.
  • Contextual Messaging: Guides you to write commit messages that explain the why, ensuring future maintainers understand the intent behind architectural decisions and bug fixes.

Quick Start

Ask the agent to commit your current changes using the kanso-commit skill to ensure they are atomic and follow the repository's established conventions.

Frequently Asked Questions about kanso-commit

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

FAQPage Schema
How do I split working tree changes into atomic git commits?

To split changes into atomic git commits, the skill analyzes your working tree for distinct logical groupings and helps you stage and commit them separately. It requires git CLI access to verify and commit each logical change individually.

What is the best way to write commit messages that explain the why?

Writing commit messages that explain the why involves prompting for descriptive, imperative statements detailing the rationale behind modifications. This approach ensures future maintainers understand architectural decisions rather than just reading the diff.

Can I enforce existing repository commit conventions automatically?

You can enforce existing repository commit conventions by detecting and adhering to your project's established style. The skill identifies patterns like Conventional Commits or Django-style and maintains project-wide consistency across new commits.

Does this git commit automation work without external dependencies?

This git commit automation works without external dependencies, requiring only git CLI access to stage, verify, and commit changes. It operates internally to analyze the working tree and prompt for appropriate commit messages.

How do I ensure my refactoring changes are committed logically?

To ensure refactoring changes are committed logically, the skill identifies distinct logical changes in your working tree and separates them into clean, atomic commits. This prevents mixing unrelated modifications into a single commit history entry.