gspdev-housekeeping

Run this often — after adding/removing skills or agents, after architecture changes, after version bumps. Think of it as a linter, not a test suite.

Source layout reference:

• gsp/skills/ — skills (SKILL.md files)
• gsp/agents/ — agents (gsp-*.md files)
• gsp/templates/ — config, state, brief, roadmap templates
• bin/install.js — multi-runtime installer
• VERSION, package.json — version sources
• CLAUDE.md — project instructions (references counts)

Step 0: Parse mode

$ARGUMENTS:

• check or empty — dry run, report only
• fix — report and fix each issue (confirm before editing)

Step 1: Gather counts

Run in parallel:

# Actual counts from filesystem
SKILL_COUNT=$(ls -d gsp/skills/*/SKILL.md 2>/dev/null | wc -l | tr -d ' ')
AGENT_COUNT=$(ls gsp/agents/gsp-*.md 2>/dev/null | wc -l | tr -d ' ')
echo "skills=$SKILL_COUNT agents=$AGENT_COUNT"

# Versions from all sources
cat VERSION
node -e "process.stdout.write(require('./package.json').version)"
echo
node -e "process.stdout.write(require('./gsp/templates/projects/config.json').version)"
echo
node -e "process.stdout.write(require('./gsp/templates/branding/config.json').version)"

Step 2: Version sync

Check that all 4 version sources agree: VERSION, package.json, projects/config.json, branding/config.json.

Any mismatch → drift issue. The VERSION file is the source of truth.

Fix: update the mismatched files to match VERSION.

Step 2.5: Changelog health

Check CHANGELOG.md for common issues:

1. Unreleased section exists — ## [Unreleased] must be present at the top. If missing, flag it.
2. Unreleased is not empty — if there are commits since the last versioned entry but Unreleased has no content, flag: "Unreleased section is empty but there are new commits. Run /gspdev-changelog update to populate."
3. Current version coverage — if VERSION matches the latest versioned section in CHANGELOG.md, that's fine (post-release state). If VERSION is ahead of the changelog (no versioned section for it), Unreleased should have content.