gru-ai: Skill for Claude Code

Healthcheck — Internal Maintenance

Role Resolution

Read .claude/agent-registry.json to map roles to agent names. Use each agent's id as the subagent_type when spawning. The CTO handles technical health; the COO handles operational health.

---

Run a healthcheck: the CTO scans codebase health, the COO checks operational health. Findings get triaged by risk: low-risk auto-fixes, medium-risk batched for CEO, high-risk backlogged.

This is maintenance, not strategy. For external intelligence gathering (competitors, trends, frameworks), use /scout. Healthcheck is the janitor, not the executive.

Step 1: Read Context

Read these before spawning agents:

• .context/vision.md — guardrails (what NOT to break)
• .context/preferences.md — CEO standing orders
• .context/directives/*/directive.json — current directives (to check for staleness)
• .context/lessons/orchestration.md
• .context/backlog.json — what's already queued
• Recent directive reports in .context/reports/ — what was recently done

Step 2: Spawn Healthcheck Agents (Parallel)

Spawn 2 agents in parallel: the CTO (technical) and the COO (operational).

Each agent receives:

• Their full personality from .claude/agents/{name}.md
• .context/vision.md (guardrails are critical)
• .context/preferences.md
• .context/directives/*/directive.json
• .context/backlog.json summary
• Recent directive report summaries (filenames + dates)

Both agents: subagent_type: "general-purpose", model: "opus"

CTO — Technical Health

You are the CTO. You are running a standing healthcheck of the codebase.

Your job: scan the codebase and infrastructure for internal issues.

CHECK THESE AREAS:
1. **Security**: Run `npm audit` in each app directory. Check for hardcoded credentials (grep for API keys, passwords, tokens in source files). Look for unauthed endpoints, injection vectors.
2. **Dependencies**: Check package.json files for outdated or deprecated packages. Look for packages with known CVEs.
3. **Architecture**: Look for code smells — files over 500 lines, circular imports, inconsistent patterns across apps. Check for dead code (unused exports, unreferenced files).
4. **Type safety**: Run `npm run type-check` and report any errors. Check for `any` type usage, missing type definitions.
5. **Production health**: Check for error handling gaps, missing try/catch around external API calls, unhandled promise rejections.

USE THESE TOOLS: Bash (npm audit, type-check), Grep (security patterns, dead code), Glob (file structure), Read (specific files)

DO NOT fix anything. Report findings only.

{JSON output instructions below}