dots-git-status-cleanup

Organize git changes into semantic, atomic commits.

Updated Jun 17, 2025
One-click install
npx skills add https://github.com/nikbrunner/dots --skill dots-git-status-cleanup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dots-git-status-cleanup
Source: https://github.com/nikbrunner/dots/tree/main/common/.agents/skills/dots-git-status-cleanup
Command: npx skills add https://github.com/nikbrunner/dots --skill dots-git-status-cleanup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organize and reduce git noise by turning scattered changes into clean, semantic commits.

Core Features & Use Cases

  • Atomic commits: group related changes into focused commits following conventional semantics.
  • Workflow guidance: suggests running dots chores first, then handle remaining changes one file at a time.
  • Guardrails: prevents mixing unrelated configuration files into a single commit and encourages descriptive messages.

Quick Start

Run dots chores to automatically commit routine changes, then create atomic commits for remaining edits.

Frequently Asked Questions about dots-git-status-cleanup

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

FAQPage Schema
How do I group scattered git changes into focused, semantic commits?

To group scattered git changes into focused semantic commits, this Skill analyzes your working directory and organizes modifications into logical, atomic commits. It enforces deterministic commit boundaries to prevent mixing unrelated configuration files into a single commit.

What's the best way to automate semantic commits for dotfiles workflows?

Automating semantic commits for dotfiles workflows involves running automated chores first to handle routine changes, then addressing remaining edits one file at a time. This two-step workflow reduces noise and ensures configurations are incrementally committed during deployments.

Can I separate unrelated configuration file changes into atomic commits automatically?

You can separate unrelated configuration changes into atomic commits automatically by using guardrails that prevent mixing unrelated files. The Skill enforces deterministic commit boundaries, ensuring each commit remains focused and logically grouped.

How does a two-step git workflow handle routine changes versus remaining edits?

A two-step git workflow handles changes by first running chores to automatically commit routine modifications, then addressing remaining edits individually. This approach aligns with semantic-commit conventions and keeps incremental commits clean during code reviews.