gum-status

GUM Status

This skill shows exactly what modules are active RIGHT NOW and what rules the agent is following. Not module names -- the actual expanded rules content, override state, and hook configuration. The user should see the full picture of what governs agent behavior in this session.

Announce at start: "I'm using the gum-status skill to show your active GUM context."

The Iron Law

SHOW THE RULES, NOT JUST THE NAMES.

"You have 4 active modules" is useless. The user needs to see what those modules SAY. Always expand and display the actual rules content.

When to Use

• User says "status", "what modules are active", "show my rules", "what's gum doing"
• User wants to verify a module is enabled before relying on it
• User is confused about why the agent is or isn't following a rule
• User wants to check override state (team vs personal vs default)
• Before debugging compliance issues

Use this ESPECIALLY when:

• User says "why isn't the agent doing X" -- status reveals if the rule exists and is active
• User switched projects and wants to see what's active here
• User just ran npx get-gum toggle and wants to verify

Process

Phase 1: Read All State Sources

Read these in order:

1. Run npx get-gum list --gum-dir ~/.gum via Bash -- get all modules and their enabled/disabled status
2. Read ~/.claude/rules/gum/*.md -- these are the synced active rules (auto-loaded, no permission needed)
3. Read .gum.json in current directory -- team-level overrides (if exists)
4. Read .gum.local.json in current directory -- personal overrides (if exists)

Phase 2: Apply Override Priority

Overrides stack. Later sources win:

module.yaml (default) < .gum.json (team) < .gum.local.json (personal)

MUST apply this correctly. A module enabled in module.yaml but disabled in .gum.json is DISABLED. A module disabled in .gum.json but re-enabled in .gum.local.json is ENABLED.

Track the effective state AND the source of that state: