handover

Solid

Use when handing finished work over to code review — writing a PR description or packaging a change for review by a human, an agent, or both.

AI & Automation 46 stars 6 forks Updated today MIT

Install

View on GitHub

Quality Score: 86/100

Stars 20%
56
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Handover Package a finished change so its reviewers never reconstruct intent from the diff. Write for a reviewer holding the diff and nothing else — no planning docs, no session, no knowledge that either exists. ## Resolve the task The input is any partial reference — ticket id, slug, a planning artifact's path — or nothing, meaning the session's task; in a fresh session, infer it from branch name and recent commits. Resolve it to the task's **planning home**: its `<id>-<slug>/` directory in the project's planning directory, or its flat `<id>-<slug>.*` files in a shared family directory. One clear match → proceed, stating the home and artifacts found. Inferred, or several candidates (`-vN`, …) → confirm first. An explicit reference matching nothing local → stop and ask; never guess. ## Gather Read these, skipping what doesn't exist: 1. **Task artifacts** — every `<id>-<slug>*.md` in the planning home: ticket, requirements, plan, decisions log, prior review and handover rounds, whatever else matches. 2. **Related tickets** — one hop only: parent (climbing higher only past thin containers), direct predecessors/successors, explicit relations, family-directory siblings; never expand their own relations. Local `.TICKET.md`s first; fetch from the tracker only when a relation has no local file and looks load-bearing for a why — in doubt whether to fetch, ask. 3. **The session**, when it produced the change: decisions, pivots, constraints. 4. **The diff** against ...

Details

Author
eai-org
Repository
eai-org/agent-toolkit
Created
3 months ago
Last Updated
today
Language
Shell
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category