Skip to content
Skills Library
Programming · Testing

setup

/setup

Configure the testing plugin's can't-fail checks for this repository. check prints the resolved testing config cascade, which test-lint rules the repo's lint config turns on per language (a missing one is a finding), an optional instruction line to paste, and any test glob the shipped test-weaken hook skips; apply writes your answers to docs/conventions/testing.yaml (or to the docs/conventions/testing.md block or .claude/testing.yaml when that is the team file in use). Use when: 'set up testing', 'configure the test scan', 'exclude these tests from the audit', 'add a test glob', 'which test li

Licence
MIT
Last repository change
26.10.2026

Assessment and security

84/ 100Class: good
Format9 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
4
Scripts
2
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 2 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/setup.sh, scripts/setup.test.sh

What it does and when to use it

Configure the testing plugin's can't-fail checks for this repository. check prints the resolved testing config cascade, which test-lint rules the repo's lint config turns on per language (a missing one is a finding), an optional instruction line to paste, and any test glob the shipped test-weaken hook skips; apply writes your answers to docs/conventions/testing.yaml (or to the docs/conventions/testing.md block or .claude/testing.yaml when that is the team file in use). Use when: 'set up testing', 'configure the test scan', 'exclude these tests from the audit', 'add a test glob', 'which test li

Triggers from the description

s canset up testingconfigure the test scanexclude these tests from the auditadd a test glob

Arguments

/setup [check|apply]
Original author description

Configure the testing plugin's can't-fail checks for this repository. check prints the resolved testing config cascade, which test-lint rules the repo's lint config turns on per language (a missing one is a finding), an optional instruction line to paste, and any test glob the shipped test-weaken hook skips; apply writes your answers to docs/conventions/testing.yaml (or to the docs/conventions/testing.md block or .claude/testing.yaml when that is the team file in use). Use when: 'set up testing', 'configure the test scan', 'exclude these tests from the audit', 'add a test glob', 'which test li

How it works

  1. Purpose
  2. The config
  3. The test judge
  4. check (read-only)
  5. apply
  6. Next
  7. What this skill does NOT do
Original SKILL.md headings · 141 lines, 1,151 words
SKILL.md preview
---
description: "Configure the testing plugin's can't-fail checks for this repository. check prints the resolved testing config cascade, which test-lint rules the repo's lint config turns on per language (a missing one is a finding), an optional instruction line to paste, and any test glob the shipped test-weaken hook skips; apply writes your answers to docs/conventions/testing.yaml (or to the docs/conventions/testing.md block or .claude/testing.yaml when that is the team file in use). Use when: 'set up testing', 'configure the test scan', 'exclude these tests from the audit', 'add a test glob', 'which test lint rules are missing', 'testing setup'. Re-runnable."
argument-hint: "[check|apply]"
user-invocable: true
disable-model-invocation: true
---

## Purpose

`/testing:audit` and the opt-in `test-weaken` hook find tests by the shipped adapters' filename globs
and judge them by the shipped rule levels. This skill shows what a repository changed about that
through the testing config, and writes it. `check` changes nothing; `apply` runs `check`,
asks, writes, and runs `check` again. No argument means `check`.

It never edits `CLAUDE.md` or `AGENTS.md`. The instruction line is printed for you to paste.

## The config

The testing config resolves across the config-cascade layers, in order: `~/.claude/testing.yaml`,
the team layer and `<root>/.claude/testing.local.yaml`, where `<root>` is the scanned file's git
toplevel, else `${CLAUDE_PROJECT_DIR}`. The team layer is `<root>/docs/conventions/testing.yaml`.
Without it, the team layer is the `yaml config` block in `<root>/docs/conventions/testing.md`
(read for one more release), else `<root>/.claude/testing.yaml`; the first present wins and the
resolver prints a warning naming each one it ignores. Lists concatenate across layers; a later
layer's scalar overrides. The format is the adapters' YAML subset in every file; a glob that starts
with `*` must be single-quoted. `docs/conventions/testing.yaml` also holds `/testing:run-e2e`'s
`e2e_driver`, `reuse_running_instance` and `browser_driver`, and `/testing:write`'s
`tdd_refactor_step` and `first_test`, which the scan ignores.

The keys:

