Creates structured context summaries for continuing work across AI sessions. Use when ending a session to enable seamless continuation in a new session without losing context.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Generates a detailed handoff document capturing the current state of work, enabling seamless continuation in a fresh AI session.
Generate a structured handoff document with:
## Session Summary
**Task**: [What was being worked on]
**Branch**: [Current git branch]
**Status**: [In progress / Blocked / Ready for review]
**Started**: [When work began]
## Completed Work
1. [Task 1] — [files changed, what was done]
2. [Task 2] — [files changed, what was done]
### Key Decisions Made
- Chose X over Y because [reason]
- Used pattern Z from [existing file] for consistency
## Remaining Work
1. [ ] [Next task] — [specific files, what to do]
2. [ ] [Following task] — [dependencies, approach]
### Blockers
- [Any blocking issues with context]
## Key Files
- `src/auth/oauth.ts` — Main implementation file (modified)
- `src/auth/types.ts` — Type definitions (new)
- `tests/auth/oauth.test.ts` — Tests (partially written)
## Patterns to Follow
- Auth middleware pattern from `src/middleware/jwt.ts`
- Error handling style from `src/errors/`
## Gotchas Discovered
- The `UserService` caches aggressively — clear cache after auth changes
- Test DB needs `--runInBand` flag to avoid connection pool exhaustion
## Commands
- Build: `npm run build`
- Test: `npm test -- --runInBand`
- Verify: `npm run typecheck`
## How to Continue
1. Read this handoff document
2. Check `git status` and `git log -5 --oneline` for current state
3. Start with [specific next task]
4. Reference [specific file] for the pattern to follow
User: "Create a handoff for this session"
Output: Generates a structured markdown document covering: 3 completed tasks with file paths, 2 remaining tasks with specific instructions, 4 key files with their roles, 2 gotchas discovered during the session, and exact build/test commands.
Inspired by: oh-my-opencode /handoff command
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Applies abstract interpretation using different abstract domains (intervals, octagons, polyhedra, sign, congruence) to statically analyze program variables and infer invariants, value ranges, and relationships. Use when analyzing program properties, inferring loop invariants, detecting potential errors, or understanding variable relationships through static analysis.
The English summary is being prepared. Showing the original description.
Uses abstract interpretation to automatically infer loop invariants, function preconditions, and postconditions for formal verification. Generates invariants that capture program behavior and support correctness proofs in Dafny, Isabelle, Coq, and other verification systems. Use when adding formal specifications to code, generating verification conditions, inferring contracts for functions, or discovering loop invariants for proofs.
The English summary is being prepared. Showing the original description.
Performs abstract interpretation over source code to infer possible program states, variable ranges, and data properties without executing the program. Reports potential runtime errors including out-of-bounds accesses, null dereferences, type inconsistencies, division by zero, and integer overflows. Use when analyzing code for potential runtime errors, performing static analysis, checking safety properties, or verifying program behavior without execution.
The English summary is being prepared. Showing the original description.
Performs abstract interpretation to produce summarized execution traces and high-level program behavior representations. Highlights key control flow paths, variable relationships, loop invariants, function summaries, and potential runtime states using abstract domains (intervals, signs, nullness, etc.). Use when analyzing program behavior, understanding execution paths, computing loop invariants, tracking variable ranges, detecting potential runtime errors, or generating program summaries without concrete execution.
The English summary is being prepared. Showing the original description.
Create ACSL (ANSI/ISO C Specification Language) formal annotations for C/C++ programs. Use this skill when working with formal verification, adding function contracts (requires/ensures), loop invariants, assertions, memory safety annotations, or any ACSL specifications. Supports Frama-C verification and generates comprehensive formal specifications for C/C++ code.
The English summary is being prepared. Showing the original description.
CLI-based browser automation with persistent page state using ref-based element interaction. Use when users ask to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
The English summary is being prepared. Showing the original description.