aspire-stop
Skill439 starsChanged 6 months agoMITView on GitHub
Stop the .NET Aspire AppHost and its Docker containers via the developer CLI. Defaults to the current worktree; supports stopping all worktrees or a specific base port.
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- aspire-restartSkill
- buildSkill
- commitSkill
- create-prdSkill
- create-pull-requestSkill
- db-querySkill
- e2eSkill
- enhanced-message-contextSkill
- fix-e2e-testsSkill
- formatSkill
- lingui-best-practicesSkill
- lintSkill
- pull-platformplatform-changesSkill
- rebrandSkill
- rebuild-branchSkill
- swc-plugin-compatibilitySkill
- team-interruptSkill
- testSkill
- ultra-reviewSkill
- upgrade-packagesSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Very specific: line 12
Use developer-cli exactly as written - do not expand to an absolute worktree path.
- Distinctive: line 26
Before deleting a worktree, to ensure its Docker containers don't leak.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
Stop Aspire
dotnet run --project developer-cli -- stop [--all] [--port <basePort>]Use developer-cli exactly as written - do not expand to an absolute worktree path.
Stops the Aspire AppHost and its associated Docker containers (postgres, azurite, mailpit, stripe-cli) - not just the Aspire process. Persistent containers survive a plain aspire stop by design, so this skill cleans them up too.
- (no flag) - stop the current worktree's stack
--all- stop every worktree of this repository (viagit worktree list). Only use when the user explicitly asks to stop everything - never as a default--port <basePort>- stop the worktree on that base port (e.g.9000,9100,9200); also cleans up Docker containers for that port even if the worktree was deleted
The flags are mutually exclusive.
When to use
- To free up ports without restarting (rare -
aspire-restartis the everyday default). - To stop a stack from another worktree without switching to it (
--port). - Before deleting a worktree, to ensure its Docker containers don't leak.
Output
The CLI prints what it stopped (Aspire process trees + each docker rm --force'd container) and exits.
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
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.