Help us improve
Share bugs, ideas, or general feedback.
From cryptozavr
Use at the end of a cryptozavr research session (or when the user asks "wrap up" / "what did we do"). Produces a disciplined 3-bullet summary — artifacts produced, decisions made, what's next — so the next session starts warm.
npx claudepluginhub evgenygurin/cryptozavr --plugin cryptozavrHow this skill is triggered — by the user, by Claude, or both
Slash command
/cryptozavr:post-session-reflectionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill when the user signals the session is winding down (phrases
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
Use this skill when the user signals the session is winding down (phrases like "wrap up", "what did we do", "summarize", "done for today"), or immediately after a multi-tool research collage that warrants a recap.
- **Produced**: <artifacts — tool outputs, files, commits, plan docs>
- **Decided**: <non-obvious choices made this session, with the reason>
- **Next**: <explicit next step, owner, and trigger condition>
- **Produced**: `MetricsDecorator` + `HealthMonitor` (commits b7c6991, bb1b8aa) and 24 new unit tests in `tests/unit/observability/`.
- **Decided**: Prometheus-compatible dict snapshot over text format for now — keeps the surface JSON-serialisable until we add the HTTP endpoint in Phase 2.
- **Next**: Wire `HealthMonitor.start()` into `build_production_service` and expose `venue_health_check_total` via `/cryptozavr:health` when Supabase is reachable again.
venue-debug instead).feature-dev skill's plan format there.