```yaml
adapters:
  disable: [py-unittest]         # wins over enable; a non-empty enable list is an allowlist
paths:
  exclude: ['legacy/**']         # relative to the repo root; ** crosses /, * does not
  include: ['build/**/*.test.ts'] # reaches pruned folders; an adapter must still claim the file
adapter_dirs: [tools/test-adapters]  # consumer adapters, same schema as the shipped ones
extend:
  js-vitest:
    files: ['*.it.ts']           # appended to that adapter's list field
rules:
  rule-weak-oracle: off          # off drops, warn reports without gating, error gates --check
  test-weaken-block: error       # test-weaken hook: deny an added skip or a removed test
```

The opt-in `test-weaken` hook runs before a Write or Edit to a test file and names what it removes:
test blocks, assertions, a changed expected value, or an added skip. By default it only tells the
agent. With `test-weaken-block: error`, an added skip or a removed test block is
denied until the edit carries a `test-change: <reason>` comment; removed assertions and changed
expected values are never denied. The agent can write that marker itself: it makes the reason
visible to reviewers, it does not prove the reason.

Removals (`adapters.disable`, `paths.exclude`, `rules ... off`) apply inside the scanner, so the
audit goes quiet with no plugin change; an excluded path or a disabled adapter silences
`test-weaken` too. Additions reach the audit at once; `test-weaken` covers only the shipped globs.

## The test judge

The judge that asks where each changed test's expected value came from runs on demand, as
`/testing:audit --judge`, and in `/source-control:pull-request` prep. It has no plugin option and
no hook.

## `check` (read-only)

Run the script and show its output as it prints:

```bash
bash "${CLAUDE_PLUGIN_ROOT}/skills/setup/scripts/setup.sh" check
```

It exits 0 with no finding, 1 when a test-lint rule is missing, 2 when a layer does not resolve
(the file and line are on stderr). Its four sections:

1. **config**: the resolved records, or the note that no layer exists.
2. **lint**: one row per rule for each language the repository's tracked test files use. The script
   reads the lint config as text: a rule named there, or its plugin referenced beside a recommended
   config, reads as present. Treat a `PRESENT` row from the recommended-config path as likely rather
   than proven, and say so. A `FINDING` is a gap to report, not a neutral absence. The rules:
   - JS/TS: `jest/valid-expect` (eslint-plugin-jest), `vitest/valid-expect` (`@vitest/eslint-plugin`),
     `playwright/missing-playwright-await` and `playwright/no-focused-test` (eslint-plugin-playwright).
     Each is in its plugin's recommended config. Verified 2026-09-29 against the plugins' README and
     rule pages (github.com/jest-community/eslint-plugin-jest, vitest-dev/eslint-plugin-vitest,
     playwright-community/eslint-plugin-playwright); recheck when a plugin release note moves one of
     these rules out of its recommended config or renames it.
   - C#: `xUnit2021` (xunit.analyzers, which the `xunit` 2.3+ and `xunit.v3` packages bring in;
     `xunit.core` alone does not) and `NUnit2009` (NUnit.Analyzers, a separate package the `nunit`
     template adds). Verified 2026-09-29 against xunit.net/xunit.analyzers/rules/xUnit2021, the
     xunit.analyzers README and the NUnit2009 page in nunit/docs; recheck when an xunit or NUnit
     release note changes how the analyzers are packaged.
   - Python: ruff `PLR0124`, `PT011` and `F631`. Ruff's default rule set holds `PLR0124` and `F631`
     but not `PT011`; a `select` replaces the defaults and selectors match by prefix. Verified
     2026-09-29 against docs.astral.sh/ruff/default-rules and /linter (only part of the default list
     was read); recheck when a ruff release note changes the default rule set.
   - Bash, PowerShell and Go: no maintained rule.
3. **instruction**: the optional line, naming the one file Claude Code loads at the repository
   root: `CLAUDE.md`, else `.claude/CLAUDE.md`, else `CLAUDE.local.md`, else `AGENTS.md`, else `CLAUDE.md` in
   `${CLAUDE_CONFIG_DIR:-~/.claude}`. `CLAUDE.local.md` always loads. By default Claude Code reads `AGENTS.md`
   only when no `CLAUDE.md`, `.claude/CLAUDE.md` or `CLAUDE.local.md` exists. Verified 2026-09-30
   against code.claude.com/docs/en/memory; recheck when a Claude Code release note changes the
   Project instructions default or which files count. Offer it; do not paste it anywhere.
