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 26 stars 3 forks Updated today MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
48
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. ## Gather Start the project's checks (tests, lint, build — whatever it defines) first, unless this session already ran them on this tree; read these while they run, skipping what doesn't exist: 1. **Decisions log** — a `*.DECISIONS.md` beside the task's plan. 2. **Planning docs** — the task's requirements, plan, and ticket in the project's planning directory. 3. **The session**, when it produced the change: decisions, pivots, constraints. 4. **The diff** against the target, plus commit subjects. Each source once, no deeper than the artifact needs: skim the diff whole, deep-read only the files you will name in the *Review guide*, and never rebuild history commit by commit — which commit changed what is the diff's job, not yours. Then match the plan's steps and acceptance criteria against the diff both ways — planned but absent, present but unplanned. Done when every source is read or confirmed absent and every planned item is matched. ## Never invent rationale State a "why" only where a source gives it. A deviation nothing explains is asked of the author once; unanswered or unaskable, it ships flagged in plain words ("nothing records why — worth confirming"), since it may be an unintentional gap rather than a decision. Sourcing is your gate, not the review...

Details

Author
eai-org
Repository
eai-org/agent-toolkit
Created
2 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