handoff
Compact the current conversation into a handoff document for another agent to pick up.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 2
- Forks
- 1
01 前言 Front Matter
- name
- handoff
- description
- Compact the current conversation into a handoff document for another agent to pick up.
- argument-hint
- What will the next session be used for?
- disable-model-invocation
- true
02 资源文件 1
- 许可证LICENSE.txt1.0 KB
03 SKILL.md 正文
Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary directory of the user's OS ($TMPDIR, else /tmp; %TEMP% on Windows) - not the current workspace.
Include a "suggested skills" section in the document, naming which skills the next agent should call the Skill tool for.
Do not duplicate content already captured in other artifacts (specs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.
Redact any sensitive information, such as API keys, passwords, or personally identifiable information.
If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.
04 同仓库更多 Skills
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
tdd
Test-driven development for ASP.NET Core and EF Core with xUnit. Use when building a feature or fixing a bug test-first, when the user mentions TDD or red-green-refactor, or when adding integration tests for endpoints or data access.
retro
Conduct a retrospective on a coding session.
pr
Use when writing a PR body.
postgresql
PostgreSQL gotchas and version-gated facts - indexing (B-tree, GIN, GiST, BRIN, partial, expression), JSONB, EXPLAIN ANALYZE and tuning, row-level security and multi-tenancy, full-text search, partitioning, connection pooling, extensions, logical replication, pgvector and RAG. Use when designing tables or indexes for PostgreSQL, writing or reviewing raw SQL, diagnosing a slow query, or choosing a PostgreSQL feature. For EF Core query performance use the optimizing-ef-core-queries skill; for migrations follow the ef-migrations rule.
improve-codebase-architecture
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.