test smoke

Manually checking test status across different environments wastes time and leads to broken deployments. This skill automates the detection and execution of smoke tests for Python and Node.js repositories. It identifies your environment, runs the appropriate test suite, and provides a concise status report.

What it does

• Automatic detection identifies pytest, npm, yarn, or pnpm runners based on project files.
• Python execution runs pytest with short traceback formatting within virtual environments.
• Node execution triggers the defined test script using the project's specific package manager.
• Failure capturing extracts the summary line and the first specific error message upon failure.
• Status reporting returns a clear Pass, Fail, or Skip result without manual interpretation.

How it works

1. The skill scans the root directory for pyproject.toml, package.json, or lock files.
2. It executes the correct test command using the detected environment settings.
3. It parses the output to find the summary line and any critical error details.
4. It presents the final status and offers to log notable results if memory skills are present.

Frameworks & tools

Works with Python (pytest) and Node.js (npm, yarn, pnpm). Specifically looks for tests/ directories, pytest.ini, package.json, and standard lock files.

Why this beats prompting it yourself

Writing custom logic to handle different lock files and test runners is tedious. This skill standardizes the "is it broken?" check into a single command that handles environment switching and output parsing for you.

Use cases

• Run quick sanity checks after refactoring code.
• Verify repository health immediately after a fresh clone.
• Confirm bug fixes before submitting a pull request.
• Detect if a dependency update broke the existing test suite.

Known limitations

Does not support Go, Ruby, or other non-JS/Python runners. Requires a pre-configured test script in Node or pytest in Python.