test-runner

Run ruff, lint, and parallel mocked, e2e-live, and smoke tests.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/cncorp/superpowers --skill test-runner-cncorp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-runner
Source: https://github.com/cncorp/superpowers/tree/main/dot-claude/skills/test-runner
Command: npx skills add https://github.com/cncorp/superpowers --skill test-runner-cncorp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Inconsistent testing practices lead to undetected bugs, broken deployments, and wasted time. This skill enforces a mandatory, comprehensive testing workflow after every code change.

Core Features & Use Cases

  • Mandatory Pre-commit Checks: Ensures ruff (formatting) and lint (type checking) are run first, catching style and type errors early.
  • Tiered Testing: Provides quick mocked tests for rapid iteration and a full parallel test suite for exhaustive validation before deployment.
  • Strict Verification: Prohibits claiming "all tests pass" without running the full suite and verifying logs, preventing false positives.
  • Failure Isolation: Mandates a git stash workflow to definitively prove if a test failure is related to your changes or pre-existing.
  • Use Case: After modifying any code, use this skill to run just ruff, just lint, and just test-all-mocked for quick validation. Before marking your task complete, run the full parallel test suite to ensure comprehensive coverage and prevent regressions.

Quick Start

Use the test-runner skill to run ruff, lint, and all mocked tests after your code changes.

Frequently Asked Questions about test-runner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run tests and linting after code changes?

Run tests and linting by executing `just ruff` for formatting, `just lint` for type checking, and `just test-all-mocked` for quick validation. Before deployment, run the full parallel test suite with `just test-all` to verify all mocked, e2e-live, and smoke tests pass.

What's the best way to prevent bugs before deployment?

Enforce mandatory pre-commit checks and comprehensive testing workflows. This skill runs ruff and lint first to catch style and type errors, then executes tiered mocked and parallel test suites to isolate failures and prevent false positives before marking work complete.

How do I verify test results across multiple test suites?

Run the parallel test-runner pipeline which captures per-suite logs for mocked, e2e-live, and smoke tests simultaneously. The skill prohibits success claims until all suites pass and logs are verified, preventing premature deployments from undetected regressions.

Can I use this for CI/CD pipelines?

Yes. This skill applies to development workflows requiring parallelized unit, integration, and e2e test execution with comprehensive log collection. It integrates with CI/CD systems via Just command wrappers and the parallel test-runner pipeline for consistent verification across environments.

What should I do if a test fails after my changes?

Use the mandated `git stash` workflow to definitively prove whether the failure relates to your changes or pre-existing issues. Isolate failures by re-running tests with stashed changes to confirm causation before proceeding.

Do I need to run all test types for quick validation?

No. For rapid iteration during development, run `just test-all-mocked` for quick feedback. Before deployment or marking tasks complete, run the full parallel suite to ensure exhaustive validation and prevent regressions.