Dev Smoke
AI DevKit · Smoke-test the user flows a change affects (CLI, API, UI) end to end with a...
Install
npx skills add codeaholicguy/ai-devkit --skill dev-smoke -g -a claude-code -y- Repository
- codeaholicguy/ai-devkit1.7k
- Category
- Design
- Updated
- 4d ago
- License
- Apache-2.0
- Context cost
- Lightabout 911 tokens
- Runs scripts
- Yes, review before use
What it does
AI DevKit · Smoke-test the user flows a change affects (CLI, API, UI) end to end with a disposable sandboxed script against the real app. Use before calling a feature or fix done, when unit tests pass but the flow is untested, or when users ask for a smoke, e2e, or impact check.
Smoke
Exercise the flows a change touches the way a user would, then throw the script away. Report with verify; use dev-testing for permanent tests.
Rules
- Drive the real entry point: built binary, running server, CLI, UI, or job. Imported functions and mocks are not smoke checks.
- Sandbox everything: temp dir, isolated
HOMEand config, empty git hooks, seeded test data, test accounts and tokens. - Never use production, shared environments, real accounts or credentials, or paid APIs. Ask before outward-facing side effects: messages, emails, webhooks, deploys, pushes.
- Start servers on a dedicated port, wait until they respond, and stop the whole process tree on exit. Never reuse or kill the user's own servers.
- Keep secrets out of the script and its output.
- Write the script outside the repo; commit it only if the user asks to promote it.
- Timebox setup. If the app cannot run locally, say what was not checked instead of faking a pass.
