Verify Build Works
Smoke-test that the project still builds, the dev server starts, and the main user flow loads after a change. Run after every non-trivial edit, after a rollback, before a commit, and before pushing to remote.
Install
$ agentstack add skill-lglucas-ai-dev-operating-system-verify-build-works ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-lglucas-ai-dev-operating-system-verify-build-works) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Verify Build Works
When to run this skill
- After applying a fix from
bug-triage-agent. - After a
rollback-safeoperation. - Before any commit larger than a single docs change.
- Before pushing to remote.
- Before opening a PR.
- Before tagging a release.
Verification ladder (run all that apply, in order)
Step 1 — Static checks (cheap, fast)
npm run typecheck
npm run lintStop and report at first failure. Don't continue if static layer is broken.
Step 2 — Build
npm run buildIf build fails, hand off to bug-triage-agent.
Step 3 — Dev server starts
npm run devConfirm: process alive after 15s, HTTP 200 on http://localhost:/, no fatal stderr.
Step 4 — Smoke test the golden path
For UI: load homepage + most critical authenticated page. For API: hit GET /health (or main endpoint) → 2xx.
npm run test:smoke # if existsStep 5 — Visual sanity (UI only)
- Open the affected page in a real browser.
- Confirm change is visible and not regressed.
- Confirm at least one adjacent feature didn't break.
Output format
🧪 verify-build-works
Step 1 — Static checks: ✅ typecheck OK, lint OK
Step 2 — Build: ✅ build succeeded in 14s
Step 3 — Dev server: ✅ ready on :3000, GET / → 200
Step 4 — Smoke tests: ⚠️ no test:smoke script — skipped
Step 5 — Visual sanity: ✅ home renders, login renders
Verdict: SAFE TO COMMIT.If any step fails:
🧪 verify-build-works — ❌ FAIL at Step 2 (build)
Erro principal: src/features/auth/sign-in.ts(23,7): TS2322 ...
Próximo passo: invoco o bug-triage-agent.Tone for the vibe coder
> Antes de avisar que terminou, eu sempre testo. Se algo está quebrado, eu falo agora — não na frente do primeiro usuário.
Do NOT
- Don't claim success without running the steps.
- Don't suppress errors with
|| true. - Don't skip step 3 because "build passed".
- Don't run destructive commands (DB migrations, file deletions) as part of verification.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: lglucas
- Source: lglucas/ai-dev-operating-system
- License: MIT
- Homepage: https://github.com/lglucas/ai-dev-operating-system
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.