agentleFS
Sign inStart free
surasakchosurasakcho/claude-skills/wrap/SKILL.md

wrap

Skill0 starsChanged 5 months agoMITView on GitHub

End-of-session ritual — summarize the session, update project logs, commit and push, then write next-session handoff notes into a committed project file. Use when the user says "wrap", "wrap up", "hand off", or otherwise signals they're closing out for now.

45 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use start, update and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    start

    Set up your bio-research environment and explore available tools. Use when first getting oriented with the plugin, checking which literature, drug-discovery, or visualization MCP servers are connected, or surveying available analysis skills before starting a new project.

    Also in 5 projects that use this

  • AnthropicSkill

    update

    Sync tasks and refresh memory from your current activity. Use when pulling new assignments from your project tracker into TASKS.md, triaging stale or overdue tasks, filling memory gaps for unknown people or projects, or running a comprehensive scan to catch todos buried in chat and email.

    Also in 3 projects that use this

  • LangChainSkill

    remember

    Review the current conversation and capture valuable knowledge — best practices, coding conventions, architecture decisions, workflows, and user feedback — into persistent memory (AGENTS.md) or reusable skills. Use when the user says: (1) remember this, (2) save what we learned, (3) update memory, (4) capture learnings.

    Also in 3 projects that use this

  • termdockSkill

    recall

    Retrieves cross-session memories about past decisions, lessons, and patterns. Use when user asks about prior work, past decisions, or mentions a feature. Triggers include check memory, what did we decide, how did we solve.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    build

    Build the TypeSpec Rust emitter from source. Run this after cloning the repo, after pulling changes, or when TypeScript source files have been modified.

    Also in 3 projects that use this

  • SentrySkill

    spec

    Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.

    Also in 3 projects that use this

  • +1 more from anthropics

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 6 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 40 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check this project's CLAUDE.md for a custom wrap ritual.

    line 10
  2. Distinctive:

    Run git status and git diff.

    line 14
  3. Distinctive:

    Write a short summary (a few sentences) of what was done this session: what changed and why.

    line 18
  4. Very specific:

    Look for established conventions — a changelog, worklog, ADR directory, TODO/DONE tracker, .changeset/ in JS repos.

    line 22
  5. Distinctive:

    If new conventions were established this session that CLAUDE.md doesn't capture yet, update CLAUDE.md too.

    line 24
  6. Distinctive:

    Do not invent a new log file just because none exists — that's the project owner's call.

    line 26
  7. Distinctive:

    Ask the user: "Anything specific to note for next session?" If they give input, use it.

    line 34
  8. Very specific:

    Add or update a ## Next Session section with: what was done, what to do next, known bugs/blockers, suggested skills

    line 38
  9. Very specific:

    Commit only the handoff file with message docs: handoff notes for next session

    line 39
  10. Distinctive:

    Never write handoff notes to OS temp or claude memory.

    line 42

“Common” is measured: kept by at least 6 in 10 of the 40 edited versions of this file we could read. “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

Close out the current session. Steps run in order; never save session notes to OS temp or claude memory — everything must end up committed and pushed.

1. Check for a project-defined wrap convention first

Check this project's CLAUDE.md for a custom wrap ritual. If one is defined, follow it exactly instead of the steps below.

2. Check for anything to wrap

Run git status and git diff. If there are no staged/unstaged changes and nothing meaningful happened this session, say so and stop — don't manufacture a commit.

3. Summarize the session

Write a short summary (a few sentences) of what was done this session: what changed and why. Scoped to this conversation's work, not a general changelog.

4. Update project-specific logs, only if they already exist

Look for established conventions — a changelog, worklog, ADR directory, TODO/DONE tracker, .changeset/ in JS repos. If one exists, update it consistent with its existing format.

If new conventions were established this session that CLAUDE.md doesn't capture yet, update CLAUDE.md too.

Do not invent a new log file just because none exists — that's the project owner's call.

5. Commit and push work

Stage the relevant files (never a blanket git add -A) and commit, following this repo's existing commit message style. Push to the current branch's upstream.

6. Write and push handoff notes (always, as a separate commit)

Ask the user: "Anything specific to note for next session?" If they give input, use it. If they say no or don't respond, write a brief note based on what you know needs doing next.

Then, before finishing:

  • Find or create the handoff target file (CONTEXT.md → HANDOFF.md → TODO.md, in that order; create HANDOFF.md if none exist)
  • Add or update a ## Next Session section with: what was done, what to do next, known bugs/blockers, suggested skills
  • Commit only the handoff file with message docs: handoff notes for next session
  • Push immediately — this is a separate push from step 5; the handoff must reach the remote before the session ends

Never write handoff notes to OS temp or claude memory. The session is not complete until this push succeeds.

7. Report back

One short summary: what was committed, whether any project logs were updated, and confirmation it pushed — with the remote/branch.

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.

Check your setup, free