Individual skill
verify-and-debug
Prove a create-bun-api project works and fix failures, using bun run verify (typecheck, lint, tests, then boot and GET /health) and its JSON report. Use when finishing any task (before saying it is done), when tests or the typecheck fail, when the server won't start, or when asked to check, debug, or validate the project.
skills/verify-and-debug/SKILL.md
Source commit fab932074b6834948af8313220804b174e5b4c64
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 11
- Repository last updated
- Oct 21, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- bunjs Repository topic
- cli Repository topic
- typescript Repository topic
- agent-skills Repository topic
- agents-md Repository topic
- ai-agents Repository topic
- api Repository topic
- bun Repository topic
- claude-code Repository topic
- codex Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,156 bytes
Read excerpt
# Verify and debug
1. Run `bun run verify --json`. It prints `{ "ok": …, "steps": [{ "id", "ok", "ms", "command", "output"? }] }`.
`output` holds the last 40 lines of a failing step. Every step runs even after a failure.
2. Fix failures in this order, because earlier ones often cause later ones:
| Step | Reproduce alone | Usual causes |
| --- | --- | --- |
| `typecheck` | `bun run typecheck` | Wrong import path. A status code missing from the route's `response` map (for 204, use `status(204, undefined)` and `204: t.Void()`). Possibly-`undefined` values from indexed access (`noUncheckedIndexedAccess`). |
| `lint` | `bun run lint` | Run `bun run format` first; it fixes formatting and import order. Whatever remains is real: unused code or `any`. |
| `test` | `bun test <file>` or `bun test -t "<name>"` | Read the expected-versus-received diff. A wrong HTTP status usually means an object was returned instead of an error helper thrown. |
[Credential-related source omitted]
3. Rerun `bun run verify --json` until `ok` is `true`. Then report which steps ran.