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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit work often turns into messy, oversized commits that are hard to review and harder to revert; this skill organizes your uncommitted changes into logical, feature-based commits with consistent messages.

Core Features & Use Cases

  • Uncommitted change analysis (staged + unstaged): Detects what changed and what should be included.
  • Logical grouping by module/feature: Clusters related files (schema/API/frontend/config/tests/docs/scripts) into coherent commit sets instead of one big dump.
  • Commit message generation and CI gate: Produces well-formed commit messages, runs required CI checks before staging/committing, and pushes by default.

Quick Start

Use the commit skill to analyze your working tree, generate a multi-commit plan, run CI checks, then commit and push changes in logical modules.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I split uncommitted git changes into logical commits by feature?

To split uncommitted git changes, analyze your working tree and group related files by module, such as schema, API, or UI, into coherent commit sets instead of one large dump. This approach ensures your commits are organized by feature and easier to review.

How do I run CI checks before committing changes to a git repository?

Running CI checks before committing changes requires a discovery-and-execution step with timeouts to validate your code. This ensures required CI commands pass before writing history, preventing broken commits from being pushed to your remote repository.

Can I review a multi-commit plan before pushing changes to git?

Yes, you can review a multi-commit plan before pushing changes by using a dry-run mode. This allows you to analyze your working tree and verify the logical grouping of staged and unstaged files before any history is written or changes are pushed.

How do I prevent README drift when committing code changes?

To prevent README drift when committing code changes, use automatic README drift checks during your commit workflow. This detects documentation inconsistencies before writing history, ensuring your README stays synchronized with your feature-based commits.

What is the best way to organize a feature-based workflow with staged and unstaged files?

Organizing a feature-based workflow with staged and unstaged files involves clustering related changes by module, including config, tests, and docs. This creates clean, logically grouped commit sets that are easy to review and revert if necessary.