Generate and maintain a local deploy.sh smoke test script.
npx skills add https://github.com/cryptofish7/dotfiles --skill smoke-test-cryptofish7
Please help me install this Agent Skill. Skill: smoke-test Source: https://github.com/cryptofish7/dotfiles/tree/main/config/claude/skills/smoke-test Command: npx skills add https://github.com/cryptofish7/dotfiles --skill smoke-test-cryptofish7
Generate and maintain a local smoke test script (deploy.sh). Discovers project tooling, tests only what's implemented, and grows as features are added. Use when the user asks to "smoke test", "deploy locally", "test local deploy", "update deploy script", "run deploy", or "run smoke test".
Run the smoke-test skill to generate or update the deploy.sh script for the current project.
High-intent search queries and answers about installing and using this skill.
A local smoke test script like deploy.sh verifies your project runs correctly by automating deployment checks. It discovers existing project tooling, tests only implemented features, and outputs a deterministic script suitable for repeated runs to catch runtime issues.
Maintaining a deploy script involves re-auditing the project state on each invocation to detect newly implemented commands. This updates the smoke test stages automatically, ensuring the script evolves alongside your codebase without manual intervention.
Yes, smoke tests support projects with varying languages and tooling by discovering existing configuration and commands. The script audits the current project state to detect implemented features, ensuring compatibility across different codebases and tech stacks.
To update deploy.sh for testing only implemented features, run an automated smoke test generator that audits the project state. It detects implemented commands and outputs a deterministic script that tests only the features currently available in your codebase.
You need a deterministic and idempotent deploy script for local testing when you want to verify project deployment repeatedly without side effects. This ensures consistent smoke test results across multiple runs, catching integration issues safely before pushing changes.
The main limitation of an automated local smoke test is that it only tests implemented features by discovering existing tooling. It does not replace comprehensive integration tests, but rather verifies that the current project state runs correctly locally.
Kushal9889Analyze project configurations to generate and test Claude Code hooks.
dotnetAutomate end-to-end deployment testing for Aspire applications on Azure.
zardusai-cyberAutomate Python test suite design with pytest, fixtures, and coverage reporting.
aivos-xieAnalyze APK files for vulnerabilities using static and dynamic security analysis.
