repo-audit

name	repo-audit
description	Audit the numpad repository — implementation state, docs drift, architecture health, and next priorities.

repo-audit skill

Use this skill when the task is a health check, gap analysis, docs vs code comparison, or identifying the best next implementation milestone.

Inspection checklist

Work through these in order:

1. Read key docs first

• docs/STATUS_GAP_ANALYSIS.md — starting point for known gaps
• docs/IMPLEMENTATION_ROADMAP.md — milestone state
• docs/ARCHITECTURE.md — declared architecture
• docs/ENGINE_SPEC.md — engine contracts
• docs/AI_SPEC.md — AI contracts
• docs/API_CONTRACTS.md — frontend↔native surface

2. Inspect implementation reality

• src/engine/index.ts — public facade: what's actually exported
• src/app/store/workspace.store.ts — what state and actions exist
• src-tauri/src/lib.rs — what commands are registered
• src-tauri/src/services/ — what services exist
• src/features/ — which features are present and their file structure
• src/features/settings/settings.store.ts — what settings exist

3. Compare: docs vs code

For each doc, verify:

• Are the described commands still in lib.rs?
• Are the described service methods still in services/?
• Do the TypeScript types in ai.types.ts match the Rust types?
• Does docs/ARCHITECTURE.md match the actual file structure?
• Does docs/ENGINE_SPEC.md match what src/engine/index.ts exports?

4. Architecture health

Check for boundary violations:

• Does src/engine/ import from src/features/ or src/app/? (it must not)
• Are there any invoke calls directly in components? (should be in *.native.ts files)
• Is business logic in Tauri command handlers? (should be in services/)
• Are there hardcoded color values instead of CSS variables?
• Are there any types in TypeScript files?

5. Identify gaps

• Features referenced in docs but not in code
• Features in code but missing from docs
• TODO/FIXME comments that indicate incomplete work
• Partial implementations (files that exist but are stubs)

Required output format

Always return these sections:

## Implementation summary
<2-3 sentence overview of current state>

## Confirmed working systems
<bullet list with specific file references>

## Incomplete or missing systems
<bullet list with specific file references and what's missing>

## Documentation drift
<bullet list of specific doc ↔ code mismatches>

## Architecture risks
<bullet list of boundary violations, debt, or structural risks>

## Recommended next priorities
1. <most urgent with rationale>
2. <second>
3. <third>

Project reminders

• Deterministic engine is the source of truth — any AI involvement in arithmetic is a defect.
• No unit tests should be added.
• Prefer concrete file-based observations — never speculate without reading the file.
• The docs/STATUS_GAP_ANALYSIS.md may be stale — always verify against actual code.