agentleFS
sefaertuncsefaertunc/Worclaude/.claude/skills/review-and-handoff/SKILL.md

review-and-handoff

Skill4 starsChanged 7 months agoMITView on GitHub

Session ending protocol, HANDOFF document format, seamless continuation between sessions

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every session should end cleanly.

    line 11
  2. Distinctive:

    Commit any working code (don't leave uncommitted changes)

    line 15
  3. Distinctive:

    Run tests to confirm nothing is broken

    line 16
  4. Distinctive:

    If mid-task, write a HANDOFF document

    line 18
  5. Very specific:

    When ending mid-task, PROGRESS.md isn't enough.

    line 49
  6. Distinctive:

    If no, the handoff is missing context.

    line 97
  7. Distinctive:

    Don't skip the handoff because "it's almost done." You might not get back to this task for days.

    line 101
  8. Distinctive:

    Always commit before writing the handoff.

    line 105
  9. Distinctive:

    If the code isn't committed, the handoff points to nothing.

    line 106
  10. Distinctive:

    Update PROGRESS.md even if you write a HANDOFF.

    line 107

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Review and Handoff

Session Ending Protocol

Every session should end cleanly. The /end command triggers this, but understanding the protocol matters more than the command.

Before ending:

  1. Commit any working code (don't leave uncommitted changes)
  2. Run tests to confirm nothing is broken
  3. Update PROGRESS.md
  4. If mid-task, write a HANDOFF document

PROGRESS.md Update

PROGRESS.md is the single source of truth for project state across sessions.

Update these sections:

## Current Status
{What phase/feature is active}

## Completed This Session
- {Specific thing done}
- {Another specific thing done}

## In Progress
- {What's partially done, and where it stands}

## Blockers
- {Anything preventing forward progress}

## Next Steps
- {Ordered list of what to do next}

Be specific. "Worked on auth" is useless. "Implemented JWT token generation and validation in src/auth/tokens.js; unit tests passing; integration tests not yet written" is useful.

HANDOFF Document Format

When ending mid-task, PROGRESS.md isn't enough. Write a handoff at docs/handoffs/HANDOFF_{date}.md.

# Handoff: {Date}

## What I Was Doing
{1-2 sentences on the exact task}

## Current State
- Branch: {branch name}
- Last commit: {hash and message}
- Tests: {passing/failing, which ones}
- Files changed: {list of modified files}

## What's Left
1. {Next specific step}
2. {Step after that}
3. {Final step for this task}

## Context That Matters
- {Decision made during this session and why}
- {Gotcha discovered that isn't documented elsewhere}
- {Assumption being made that should be validated}

## How to Verify When Done
{What "done" looks like for this task}

What Context Matters

Include in handoffs:

  • WHY decisions were made, not just what
  • Failed approaches and why they failed (prevents re-trying dead ends)
  • Dependencies discovered during implementation
  • Anything that surprised you about the codebase

Don't include:

  • Obvious things a fresh session can figure out from the code
  • Full code dumps (the code is in version control)
  • Speculation about future tasks unrelated to the current work

The Fresh Session Test

A good handoff passes this test: could a fresh Claude session, reading only PROGRESS.md and the HANDOFF file, continue the work without asking clarifying questions?

If no, the handoff is missing context.

Gotchas

  • Don't skip the handoff because "it's almost done." You might not get back to this task for days. What's obvious now will be opaque later.
  • HANDOFF files are ephemeral. Delete them once the task is complete. Don't let stale handoffs accumulate — they become misleading.
  • Always commit before writing the handoff. The handoff references a commit hash. If the code isn't committed, the handoff points to nothing.
  • Update PROGRESS.md even if you write a HANDOFF. PROGRESS.md is the persistent state; HANDOFF is the detailed supplement.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.