test-suite

Runs the full npm test suite and fixes failing tests one at a time.

2|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/SkinnnyJay/simpill-utils --skill test-suite-skinnnyjay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-suite
Source: https://github.com/SkinnnyJay/simpill-utils/tree/main/.claude/skills/test-suite
Command: npx skills add https://github.com/SkinnnyJay/simpill-utils --skill test-suite-skinnnyjay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually running tests, triaging failures, and verifying fixes before a commit is repetitive and error-prone. This Skill automates the full test-fix-verify loop so every commit lands on a green build. ## Core Features & Use Cases - Full Suite Execution: Runs npm test across Jest-based utils packages and Vitest where configured. - Systematic Failure Fixing: Discovers all failures, creates a task list, and fixes one test at a time with minimal root-cause patches. - Build Verification: Re-runs the full suite and npm run build to confirm fixes introduce no regressions. - Use Case: Before committing changes to a TypeScript utility package, invoke this Skill to run all tests, repair any broken assertions, and confirm the build still compiles. ## Quick Start Run the full test suite, fix any failing tests one at a time, and confirm the build passes before I commit.

Frequently Asked Questions about test-suite

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

FAQPage Schema
How do I run and fix all failing tests before committing?▼

Run npm test to execute the full suite, list every failure, then fix one test at a time by reading the failing test and source, applying a minimal root-cause fix, and re-running that specific test. Finish with a full suite run and npm run build.

What test runners does this workflow support?▼

The workflow runs Jest in the utils packages and Vitest where it is configured, both invoked through the standard npm test command. No additional test runner setup is required beyond the existing package scripts.

Should I fix all failing tests at once or one at a time?▼

Fix one test at a time. Identify the root cause, apply a minimal fix, and re-run that specific test to confirm before moving on. This prevents fixes from masking each other or introducing new failures.

Why does the build need to run after fixing tests?▼

Test fixes can change source code in ways that break TypeScript compilation. Running npm run build after all fixes confirms the changes still compile and no regressions were introduced.

What counts as a passing result for the test suite?▼

All tests must pass with a 100% success rate and npm run build must complete successfully after the fixes. Failing to run tests, leaving tests unfixed, or introducing new failures counts as failure.