smoke
Skill1 starsChanged 3 months agoMITView on GitHub
Boot Hangar in demo mode and verify the critical API paths work — tickets, agents, skills, runs, and the SSE stream. Use before merging any server change, when something feels broken, or as a quick sanity check. Runs typecheck first, then spins up the server and exercises the endpoints.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- nightly-labs/openbottheir own version, first seen Nov 14, 2026
- assaio/assaiotheir own version, first seen Sep 29, 2026
- pgnzbl-ux/crucibletheir own version, first seen Aug 27, 2026
- VoxTechnologies/transmute-frameworktheir own version, first seen Jul 26, 2026
- lfrodrigues/packt-claude-code-course-auththeir own version, first seen Jul 15, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- nightly-labs/openbot★ 7.9ksame name
- assaio/assaio★ 63same name
- lfrodrigues/packt-claude-code-course-auth★ 9same name
- VoxTechnologies/transmute-framework★ 5same name
- pgnzbl-ux/crucible★ 4same name
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 repository6 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- aiwf-syncSkill
- config-fieldSkill
- docs-updateSkill
- hangar-validateSkill
- releaseSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Stop and report if typecheck fails — there's no point starting the server with broken types.
- Distinctive: line 20
Start the server in demo mode (no Jira, no real config):
- Distinctive: line 36
If it doesn't come up in 15 s, kill the process, report the failure, and stop.
- Distinctive: line 40
Run all of these and report the status code + a brief summary of the payload for each:
- Distinctive: line 61
If the run id doesn't exist or the stream returns nothing, report it.
“Common” is measured: kept by at least 6 in 10 of the 3 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
Smoke-test Hangar — confirm the server boots, serves demo data, and the SSE stream flows.
Steps
1. Typecheck
npm run typecheckStop and report if typecheck fails — there's no point starting the server with broken types.
2. Boot demo mode
Start the server in demo mode (no Jira, no real config):
HANGAR_DEMO=1 npm run dev:server &
SERVER_PID=$!Poll until it's up (up to 15 s):
for i in $(seq 1 15); do
curl -sf http://localhost:3001/api/config > /dev/null && break
sleep 1
doneIf it doesn't come up in 15 s, kill the process, report the failure, and stop.
3. Exercise the critical endpoints
Run all of these and report the status code + a brief summary of the payload for each:
| Endpoint | What to check |
GET /api/config | returns { boards: [...] } with at least one board |
GET /api/tickets?board=DEMO | returns { tickets: [...] } with 6+ demo tickets |
GET /api/agents | returns an array (may be empty if no agents dir) |
GET /api/skills | returns an array of skills |
GET /api/runs | returns { runs: [...] } with at least one done run |
For each, note the HTTP status code. A 4xx/5xx is a failure; report it clearly.
4. Verify the SSE stream
Pick the first run from GET /api/runs (runs array) that has state done. Connect to its SSE stream:
curl -sf --max-time 3 http://localhost:3001/api/runs/<id>/streamExpect to see at least one data: line. If the stream opens and emits data, it passes.
If the run id doesn't exist or the stream returns nothing, report it.
5. Tear down
Kill the server:
kill $SERVER_PID 2>/dev/null; wait $SERVER_PID 2>/dev/null6. Report
Print a pass/fail summary:
SMOKE RESULTS
─────────────
typecheck ✓ / ✗
server boot ✓ / ✗
GET /api/config ✓ / ✗
GET /api/tickets ✓ / ✗
GET /api/agents ✓ / ✗
GET /api/skills ✓ / ✗
GET /api/runs ✓ / ✗
SSE stream ✓ / ✗
─────────────
Overall: PASS / FAILInclude a one-sentence note for each failure. If everything passes, say so and stop — no unnecessary detail.
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.

