gspdev-housekeeping

Detect version mismatches, count drifts, and stale terminology in GSP repositories.

49|4|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/jubscodes/get-shit-pretty --skill gspdev-housekeeping
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gspdev-housekeeping
Source: https://github.com/jubscodes/get-shit-pretty/tree/main/dev/skills/gspdev-housekeeping
Command: npx skills add https://github.com/jubscodes/get-shit-pretty --skill gspdev-housekeeping

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When developers modify GSP project files, version numbers, counts, and terminology can drift, causing broken builds, outdated documentation, and confusion.

Core Features & Use Cases

  • Scan version files and ensure they are synchronized across the repository.
  • Verify that counts of skills and agents in CLAUDE.md match the actual filesystem.
  • Detect stale terminology and outdated comments in source and installer files.
  • Check CHANGELOG health and suggest appropriate actions.
  • Propose clean, grouped git commits for any required fixes.

Quick Start

Run gspdev-housekeeping fix to automatically correct detected drifts, or run gspdev-housekeeping for a dry‑run report.

Frequently Asked Questions about gspdev-housekeeping

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

FAQPage Schema
How do I detect version drift and stale terminology across my git repository?

Version drift and stale terminology are detected by scanning version files and source code to find mismatches and outdated comments. This Skill inspects your repository's file system and git status to report inconsistencies.

How do I synchronize version numbers across project files after adding or removing components?

To synchronize version numbers, run an automated fix command that scans the repository and corrects detected drifts. It edits markdown and JSON files to ensure all version references are consistent across the project.

Why does my project documentation show incorrect counts for skills and agents?

Incorrect counts in documentation occur when filesystem changes are not reflected in markdown files. This Skill verifies that the counts of skills and agents in CLAUDE.md match the actual filesystem to resolve the discrepancy.

Can I perform a dry-run audit of my repository before applying fixes?

Yes, you can perform a dry-run audit by running the default command without arguments. This generates a report of version mismatches and stale terminology without modifying any files.

What is the best way to group git commits when fixing repository drift?

The best way to group git commits is to use an automated audit tool that proposes clean, grouped commits for required fixes. This ensures that version corrections and terminology updates are logically organized.

How do I check the health of a CHANGELOG after modifying project versions?

To check CHANGELOG health, run a repository audit that checks the file's consistency and suggests appropriate actions. This ensures your changelog accurately reflects recent version modifications and updates.