Maintenance

GAIA ships commands for doing work and commands for keeping the GAIA setup itself in shape. This page covers the second kind: the commands that check and repair GAIA’s own setup as a project grows.

As a project accumulates work, three parts of that setup drift independently:

• the Claude integration surface: hooks, command and skill frontmatter, rule wiring, .claude/settings.json;
• the loaded context Claude reads every session: machine-local memory, project rules, and autoloaded CLAUDE.md files;
• the wiki itself: pages that overlap or contradict each other, and broken wikilinks.

Each part has its own command. They run independently and do not call one another.

Command	What it checks	The question it answers
/gaia-fitness	The Claude integration surface: hooks, frontmatter, rules, .claude/settings.json	Does the machine run?
/gaia-audit	The loaded context: memory, rules, and autoloaded files, for duplication, contradictions against the source of truth, stale entries, and over-budget autoloads	Is the fuel clean?
/gaia-wiki	The wiki itself: redundant or conflicting pages, and broken wikilinks	Is the knowledge base internally consistent?

Which one to run

Pick by symptom:

• The integration feels off, a hook is not firing, a rule is not loading, a command misbehaves: run /gaia-fitness.
• The base context feels heavy, or machine-local memory has grown large: run /gaia-audit.
• The wiki has grown and pages overlap, or wikilinks break: run /gaia-wiki.

The boundary between /gaia-audit and /gaia-wiki is deliberate. /gaia-audit reconciles the loaded context against the wiki (the source of truth) and resolves disagreements between project files; it does not touch wiki-page-vs-wiki-page conflicts. Those belong to /gaia-wiki consolidate.

Related

For keeping dependencies and GAIA itself current, a different kind of upkeep, see /update-deps and /update-gaia.