Release Smoke Check Skill
Purpose
Provide a consistent, low-friction pre-release check to catch regressions early.
When to Use
- •Before tagging or shipping a release
- •After dependency or config updates
- •When CI failures need local reproduction
Inputs
- •Target branch/commit
- •
package.jsonscripts
Outputs
- •Pass/fail summary stored under
.agent/artifacts/{conversation-id}/release_smoke_check.md - •Command list with exit codes and key errors
Prerequisites
- •Node/npm installed
- •Dependencies installed (
npm install)
Tools & Availability
- •Local shell + npm scripts
- •If a script is missing, record it explicitly
Methodology
- •Run
npm run lint - •Run
npm run typecheck - •Run
npm run test - •Run
npm run build - •Capture exit codes and first actionable error line for failures
Verification
- • All four commands executed or documented as missing
- • Pass/fail summary includes exit codes
- • Failure notes include the first actionable error
Pass/Fail: Pass only if all checks above are satisfied.
Risks & Mitigations
- •Flaky tests → rerun once and record both outcomes
- •Slow builds → run during low-activity periods