.claude/skills/exit-review/SKILL.md
End-of-session learning classification. Reviews accumulated learnings and classifies each as GREEN (generic, goes to global wiki), YELLOW (project-specific, goes to project wiki), or RED (sensitive, discarded). Triggered at session end via Stop hook. Use when: (1) session ending, (2) manual review of learnings. Triggers: /exit-review, 'review learnings', 'classify learnings'.
npx skillsauth add alfredolopez80/multi-agent-ralph-loop exit-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Classify accumulated learnings before session ends.
| Color | Meaning | Destination | Example |
|---|---|---|---|
| GREEN | Generic (useful for any project) | $VAULT_DIR/global/wiki/{category}/ | "Use zod for runtime validation" |
| YELLOW | Project-specific | $VAULT_DIR/projects/{project}/wiki/ | "Hook sanitize-secrets.js uses 28 patterns" |
| RED | Contains secrets or sensitive info | DISCARDED (never saved) | "API key is sk-..." |
$VAULT_DIR/global/wiki/{category}/
c. If YELLOW: write to $VAULT_DIR/projects/{project}/wiki/
d. If RED: discard with warning---
type: learning
classification: GREEN
source: session-2026-04-04
confidence: 0.3
sessions_confirmed: 1
category: typescript
---
# Use zod for runtime validation at API boundaries
Runtime validation with zod catches type mismatches that TypeScript alone misses at API boundaries.
Particularly useful for external API responses where the shape is not guaranteed.
## Evidence
- Used successfully in auth endpoint validation
- Caught 3 type mismatches in first session
Stop event via session-end-handoff.sh/exit-reviewsession-accumulator.sh collects learnings during sessionvault-graduation.sh promotes high-confidence ones to rules at next SessionStartdevelopment
Living knowledge base management. Actions: search (query vault), save (store learning), index (update indices), compile (raw->wiki->rules graduation), init (create vault structure). Follows Karpathy pipeline: ingest->compile->query. Use when: (1) searching accumulated knowledge, (2) saving learnings, (3) compiling raw notes into wiki, (4) initializing a new vault. Triggers: /vault, 'vault search', 'knowledge base', 'save learning'.
testing
Produce a verifiable technical specification before coding. 6 mandatory sections: Interfaces, Behaviors, Invariants (from Aristotle Phase 2), File Plan, Test Plan, Exit Criteria (executable bash commands + expected results). Use when: (1) before implementing features with complexity > 4, (2) as Step 1.5 in orchestrator workflow, (3) when requirements need formalization. Triggers: /spec, 'create spec', 'write specification', 'technical spec'.
testing
Pre-launch shipping checklist orchestrating /gates, /security, /browser-test, /perf. Ensures nothing ships without passing all quality checks. Use when: (1) before deploying, (2) before merging to main, (3) before release. Triggers: /ship, 'ship it', 'ready to deploy', 'pre-launch check'.
development
Performance optimization skill. Core Web Vitals via Lighthouse, bundle size analysis, metrics tracking over time. Use when: (1) optimizing frontend performance, (2) analyzing bundle size, (3) tracking metrics regression. Triggers: /perf, 'performance audit', 'core web vitals', 'bundle size'.