session-review
Session Review & Handoff
Analyze agent sessions and prepare context handoffs for session continuity.
Purpose
This skill serves two complementary workflows:
Review (/pokayokay:review) — Retrospective analysis:
- Understand what the agent actually did vs what was planned
- Identify good patterns to reinforce and bad patterns to prevent
- Find wasted effort and context efficiency issues
- Generate improvements for skills, prompts, and workflows
Handoff (/pokayokay:handoff) — Forward-looking context preservation:
- Document completed work and in-progress state
- Capture decisions, blockers, and next steps
- Track skill usage and ad-hoc work
- Prepare context for the next session or agent
More from srstomp/pokayokay
architecture-review
Use when auditing project structure, planning refactors, improving code organization, analyzing dependencies and module boundaries, or identifying structural issues. TypeScript/JavaScript-primary with language-agnostic patterns.
301figma-plugin
Use when building Figma plugins, creating design automation tools, implementing sandbox/UI communication, or working with the Figma Plugin API for node manipulation, styles, and components.
79security-audit
Use when reviewing code security, auditing dependencies for CVEs, checking configuration or secret security, assessing authentication and authorization patterns, identifying OWASP vulnerabilities (injection, XSS, CSRF), or addressing security concerns about implementations.
48testing-strategy
Use when designing test architecture, building API test suites, validating API contracts, setting up component or E2E testing, managing test data, debugging flaky tests, reviewing coverage strategy, or organizing test files. Covers test pyramid, mocking (MSW), frontend (React Testing Library, Playwright), and CI integration.
28sdk-development
Use when building TypeScript SDKs, extracting shared code into packages, creating developer tooling libraries, designing clean API surfaces, or publishing to npm (public or private). Covers typed clients, error handling, multi-target bundling (ESM/CJS/browser).
28spike
Time-boxed technical investigation with structured output. Use for feasibility studies, architecture exploration, integration assessment, performance analysis, or risk evaluation. Creates spike tasks in ohno, enforces time-boxing, generates spike reports, and creates actionable follow-up tasks.
25