agentleFS
Sign inStart free
matthewwong525matthewwong525/WongStack/.agents/skills/close/SKILL.md

close

Skill7 starsChanged 11 days agoMITView on GitHub

Wrap up a chat: save what it learned, update the wiki, keep unfinished work, close the workspace.

26 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use open, reconcile and 6 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.
  • BlockSkill

    open

    Open markdown documents in Penpal for collaborative review. Use when you want a human to review a document, plan, or research artifact.

    Also in 5 projects that use this

  • howellsSkill

    reconcile

    Audit a project against current plugin conventions and offer to update structure.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    validate

    Run the full CI validation workflow locally before submitting a PR. Use this as a final check to ensure all Azure DevOps CI pipeline steps will pass.

    Also in 4 projects that use this

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

  • OpenAISkill

    bootstrap

    Project bootstrapping orchestrator for repos that depend on Vercel-linked resources (databases, auth, and managed integrations). Use when setting up or repairing a repository so linking, environment provisioning, env pulls, and first-run db/dev commands happen in the correct safe order.

    Also in 3 projects that use this

  • genomewalkerSkill

    resume

    Resume a thread by loading its ~800-token context capsule

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 2

    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:

    Use conversation/tasks and the write gate: project fact for goal/result, threads for remaining pieces with next step/blocker, supersedes …

    line 13
  2. Very specific:

    Read git status --porcelain, git log origin/main..HEAD, gh pr view --json state,headRefOid,url.

    line 17
  3. Very specific:

    Use active/archived CHANGE_NAME.

    line 31
  4. Distinctive:

    After the reply, archiving stops workspace processes, not shared services.

    line 45

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

/close authorizes these steps, including save/ship. Discard only when explicitly requested.

1. Write the wrap-up

Use conversation/tasks and the write gate: project fact for goal/result, threads for remaining pieces with next step/blocker, supersedes for resolved threads. Save carries them.

2. Pick a route

Read git status --porcelain, git log origin/main..HEAD, gh pr view --json state,headRefOid,url. Paseo worktrees have PASEO_AGENT_ID and are outside the main checkout.

  • discard: explicit request in a Paseo worktree. Save facts, skip wiki. Elsewhere, keep; never discard the main checkout.
  • keep: edits or unmerged HEAD commits. Run /save verbatim; stop for failed push, otherwise name any red checks and continue. Update wiki when closing after shipment.
  • wrap: otherwise save facts, then update wiki.

Update the wiki

M="$(git rev-parse --show-toplevel)/.claude/skills/memory/scripts/memory.mjs"
node "$M" show "$CHANGE_NAME"
node "$M" search --branch "$BRANCH" --change "$CHANGE_NAME" --limit 200

Use active/archived CHANGE_NAME; without one, omit show/--change. On main omit --branch. Deduplicate session facts; place repeatable ones. Report unreachable memory and continue.

Save knowledge/ pages at once; report the undo line. Publish other edits alone. After a merge, first git fetch origin main, git switch -c "$BRANCH-wiki" origin/main, and git branch -D "$BRANCH". Then invoke /ship, minus its closing step. No edit → report no repeatable fact.

3. Close

S="$(git rev-parse --show-toplevel)/.claude/skills"
node "$S/memory/scripts/memory.mjs" keep-transcript current # never stops the close
node "$S/hand-over/scripts/hand-over.mjs" close # only when this chat's private link is open
node "$S/explore/scripts/step-title.mjs" remove # off the Inbox's chat list; never stops the close
node "$S/schedule/scripts/tidy.mjs" close # --discard on that route

After the reply, archiving stops workspace processes, not shared services.

  • Exit 0: say the workspace is closing. Archived chat remains readable.
  • Exit 2: in the main checkout or outside Paseo, say there's no workspace to close; else give its error in plain words.
  • Exits 3 to 5: Paseo couldn't close it here; the Paseo app can archive it.

4. Report

Report plainly: facts, wiki edits, saved-work link or discard, then close result. Ask no next step; failed closes end with repair options.

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