repo-hygiene-pass

Name: repo-hygiene-pass
Availability: InStock
Author: rbtkhn

Organizes mixed Git repository changes into commit groups and removes scratch files from commits.

Updated Feb 8, 2026

Search Tags:#git #workflow #commit #repository #staging #hygiene

Ready to run

npx skills add https://github.com/rbtkhn/grace-mar --skill repo-hygiene-pass

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: repo-hygiene-pass
Source: https://github.com/rbtkhn/grace-mar/tree/main/.cursor/skills/repo-hygiene-pass
Command: npx skills add https://github.com/rbtkhn/grace-mar --skill repo-hygiene-pass

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of messy Git worktrees by helping operators separate unrelated changes, prevent accidental inclusion of scratch files, and prepare cleaner commits.

Core Features & Use Cases

Commit Organization: Groups modified files into intent-based buckets and guides focused staging instead of broad commits.
Repository Cleanup: Helps isolate generated files, local scratch content, and production changes to keep repositories maintainable.
Use Case: When a repository contains feature work, documentation edits, and temporary files together, use this Skill to organize changes into safe, reviewable commit units.

Quick Start

Use the repo-hygiene-pass skill to review my current Git changes and organize them into clean commit groups.

Frequently Asked Questions about repo-hygiene-pass

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

FAQPage Schema

How do I organize mixed Git changes into separate commits?▼

To organize mixed Git changes, this Skill groups modified files into intent-based buckets and guides focused staging, preventing broad commits from mixing unrelated work. It separates feature code, documentation edits, and temporary files into safe, reviewable commit units.

How do I remove scratch files and generated content from my Git commits?▼

To remove scratch files and generated content from Git commits, this Skill isolates local scratch content and accidental noise from production changes during repository cleanup. It ensures only intended modifications are staged and committed.

What is the best way to group modified files into intent-based Git commits?▼

The best way to group modified files into intent-based Git commits is by applying disciplined staging practices to separate unrelated changes. This Skill categorizes worktree modifications into focused, rollback-safe commit groups without destructive history rewriting.

Can I prepare a Git push without destructive history rewriting?▼

Yes, you can prepare a Git push without destructive history rewriting by organizing your staged changes into rollback-safe commit groups. This Skill structures your repository changes safely before pushing, avoiding any destructive history modifications.

Does this Git commit organization method support software development workflows with documentation updates?▼

Yes, this Git commit organization method supports software development workflows involving code changes, documentation updates, and generated files. It separates these mixed modifications into distinct, reviewable commit units tailored for development and push preparation scenarios.