agentleFS
thalissonbarbosasthalissonbarbosas/hangar/.claude/skills/smoke/SKILL.md

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

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
  1. Distinctive:

    Stop and report if typecheck fails — there's no point starting the server with broken types.

    line 16
  2. Distinctive:

    Start the server in demo mode (no Jira, no real config):

    line 20
  3. Distinctive:

    If it doesn't come up in 15 s, kill the process, report the failure, and stop.

    line 36
  4. Distinctive:

    Run all of these and report the status code + a brief summary of the payload for each:

    line 40
  5. Distinctive:

    If the run id doesn't exist or the stream returns nothing, report it.

    line 61

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Smoke-test Hangar — confirm the server boots, serves demo data, and the SSE stream flows.

Steps

1. Typecheck

npm run typecheck

Stop 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
done

If 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:

EndpointWhat to check
GET /api/configreturns { boards: [...] } with at least one board
GET /api/tickets?board=DEMOreturns { tickets: [...] } with 6+ demo tickets
GET /api/agentsreturns an array (may be empty if no agents dir)
GET /api/skillsreturns an array of skills
GET /api/runsreturns { 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>/stream

Expect 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/null

6. 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 / FAIL

Include a one-sentence note for each failure. If everything passes, say so and stop — no unnecessary detail.

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.