agentleFS
Sign inStart free
CG-5228CG-5228/ClaudeCodeImpactLab_hackathon/skills/resume/SKILL.md

resume

Skill1 starsChanged 13 days agoMITView on GitHub

Restore the latest StopCode handoff and mission for this project. If quiet hours are active, asks for an explicit override before lifting them. Use when the user runs /stopcode:resume or wants to pick the parked work back up.

58 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use report, config and 7 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.
  • MicrosoftSkill

    report

    Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded charts.

    Also in 7 projects that use this

  • MicrosoftSkill

    config

    Show or change TokenEconomizer's settings: turn micro-skills, tool pruning or the loop guard on or off, or tune them, for this repository or (with --global) every repository. Use when the user asks to configure, enable or disable TokenEconomizer or one of its mechanisms.

    Also in 3 projects that use this

  • sahinSkill

    execute

    Also in 4 projects that use this

  • u9401066Skill

    bug-fix

    Structured bug fixing workflow with root cause analysis and regression prevention. Triggers: BF, 修 bug, fix bug, debug, 除錯, 錯誤, error, 問題, issue, 修復, fix, 故障, fault, 異常, exception, 失敗, failure, 不能用, broken, 壞掉.

    Also in 3 projects that use this

  • GitHubSkill

    state-management

    CoreAI Sandbox's TanStack Query + mock-JSON data layer. USE WHEN: editing data-fetching hooks (`app/hooks/use*.ts`), adding mock data in `app/data/`, or wiring a component to query state.

    Also in 3 projects that use this

  • HermeticOrmusSkill

    close

    End-of-session ritual. Captures session state, updates auto-memory, writes a session summary, then exits the session cleanly.

    Also in 3 projects that use this

  • +2 more from microsoft

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 51 edited versions we read keep these.

  • 2

    Distinctive

    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. Very specific:

    Run without an override first (unless the user already passed --override, in which case go to step 2's second command):

    line 17
  2. Distinctive:

    If they say no, stop here.

    line 29
  3. Distinctive:

    If there is no handoff yet, say so and show the mission status instead.

    line 36

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

/stopcode:resume

Arguments from the user: $ARGUMENTS

During quiet hours the StopCode hook lets only a bare StopCode command through: run each command below exactly as written, on its own line, with no cd, no &&, no ;, no pipes and no redirection. Read the command's text output; do not append anything to inspect exit codes.

Steps

  1. Run without an override first (unless the user already passed --override, in which case go to step 2's second command):

    node "${CLAUDE_PLUGIN_ROOT}/bin/stopcode.js" resume

  2. If the output says quiet hours are active ("Quiet hours are active ... Resume with an explicit override"): tell the user when the interval ends and ask one explicit yes/no question: "Lift the quiet-hours boundary now?" Only if the user clearly says yes (or already passed --override), run:

    node "${CLAUDE_PLUGIN_ROOT}/bin/stopcode.js" resume --override

    If they say no, stop here; their work stays parked and the wellness chat in the dashboard remains available.

  3. On success, show at most 10 lines: the mission, its status headline, the next action, and the resume-context block from the handoff. Mention the handoff path for the full receipt.
  4. Then stop and wait. Do not start implementing the next action, run tests, or open files until the user asks. Resuming restores context; it does not launch work.

Rules

  • Completed and archived missions stay in history; resuming never deletes them.
  • If there is no handoff yet, say so and show the mission status instead.

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