rafaie/smoke-test
skills/smoke-test/SKILL.md
Run a real entrypoint smoke test, emit required artifacts, classify failures, and recommend the next action.
$ install --global
skillsauthnpx skillsauth add rafaie/codex_home smoke-testInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 5, 2026, 6:21 AM170.7s1 file scanned
SKILL.md
- name:
- smoke-test
- description:
- Run a real entrypoint smoke test, emit required artifacts, classify failures, and recommend the next action.
- Resolve the smoke command.
- Read
codex.tomland use[commands].smokewhen present. - If absent, use
uv run python scripts/smoke.pywhenscripts/smoke.pyexists. - If neither exists, fail as
config_errorand report the missing command/script.
- Read
- Scope smoke to the requested work item when provided.
- Prefer
--work-item <work-id>forscripts/smoke.py. - Treat
--featureas a deprecated compatibility alias only.
- Prefer
- Run smoke using the real entrypoint path.
- Smoke must execute a subprocess command path (CLI/module/script), not only import-level calls.
- Use tiny fixture inputs under
tests/fixtures/smoke/when available.
- Enforce required artifact contract under
artifacts/smoke/<run-id>/(or equivalent configured directory):summary.jsoncases/<case_id>.jsonstdout.txtstderr.txttiming.json
- Validate outputs.
- Always validate schema contract.
- Always validate invariants (required fields/ranges/non-empty critical fields).
- Golden comparison is optional per scenario and must support explicit
--recordupdates.
- Summarize every run:
- command run
- work item ID (
work_item) when provided - fixture(s)/scenario(s)
- exit code
- artifact locations
- wall-clock time
- budget telemetry (
requests_used,time_budget_exceeded, max request/time settings) - failure bucket counts
- Classify failures into one primary bucket per case/run summary:
config_error,fixture_error,auth,permission_error,network_error,timeout,rate_limit,quota_exceeded,provider_error,invalid_response,parse_error,schema_error,invariant_error,golden_mismatch,budget_exceeded,artifact_error,subprocess_error,internal_error
- Use this exit-code mapping:
0pass10config/fixture/auth/permission failure12artifact failure20subprocess failure22network failure23timeout24rate limit25quota exceeded26provider error30invalid/parse error40schema validation failure41invariants failure50golden mismatch55budget exceeded60internal/unclassified
- If multiple failures occur, prioritize exit code in this order:
- artifact -> config/fixture/auth/permission -> quota -> rate_limit -> network -> timeout -> provider -> subprocess -> invalid/parse -> schema -> invariant -> golden -> budget -> internal
- Recommend next action:
- deterministic smoke/runtime/packaging issues ->
debug-loop - fixture/golden updates only when behavior change is intentional and documented
Related Skills
rafaie/write-tests
testing
VerifiedTrustedCommunity
Add or improve tests based on a work item folder's acceptance criteria and test plan.
1SKILL.mdUpdated May 5, 2026
rafaie/test-runner
testing
VerifiedTrustedCommunity
Run quick/full checks consistently, include smoke, and summarize failures into actionable buckets.
1SKILL.mdUpdated May 5, 2026
rafaie/test-plan
testing
VerifiedTrustedCommunity
Create a work item test plan from acceptance criteria and add it to the work item docs.
1SKILL.mdUpdated May 5, 2026
rafaie/spec-linter
development
VerifiedTrustedCommunity
Review a work item documentation folder for clarity, testability, and completeness before implementation.
1SKILL.mdUpdated May 5, 2026