chapter-handoff

Records a review request on a devbook chapter and builds the reviewer's brief.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/JSdotNet/devbook --skill chapter-handoff-jsdotnet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chapter-handoff
Source: https://github.com/JSdotNet/devbook/tree/main/plugins/devbook-collaboration/skills/chapter-handoff
Command: npx skills add https://github.com/JSdotNet/devbook --skill chapter-handoff-jsdotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Handing a devbook chapter to a reviewer often loses context between sessions: the reviewer does not know what changed, what judgment is being asked for, or which related chapters to read. This Skill writes the review request into the chapter's own metadata so the ask survives the session, and produces a complete brief the reviewer can start from. ## Core Features & Use Cases - Durable review requests: Writes review, reviewer, and review-at fields into the chapter's meta block, overwriting any prior request so a chapter waits on exactly one reviewer. - Reviewer brief generation: Builds a four-part brief covering the ask, what changed since last approval, neighbouring chapters reachable through related and depends-on, and evidence from the chapter's tests entries plus open annotations. - Use Case: You finished revising an architecture chapter and need a domain expert to judge it before approval. Run the handoff to record the request on the chapter and receive a ready-to-send message with the commit history, context chapters, and open findings. ## Quick Start Ask the agent to hand off the chapter at a given path and slug to a named reviewer and produce the brief to send them.

Frequently Asked Questions about chapter-handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I request a review of a devbook chapter?▼

Provide the chapter's path#slug address and name a reviewer by handle, name, or role. The skill writes review: requested, reviewer, and review-at into the chapter's meta block and returns a brief you send to the reviewer.

What goes into the reviewer brief for a chapter handoff?▼

The brief has four parts: the chapter address and the judgment being asked, commits touching the chapter since its last approved-at, chapters reachable in one step through related and depends-on, and the tests entries plus open annotation fences.

Can a chapter have more than one pending review request?▼

No. A chapter waits on one reviewer, so a new handoff overwrites the existing review request fields rather than adding a second request. Open notes from earlier passes are left untouched.

Does handing off a chapter approve it or notify the reviewer?▼

No. The skill never writes status: approved, which belongs to chapter-approve after a review clears, and it does not notify anyone or post the brief anywhere. Handing the brief back to you is the deliverable.

What happens if a chapter heading has no meta block?▼

A heading without a meta block is not addressable, so the skill requires adding one before any handoff. The review request fields live in that meta block, making it a prerequisite for recording the ask.