smoke-test
Skill1 starsChanged 9 months agoMITView on GitHub
Generate and maintain a local deploy script (scripts/deploy.sh). Discovers project services, deploys them locally, and health-checks each one. Use when the user asks to "smoke test", "deploy locally", "test local deploy", "update deploy script", "run deploy", or "run smoke test".
22 other projects use a version of this.
Adopted by
Most recently taken up by
- mjswensen/skillstheir own version, first seen Nov 15, 2026
- crbnos/carbontheir own version, first seen Nov 15, 2026
- AJschoons/robowrighttheir own version, first seen Nov 8, 2026
- blamechris/chroxytheir own version, first seen Nov 8, 2026
- danielvm-git/bigpowerstheir own version, first seen Nov 6, 2026
- dspace-group/SystemDeskMCPtheir own version, first seen Nov 1, 2026
Used with
Projects with it also use debugging-difficult-bugs, pr-explainer and 2 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.
dzevsSkilldebugging-difficult-bugs
Use early when debugging a medium or hard bug, especially when tests alone may not reveal the real runtime failure. Trigger this before extended TDD iteration when a bug involves runtime state, PTY/terminal ordering, persistence, streaming, async/concurrency, the TUI/manual reproduction, the IPC socket layer, or when a red or newly passing test may not model the real issue. Skip only when the root cause is already directly proven by a stack trace or deterministic test that exercises the real runtime path.
Also in 3 projects that use this
Mathews-TomSkillpr-explainer
Use when a developer asks to explain a pushed PR, walk through a PR stack, understand one stack member, or explain what an AI agent just pushed so they can connect code changes to end-to-end functionality and update domain knowledge. Not for defect review, merge approval, PR-body authoring, or full-repository onboarding.
Also in 3 projects that use this
dzevsSkillpr-splitter
Use when breaking a large, complex, messy, or hard-to-review pull request into multiple smaller PRs; planning stacked PRs; extracting independent changes from a branch; splitting mixed refactor and behavior changes; managing drift after review feedback (operator gate, Codex/swarm second opinion); rebasing follow-up PRs as earlier PRs change; or preserving original branch intent while shipping incrementally.
Also in 3 projects that use this
GitHubSkillcommit-message
Generate conventional commit messages - use when creating commits, writing commit messages, or asking for git commit help
Also in 3 projects that use this
Other versions22 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 22
- garrytan/gbrain★ 33ksame name
- mastra-ai/mastra★ 30ksame name
- JoshuaC215/agent-service-toolkit★ 4.6ksame name
- crbnos/carbon★ 2.8ksame name
- peteonrails/voxtype★ 1.8ksame name
- nginx/nginx-s3-gateway★ 764same name
- danielvm-git/bigpowers★ 292same name
- andrew-yangy/gru-ai★ 153same name
- stacklok/toolhive-registry-server★ 29same name
- sohei56/maul-team★ 17same name
12 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- bug-bash-updateSkill
- ci-cd-pipelineSkill
- claudemd-auditorSkill
- docs-consolidatorSkill
- ralphSkill
- refactor-auditSkill
- reflectSkill
- setup-workflowSkill
- skill-reviewerSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
1
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
- Very specific: line 34
If an existing scripts/deploy.sh exists, produce a diff:
- Very specific: line 42
Write or update scripts/deploy.sh (create the scripts/ directory if needed)
- Distinctive: line 58
If it fails, diagnose and fix the script (not the project code — the script should reflect reality)
“Common” is measured: kept by at least 6 in 10 of the 19 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.
Files
Local Deploy Script
Generate and maintain a scripts/deploy.sh script that deploys the project locally and health-checks each service. Designed to be called repeatedly — each invocation re-audits the project and adds, removes, or updates stages to match what's currently deployed.
Workflow
Phase 1: Discover project state
Build a project profile by detecting:
- Language & runtime — Check file extensions and config files (
pyproject.toml,package.json,go.mod,Cargo.toml, etc.). Note the minimum required version (e.g.,requires-python = ">=3.11"). - Package manager — pip/uv/poetry, npm/yarn/pnpm, cargo, go modules, etc.
- CLI entry point —
main.py,src/index.ts,cmd/main.go,Cargo.toml [[bin]], etc. - CLI commands — Parse argument parsers or command definitions to find subcommands.
- Key modules — Identify services, servers, and infrastructure components (databases, chain nodes, etc.).
- Existing scripts/deploy.sh — If present, read it to understand current stages and compare with detected state.
Phase 2: Design stages
Map discovered state to stages. Only include stages for services and infrastructure that are implemented.
Standard stage ordering:
- Environment — Required tools and runtimes are available (version checks, binary existence)
- Build — Compile/build steps needed before services can start (e.g.,
forge build,pnpm build,cargo build) - Start services — Start infrastructure (database, chain node, message queue) and application services (backend, frontend, indexer). Use a cleanup trap (
trap cleanup EXIT) to tear down all started services on both success and failure. - Health-check — Verify each service responds correctly (HTTP endpoints return 200, RPC nodes answer queries, databases accept connections, pages load)
If an existing scripts/deploy.sh exists, produce a diff:
- Stages to add (new services or infrastructure detected since last run)
- Stages to remove (services removed)
- Stages to update (ports, commands, or endpoints changed)
- Stages unchanged
Phase 3: Execute
- Write or update
scripts/deploy.sh(create thescripts/directory if needed) - Script structure:
#!/usr/bin/env bashset -euo pipefail- Each stage is a function:
stage_N_name() - Each stage prints
--- Stage N: <name> ---before running - On success: prints
PASS: <check> - On failure: prints
FAIL: <check>and exits immediately - Final line on success:
echo "DEPLOY OK" - The
set -eflag handles fail-fast automatically
- Run
chmod +x scripts/deploy.sh
Phase 4: Verify
- Run
./scripts/deploy.sh - Confirm it exits 0 with
DEPLOY OK - If it fails, diagnose and fix the script (not the project code — the script should reflect reality)
- Report result to user
Guidelines
- Deploy only — No static analysis, linting, typechecking, or tests. CI handles verification.
- Idempotent — Safe to run repeatedly. No side effects beyond temporary files (cleaned up).
- Only deploy what's implemented — Never include services that aren't wired up yet.
- Fast — Prefer offline stages, but if the feature being tested requires network (e.g., fetching exchange data), include it. Guard network stages with a credentials check — if credentials aren't configured, prompt the user interactively (via
read -p) and continue. Never persist credentials or silently skip functional stages. - Language-agnostic — Detect Python/Node/Go/Rust/etc. patterns from config files. Don't hardcode for any language.
- Portable — Use POSIX-compatible bash. Avoid platform-specific commands where possible.
- Minimal output on success — Each stage prints its name and PASS/FAIL. No verbose logs unless a stage fails.
- No project code changes — The skill only creates/updates
scripts/deploy.sh. It never modifies source code, tests, or configuration.
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.

