wrap-up

Q: How do I install wrap-up?

Run npx skills add https://github.com/codewithmukesh/dotnet-claude-kit --skill wrap-up in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/wrap-up/ (personal) or .claude/skills/wrap-up/ (project).

by codewithmukeshCode Quality & Workflow

Owns the session handoff lifecycle: the end-of-session ritual that captures completed work, pending tasks, and learnings into .claude/handoff.md, and the session-start protocol that loads it back. Triggers on: /wrap-up, "wrap up", "done for today", "that's all", "end session", "signing off", "handoff" — and at session start: "start session", "session start", "load handoff", "pick up where we left off", "what were we working on".

Installs: 2.8K
Last 24h: +55
Trending rank: #3134
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/codewithmukesh/dotnet-claude-kit --skill wrap-up

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads wrap-up automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

/wrap-up

What

The session continuity ritual. Sessions are ephemeral; knowledge is permanent. Wrap-up bridges sessions in both directions:

Session END — capture exactly three things: what was DONE, what is PENDING, and what was LEARNED. Write them to .claude/handoff.md and flow durable learnings into MEMORY.md.
Session START — load the handoff, memory, and instincts, then present a resume summary so no session starts blind.

When

End of a working session — "done for today", "that's all", "signing off"
Before switching projects or after a major milestone
Implicit endings — "thanks" after completed tasks, "good enough for now": offer the handoff, don't just say goodbye
Start of a session — "start session", "load handoff", "what were we working on"
For a mid-session save without ending, use /checkpoint instead

How

Session End

Review the session — From git status/diff and the conversation: files touched, tasks completed vs unfinished, decisions made and why, user corrections observed.
Check uncommitted changes — If any exist, offer to commit before wrapping.
Write the handoff — .claude/handoff.md, using the format below. Single file, always overwritten — only the current state matters. If the existing handoff has pending tasks from someone else, ask before overwriting: merge, overwrite, or skip.
Extract learnings — Corrections and discoveries worth keeping go to MEMORY.md (via instinct-system); emerging patterns update .claude/instincts.md (via instinct-system). The handoff's Learned section is the trigger, not the destination — handoffs are ephemeral.
Confirm — Summarize the handoff and learnings captured for the user.

Handoff File Format (`.claude/handoff.md`)

Write it for a stranger with zero context — file paths, rationale, specific next steps. "Continue the refactor" is useless; "Refactor src/Orders/CreateOrder.cs to the Result pattern — see Catalog for the established pattern" is actionable.

# Session Handoff

> Generated: 2026-06-12 | Branch: feature/order-validation

## Completed
- [x] Added FluentValidation to CreateOrder (src/Orders/Features/CreateOrder.cs:15-35)
- [x] Fixed N+1 in GetOrderDetails (src/Orders/Features/GetOrderDetails.cs:28)

## Pending
- [ ] Add validation to UpdateOrder (src/Orders/Features/UpdateOrder.cs)
  - Reference: CreateOrder validator for the established pattern
- [ ] Full test run — 2 pre-existing Catalog failures, not from today

## Learned
- FluentValidation validators must be registered in the module's DI setup
- Test fixture seeds 1 item per order, which hides N+1 queries

## Context
- Branch: feature/order-validation | Last commit: "Add CreateOrder validation"
- Uncommitted changes: no | Solution: src/MyApp.slnx

When multiple developers share the project, add a ## Decisions Made table (Decision | Choice | Rationale) and ## Open Questions.

Learning Extraction Checklist

Did the user correct anything? → MEMORY.md via instinct-system
Did we discover something non-obvious? → Learned section
Did we decide something with rationale? → document the "why"
Did a tool/approach fail? → note it so the next session doesn't retry it

Good learning: "EF compiled queries don't work with Include()". Bad learning: "Worked on Orders module" (vague) or "Used TimeProvider" (already a rule).

Session Start

Load context — Read .claude/handoff.md (pending work), MEMORY.md (permanent rules), .claude/instincts.md (patterns at 0.7+ confidence). Missing files are fine: note it and start clean — never block on them.
Detect the solution — Find .slnx/.sln (current dir, then parents, then children) so Roslyn MCP tools work from the first prompt.
Present a resume summary — Last session's work, pending tasks, active rules/instincts count, detected solution. Then ask what to work on — never auto-start pending work.

Example

User: /wrap-up

Claude: Wrapping up session...

## Session Summary
- Implemented OrderService with validation pipeline
- Fixed N+1 query in GetOrdersByCustomer

## Pending
- [ ] Add retry logic to payment gateway calls (OrderService.cs:42)

## Learnings Captured
- User prefers explicit mapping over AutoMapper → MEMORY.md

Written to .claude/handoff.md. See you next session.

/checkpoint — Mid-session save (commit + brief note) without ending the session
instinct-system — Routes session learnings: patterns become instincts, user corrections become permanent MEMORY.md rules

FAQ

What does the wrap-up skill do?

How do I install wrap-up?

Run npx skills add https://github.com/codewithmukesh/dotnet-claude-kit --skill wrap-up in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/wrap-up/ (personal) or .claude/skills/wrap-up/ (project).

Which AI agents can use wrap-up?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is wrap-up safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains wrap-up?

It is published by codewithmukesh in codewithmukesh/dotnet-claude-kit. It has 2,832 recorded installs.