smithery.ai

handover

Create or update a concise handover doc for the current repo/session.

First seen Mar 21, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,333 B
  • docs SUMMARY.md 85 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 4 installs

SKILL.md

Handover doc

Create or update a handover doc for the current repo.

Location

  • If repodocs/prompts/ exists -> use it.
  • Else use docs/prompts/.

Filename

  • YYYY-MM-DD-handover-<topic>.md
  • <topic> is auto-slugged on creation, using best available context:

- Prefer PR title (if PR exists for current branch). - Else a short task/context summary (e.g., feature name, incident, or subsystem). - Else latest commit subject.

  • If the user requests a specific slug/topic, honor it.
  • On update: do not rename; update existing file unless the user requests a new file.

Data sources

  • Date: date +%Y-%m-%d
  • Updated: date -u +%Y-%m-%dT%H:%M:%SZ
  • Host: hostname
  • Repo path: pwd
  • Branch: git rev-parse --abbrev-ref HEAD
  • HEAD: git rev-parse HEAD
  • Git status: git status -sb
  • PR (if available): gh pr view --json number,title,url

Format (bullets only)

  • Date: …
  • Updated: …
  • Host: …
  • Repo: …
  • Branch + HEAD: …
  • PR: (if available) #1234 Title (URL)
  • State:

- clean/dirty - merge state (if any) - CI/deploy status (if relevant)

  • Work done:

- …

  • Next:

- …

  • Notes:

- …

  • Git status:

- ``text ## branch...origin/branch M file ``