Test
Reusable Claude Code configuration repository with skills, subagents, hooks, MCP setup, and examples for bootstrapping new projects.
npx -y skills add Imran-ml/claude-skills --skill testAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use this skill to run tests, identify failures, and fix them. Triggered by "run tests", "fix failing tests", "make tests pass", or "/test".
SKILL.md
1.4 KB, 304 tokens by cl100k_base, as published. Nobody here has run it
Test Runner & Fixer
Run the test suite and automatically fix any failures.
Current Test Status
!npm test -- --passWithNoTests 2>&1 | tail -30
Instructions
-
Run the tests (filtered to
$ARGUMENTSif provided):npm test $ARGUMENTS # or: pytest $ARGUMENTS # or: go test ./... # or: cargo test -
For each failing test: a. Read the test file to understand what's being tested b. Read the source file being tested c. Identify the root cause (test wrong? source wrong? missing mock?) d. Fix the root cause — prefer fixing source bugs over changing tests e. Only update a test if it's clearly wrong or testing the wrong thing
-
Re-run tests to confirm they pass
-
If tests still fail after 2 attempts at fixing, report:
- The exact error message
- What you tried
- Your hypothesis for the root cause
- Ask the user how to proceed
Rules
- Never delete tests to make them "pass"
- Never change assertions to match wrong behavior
- Do NOT mock the database in integration tests
- Run the full suite at the end to check for regressions
- If adding new tests, follow the existing test file structure
$ARGUMENTS