agentleFS
BinayakDotelBinayakDotel/skills-marketplace/skills/stop-preview/SKILL.md

stop-preview

Skill1 starsChanged 36 days agoMITView on GitHub

Stop the local app started by /preview-pr without restarting the previous server or deleting its Convex deployment. Use when the user says /stop-preview.

  • Reads credentials

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Remove the marker after a successful stop.

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

/stop-preview

  1. List the repo's worktrees and find the one with an ignored .run/preview-pr marker. If more than one is marked, ask which PR to stop. If none is marked, say no PR preview is recorded; do not stop an unrelated process.
  2. Verify that this worktree still owns the running app using the repo's process record (in Kuhiro, .run/pids). If it does, run just stop from that worktree. The repo's stop recipe may kill any listener on its app port, so do not call it if an unrelated process now owns that port. If the recorded process is already gone, clear the stale marker and report that nothing was running.
  3. Remove the marker after a successful stop. Report the PR number and worktree. Leave the worktree, its .env.local, and any selected Convex deployment intact; do not restart the server that ran before the preview.

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.