agentleFS
st0012st0012/cctop/.agents/skills/cctop-restart/SKILL.md

cctop-restart

Skill151 starsChanged 3 months agoMITView on GitHub

Restart cctop for local development and testing. Use when the user asks to restart, relaunch, run, or prepare the cctop app locally; ensures the current cctop-hook is installed before the menubar app is relaunched and verified.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

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

    When the user asks to restart or relaunch cctop during development, treat it as an end-to-end client refresh:

    line 8
  2. Very specific:

    Run ./script/build_and_run.sh --verify from the repo root when available.

    line 10
  3. Very specific:

    If the script is unavailable, run make restart.

    line 11
  4. Very specific:

    Verify ~/.cctop/bin/cctop-hook reports or contains the current Config.hookVersion.

    line 12
  5. Very specific:

    Verify the running CctopMenubar process path points at the current worktree/debug app.

    line 13
  6. Very specific:

    Do not use make run or open ...CctopMenubar.app alone for restart requests.

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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

cctop Restart

When the user asks to restart or relaunch cctop during development, treat it as an end-to-end client refresh:

  1. Run ./script/build_and_run.sh --verify from the repo root when available.
  2. If the script is unavailable, run make restart.
  3. Verify ~/.cctop/bin/cctop-hook reports or contains the current Config.hookVersion.
  4. Verify the running CctopMenubar process path points at the current worktree/debug app.

Do not use make run or open ...CctopMenubar.app alone for restart requests; those can leave shims using a stale installed hook.

After cctop investigation, validation, delegated PR work, or any workflow that launches or kills the dev app, leave the verified debug app running for the developer unless the user explicitly asks to stop it or a concrete blocker prevents a safe relaunch. Report the running app path and installed hook version. Do not stop the app at the end merely to keep the process table tidy; the developer uses the app while reviewing the work.

For delegated task closeout after merge, make restart/app state part of the handoff: confirm the developer-facing app is running when relevant, then archive or park the driver thread. Only remove the driver worktree after confirming no app, build, test, or agent process is still running from it.

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.