__commit

Analyze git diffs and history to generate and execute convention-compliant commits.

Updated May 13, 2026
One-click install
npx skills add https://github.com/cilly-yllic/.llm --skill commit-cilly-yllic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: __commit
Source: https://github.com/cilly-yllic/.llm/tree/main/skills/ja/__commit
Command: npx skills add https://github.com/cilly-yllic/.llm --skill commit-cilly-yllic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It analyzes your current working tree changes and produces a repository-convention-compliant commit message, then performs the commit for you.

Core Features & Use Cases

  • Change analysis and commit message generation: Inspects git status, staged diff, unstaged diff, and recent history to infer change type and purpose, then drafts a conventional summary.
  • Staging-aware workflow: Detects whether changes are already staged and, if needed, prompts you to decide whether to stage and commit all changes or only the staged ones.
  • Optional push support: If the push option is enabled, pushes after a successful commit (without force-pushing).

Quick Start

Run the __commit skill with the optional push behavior enabled when you want the commit to be pushed to the remote after creation.

Frequently Asked Questions about __commit

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

FAQPage Schema
How do I generate a conventional commit message from my git diff?

To generate a conventional commit message, the Skill analyzes your staged and unstaged diffs alongside recent repository history to infer the change type and purpose. It drafts a convention-compliant summary and executes the git commit automatically.

Can I automatically stage and commit all working tree changes at once?

Yes, you can stage and commit all working tree changes at once. The staging-aware workflow detects unstaged files and prompts you to decide whether to stage and commit all changes or proceed with only the currently staged ones.

How to push after a successful git commit without force-pushing?

To push after a successful git commit without force-pushing, you enable the push option when running the workflow. The Skill executes a standard push to the remote immediately after the commit succeeds.

What is the best way to automate commit messages for refactoring and test changes?

The best way to automate commit messages for refactoring and test changes is using a diff analysis workflow that inspects repository state and recent history. It applies repository convention rules to draft an appropriate commit message and performs the commit.

Does the automated commit workflow support parallel state inspection across active branches?

Yes, the automated commit workflow supports parallel state inspection across active branches. It evaluates `git status`, staged diffs, and unstaged diffs simultaneously to infer change purpose and safely perform staging decisions.