agentleFS
Sign inStart free
mm-arturomm-arturo/claude-code-skills/skills/wrap-up/SKILL.md

wrap-up

Skill1 starsChanged 2 months agoMITView on GitHub

Prepare the current session for a PC restart or shell close. Use when

  • Reads credentials
  • Commits and pushes

62 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use refine, doctor and 10 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.
  • AlexPEClubSkill

    refine

    Always use when the user wants to discuss an exsiting feature or specification. Open an existing feature spec to improve, extend, or fundamentally challenge it. Pass the feature ID as argument (e.g. /refine PROJ-2).

    Also in 3 projects that use this

  • MicrosoftSkill

    doctor

    Diagnose an Amplifier CLI environment through the CLI doctor agent. USE WHEN a user requests CLI runtime, settings or missing-capability inspection. DO NOT USE for project bugs or other hosts.

    Also in 4 projects that use this

  • MicrosoftSkill

    sync

    Sync the current session branch with its upstream branch, or publish the current session branch to a remote. Use when the user asks to sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream.

    Also in 3 projects that use this

  • austintgriffithSkill

    orchestration

    Use when a Scaffold-ETH 2 build leaves localhost: planning the launch order, deploying and verifying contracts on a live network, standing up a fork of a real chain to rehearse a deploy, or fixing a contract bug that is already onchain. Not for running the app or a demo against that fork (`/frontend-playbook`).

    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 5 projects that use this

  • nicolasestremSkill

    brainstorm

    Structured idea generation and solution exploration with systematic analysis.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 57 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run these steps in order and report each briefly.

    line 10
  2. Very specific:

    Commit: stage meaningful changes with a descriptive message summarizing this session.

    line 36
  3. Very specific:

    Create or update HANDOFF.md at repo root with today's date:

    line 40

“Common” is measured: kept by at least 6 in 10 of the 57 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

Session wrap-up

Run these steps in order and report each briefly.

  1. Inspect: git status and git diff --stat. List important untracked files.
  2. Guard secrets: never stage .env, keys, wallets, or gitignored files. If a secret is tracked, STOP and warn instead of committing.
  3. Persist lessons: review this session for durable knowledge a future session would otherwise re-learn. Candidates:
    • corrections the user made to my behavior or output
    • environment quirks discovered the hard way (commands, flags, paths, versions, workarounds)
    • wrong assumptions I had to abandon mid-session
    • workflow or performance optimizations that verifiably worked Route each item to the right permanent home:
    • project-specific -> project CLAUDE.md (or .claude/rules/), so it ships with the repo
    • applies across all projects -> ~/.claude/CLAUDE.md
    • improves an existing skill's procedure -> edit that SKILL.md directly
    • a genuinely new repeatable workflow -> propose a new skill, but ask before creating it Quality bar - persist only what is (a) verified this session, (b) non-obvious, (c) likely to recur. Write each as one short imperative rule, not a story. Check for duplicates first; prefer rewriting an existing line over appending a near-duplicate. If nothing meets the bar, say so and skip. Finish by listing exactly what was written to which file, so the user can veto before commit.
  4. Commit: stage meaningful changes with a descriptive message summarizing this session. Prefix wip: if work is unfinished. If tests are fast, run them and note the result.
  5. Push the current branch (git push -u origin <branch> if no upstream).
  6. Create or update HANDOFF.md at repo root with today's date:
    • completed this session
    • in progress, and exactly where it stopped (file/function)
    • next 1-3 concrete steps
    • known issues / failing tests / open questions
    • commands to resume (venv activation, env vars, services)
    • standing rules / skills updated this session: one line per change with the file and the rule (copied from the persist-lessons step; write "none" if nothing was persisted)
  7. Confirm: print commit hash + branch, and remind that claude --continue resumes this session after restart.

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