Generate a session handoff note for context resets or multi-day work.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add majiayu000/claude-skill-registry --skill handoff-lightforgelabsstudio-aide --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Handoff Lightforgelabsstudio Aide?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/majiayu000-handoff-lightforgelabsstudio-aide-claude-skill-registry)More formats (shields.io, HTML) on the badges page.
---
name: handoff
description: Generate a session handoff note for context resets or multi-day work.
---
# Handoff
Produce a concise, resumable handoff note. Focus on next actions, not a status report.
## Inputs
Ask the user for: completed tasks (file:line refs), mid-flight TODOs, blockers, ordered next actions, validation status.
Auto-collect:
- `git branch --show-current` and `git log --oneline -5`
- `gh pr status` and `git status --short`
## Output format
```markdown
# Session Handoff: <task name>
**Date:** <today> | **Branch:** <branch> | **PR:** #<n> | **Issue:** #<n>
## Context
<1-2 sentence summary>
## Completed
- <specific change with file:line>
## In Progress
- <specific TODO, mid-flight>
## Blockers
- <blocker or "none">
## Next Actions
1. <first step on resume>
## Validation
Tests: passing | failing (<failures>) | Lint: passing | failing
```
## Where to post
Ask the user — post to PR comment, issue comment, or print only. Never commit.
```bash
gh pr comment <n> --body-file handoff.md
gh issue comment <n> --body-file handoff.md
```
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.