Execute the project test suite with coverage reporting. Use when validating a change.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Run Tests
Execute the full test suite for the current project, collect coverage
metrics, and report results in a structured format.
## When to Use This Skill
Use after making code changes to verify nothing is broken, or when the
user explicitly asks to run tests.
## Implementation Steps
### Step 1: Detect Test Framework
Identify the test framework by checking these files in order:
1. `pyproject.toml` or `pytest.ini` → pytest
2. `package.json` with a `test` script → jest / vitest
3. `go.mod` → `go test`
4. `Cargo.toml` → `cargo test`
### Step 2: Run Tests
Execute the test suite with coverage enabled:
- **pytest**: `pytest tests/ -v --cov=src --cov-report=term-missing`
- **jest**: `npx jest --coverage --verbose`
- **go test**: `go test -v -coverprofile=coverage.out ./...`
- **cargo**: `cargo test -- --nocapture`
### Step 3: Parse Results
Extract from the test output:
- Total tests run
- Passed / failed / skipped counts
- Coverage percentage by module
- Names and locations of failing tests
### Step 4: Report Results
Format a markdown summary:
| Metric | Value |
|--------|-------|
| Total | N |
| Passed | N |
| Failed | N |
| Coverage | N% |
…
The line at the top of this page pins the label v1.3, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_rmiklknrzrdt3ave
GET https://markdownregistry.com/api/v1/resolve?ref=stbenjam/skillsaw/run-tests
GET https://markdownregistry.com/api/v1/blob/ed604f381859a35f9475589220f6e881e3bc9681aeae678a80161d5cabbe0968
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
stbenjam/skillsaw · .agents/skills/skillsaw-issue-solver/SKILL.md · Pick up open GitHub issues from collaborators and create PRs to solve them. Use when triaging and resolving reported…
stbenjam/skillsaw · .agents/skills/skillsaw-issue/SKILL.md · Use when skillsaw reports a likely false positive, misses an edge case, behaves incorrectly, or needs an RFE. Gather a…
stbenjam/skillsaw · .agents/skills/skillsaw-lint/SKILL.md · Use when modifying agentic contextual building blocks like skills (SKILL.md), slash commands, agents, hooks, plugins…
stbenjam/skillsaw · .agents/skills/skillsaw-onboard/SKILL.md · Onboard a repository to skillsaw — run the linter, triage the findings by rule, apply autofixes, manually fix what…
stbenjam/skillsaw · .agents/skills/skillsaw-pr-followup/SKILL.md · Follow up on open PRs in skillsaw — fix failing CI, address reviewer feedback, push updates, and validate backward…
stbenjam/skillsaw · .agents/skills/skillsaw-release-ready/SKILL.md · Audit skillsaw for release readiness — test new rules against real repositories, audit core architectural dimensions…
stbenjam/skillsaw · .agents/skills/skillsaw-release/SKILL.md · Bump the version, generate release notes, and publish a new skillsaw release to PyPI. Use when cutting a new release.
different-ai/openwork · .opencode/skills/run-tests/SKILL.md · Run the tests, run one spec, run e2e locally or on Daytona, investigate a skipped spec. Use for executing…
dotnet/skills · plugins/dotnet-test/skills/run-tests/SKILL.md · ALWAYS USE before running .NET tests or answering with a test command or flags. Trigger on "run the tests", "exact…
hiroro-work/claude-plugins · .claude/skills/run-tests/SKILL.md · Verify plugins marketplace structure, version consistency, and JSON/frontmatter validity via subagent
nowsprinting/unity-coding-skills · skills/run-tests/SKILL.md · Provides guidelines for running Unity tests using the run_unity_tests tool. Make sure to use this skill whenever…
engreitzlab/perturbnmf · .claude/skills/run-tests/SKILL.md · Run the cNMF benchmarking pipeline test suite end-to-end: clean previous outputs, run sk-cNMF (CPU) and torch-cNMF (GPU…
tibursocampos/agent-dev-toolkit · core/skills/run-tests/SKILL.md · Run the workspace test command for each detected stack and return pass or fail. Use when invoking /run-tests or when…
cratis/ai · .cratis/ai/skills/run-tests/SKILL.md · Use before running .NET tests or choosing test commands, flags and filters, including command failures and dump…
