skills.rest
ksleungac
ksleungacCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

commit

Classify git status and diffs into data, program, and docs to flag unrelated changes.

17|3|Updated Mar 1, 2026
Search Tags:#git#commit#data#hygiene#code-review#version-control
One-click install
npx skills add https://github.com/ksleungac/pids-jre-simulator --skill commit-ksleungac
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/ksleungac/pids-jre-simulator/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/ksleungac/pids-jre-simulator --skill commit-ksleungac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit hygiene — before creating a commit, detect and flag unrelated changes (especially stray data fixes bundled into program commits) so they can be split into their own commits.

Core Features & Use Cases

  • Inventory and classify changed files into Data (shipped), Program (code), and others to identify scope.
  • Flag unrelated changes that should be split into separate commits to preserve clear history.
  • Generate a draft, guidance, and boundaries for the final commit message to ensure cohesive commits across teams.

Quick Start

Run the commit hygiene workflow before committing to ensure only related changes are included.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I separate data fixes from code changes before making a git commit?▼

To separate data fixes from code changes before a git commit, this Skill analyzes git status and diffs, classifies files into data, program, or docs, and outputs recommended commit boundaries to isolate unrelated changes.

What is the best way to keep my version control history clean when bundling unrelated file modifications?▼

The best way to keep version control history clean is to detect and flag unrelated changes before committing, ensuring data fixes and program changes are split into separate, cohesive commits with distinct boundaries.

How does detecting unrelated changes help with code review and commit hygiene?▼

Detecting unrelated changes improves code review and commit hygiene by ensuring each commit contains only related modifications, making it easier for reviewers to track program and data changes through a clear version history.

Can I automatically generate a draft commit message after splitting my changes?▼

Yes, you can automatically generate a draft commit message after splitting changes, as the Skill outputs a draft message and guidance based on the classified files and the recommended commit boundary.

Does this commit hygiene workflow work without requiring additional dependencies?▼

Yes, the commit hygiene workflow works without requiring additional dependencies, as it directly analyzes your existing git status and diffs to classify changed files and recommend commit boundaries.

Related Skills

Explore More Software Engineering Skills→
maxmurrmaxmurr

generating-commit-messages

Generate commit messages from git diff --staged with WHAT/WHY summaries.

Community
Basic
GlorktelligenceGlorktelligence

Git Workflow

Commit and push code changes to a remote repository using Conventional Commits.

Community
Intermediate
bailynlovebailynlove
1

requesting-code-review

Automate pre-commit code verification with static security scanning and quality gates.

Community
Advanced
lluppesmslluppesms

git-commit

Generate Conventional Commits messages from code diffs with Git CLI.

Community
Advanced