4. **hook-entry**: a `none:` line saying test-quality findings come from `/testing:audit`, not a
   per-edit hook, then, when a consumer glob matches no shipped `test-weaken` row, a line naming
   those globs: the audit scans them, `test-weaken` skips them. No settings entry is printed.

Then probe the hook launcher, which the script does not: run `command -v node` via Bash and report
`node` as a FAIL row when it is absent. Every hook row launches through `node hooks/exec-bash.mjs`,
so a missing `node` is a hook launch error, not a skip notice, and a hook cannot report its own
missing launcher.

## `apply`

1. Run `check` and summarize the effective config before proposing a change. Nothing already
   configured is dropped without the user confirming.
2. Ask only what the repository cannot answer: folders or files to leave out, test files the
   shipped globs miss (and which adapter reads them), adapters to turn off, rule levels.
3. Write the team layer with the answers. The script writes the team file in use:
   `docs/conventions/testing.yaml` whole (keeping its `e2e_driver`, `reuse_running_instance`, `browser_driver`,
   `tdd_refactor_step` and `first_test` lines), else the body of the `yaml config` block in `docs/conventions/testing.md` (the rest of
   that file stays), else `.claude/testing.yaml` whole; with none, it creates
   `docs/conventions/testing.yaml`. It keeps the result only when it resolves and writes nothing
   else; pass every value the team layer should hold, the existing ones included:

   ```bash
   bash "${CLAUDE_PLUGIN_ROOT}/skills/setup/scripts/setup.sh" apply \
     --exclude 'legacy/**' --extend js-vitest.files='*.it.ts' --rule weak-oracle=warn
   ```

   Flags: `--include`, `--exclude`, `--enable`, `--disable`, `--adapter-dir`,
   `--extend <id>.<field>=<value>`, `--rule <rule>=off|warn|error`, each repeatable.
4. Run `check` again. Offer `git add` for the file
   `apply` printed and a commit, and run each only when the user accepts. Personal overrides go in
   `.claude/testing.local.yaml`, which should be gitignored. `check` also prints the optional line
   to paste into `CLAUDE.md` or `AGENTS.md` that points at `docs/conventions/testing.md` when that
   file exists.

## Next

/testing:audit
Runs the scan with the config this skill wrote.

## What this skill does NOT do

- Edit `CLAUDE.md`, `AGENTS.md`, `.claude/settings.json`, or any lint config. It prints what to add.
- Install a lint plugin or analyzer.
- Run the audit. That is `/testing:audit`.
Files in this package (4)
  • SKILL.md 9 KB
  • evals/evals.json 2 KB
  • scripts/setup.sh 16 KB
  • scripts/setup.test.sh 16 KB

Versions

RepositoryScoreLicence
This page · melodic-software/claude-code-plugins84MIT
HwangSlater/harness-fit100MIT
nesquikm/dev-process-toolkit100MIT
userKael/rastro100MIT
als-apg/osprey100BSD-3-Clause
dedujeong/gemba100Apache-2.0
eigenwise/eigenwise-toolshed100MIT
awrshift/agent-memory-kit100MIT
lifecycle-innovations-limited/claude-ops100MIT

Database snapshot: 13.11.2026 · package version f6ba83f3bb7e (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100lint-setup
    Sets up the architecture rules of the harness catalogue on a project in any language: the native tool config, a wrapper lint plugin, and a temporary proof folder with one canary for each rule, run by harness lint canaries --proof and then deleted. Use when harness init prints…
  • 100stress-test-config
    Configure stress test config operations. Auto-activating skill for Performance Testing. Triggers on: stress test config, stress test config Part of the Performance Testing skill category. Use when writing or running tests. Trigger with phrases like "stress test config", "stress config", "stress".
  • 92conventions-testing
    Apply when writing or reviewing tests.
  • 100pw-init
    Set up Playwright in a project. Use when user says \"set up playwright\", \"add e2e tests\", \"configure playwright\", \"testing setup\", \"init playwright\", or \"add test infrastructure\".
  • 100pw-init
    Set up Playwright in a project. Use when user says "set up playwright", "add e2e tests", "configure playwright", "testing setup", "init playwright", or "add test infrastructure".
  • 100pw-init
    Set up Playwright in a project. Use when user says "set up playwright", "add e2e tests", "configure playwright", "testing setup", "init playwright", or "add test infrastructure".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.