test-discovery SKILL.md skillA
test-discovery from gptme/gptme-contrib is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add gptme/gptme-contrib/test-discovery@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- gptme/gptme-contrib
- Path
skills/test-discovery/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Aug 19, 2026
- Size
- 4,704 bytes
- Repository stars
- 15
- License
- MIT
Auto-discover and run the relevant test suite after making code edits. Use when you've edited source files and want to verify correctness without being told which tests to run. Do NOT use for purely exploratory sessions with no file edits, or when the user has already specified which test command to run.
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
# Test Discovery Skill Auto-detect and run the right test suite after code edits. Agents using this skill self-correct from test failures without a manual "run tests" prompt. ## When to Use - After editing source files (`*.py`, `*.ts`, `*.js`, `*.rs`) - After fixing a bug — run the suite to catch regressions - When you suspect a change might have broken something - Before committing, to confirm nothing regressed ## When NOT to Use - User explicitly says which test command to run — just run that - Exploratory or documentation-only session with no source edits - The test suite is known to be very slow and the change is clearly non-breaking ## Procedure ### Step 1: Detect the test runner Run the bundled detector: ```shell bash skills/test-discovery/scripts/detect-runner.sh ``` Or detect manually by priority: | Signal file | Runner | Command | |---|---|---| | `pytest.ini` / `[tool.pytest]` in `pyproject.toml` / `setup.cfg [tool:pytest]` | pytest | `uv run pytest -x -q` | | `package.json` with `"vitest"` or `"jest"` in scripts | jest/vitest | `npm test` or `npx vitest run` | | `Cargo.toml` | cargo | `cargo test 2>&1` | | `Makefile` with `test` target | make | `make test` | …
Read the whole file at its exact version.
How to install
mdr add gptme/gptme-contrib/test-discovery@sha256:b714c698308d8c39The line at the top of this page pins the label v1.0.0, 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.
[](https://markdownregistry.com/a/art_nb55prpkymsoziei)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 19, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4704 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
gptme/gptme-contrib · 15 stars · license MIT · pushed 2026-10-22 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_nb55prpkymsoziei GET https://markdownregistry.com/api/v1/resolve?ref=gptme/gptme-contrib/test-discovery GET https://markdownregistry.com/api/v1/blob/b714c698308d8c399884d08a7eb59f3fa344ee9f4e64d37454ad16878e6b472c
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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.