- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add athola/claude-night-market --skill night-market-validation-and-qa -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add athola/claude-night-market --skill night-market-validation-and-qa -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add athola/claude-night-market --skill night-market-validation-and-qa -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add athola/claude-night-market --skill night-market-validation-and-qa -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/athola/claude-night-market/tree/HEAD/.claude/skills/night-market-validation-and-qaFrom the publisher
This skill defines the evidence bar for claiming work complete, the coverage and quality thresholds that gate merges, the golden regression tests that guard settled battles, and the procedure for adding tests. The one-line thesis: a green check proves spec-satisfaction, not correctness, so every completion claim needs cited evidence and every test needs proof it can fail.
Never claim "should work". Run the thing, capture the output, cite it.
The house discipline comes from Skill(imbue:proof-of-work):
[E1], [E2], each with the exact
command and its captured output.Criterion: [E2] -> PASS or -> FAIL.COMPLETE (all
criteria passed), PARTIAL (list blockers), BLOCKED (explain
why). A blocked task reported as blocked with evidence is a
successful report. A guessed "done" is not.A passing verifier can mislead two ways (from the prover-verifier
research, codified in commit 29081fda, module
plugins/imbue/skills/proof-of-work/modules/verifier-integrity.md):
Rules that follow:
CONSTITUTION.md rule 3: no implementation without a failing test first. Scope:
plugins/*/src/, plugins/*/scripts/, plugins/*/hooks/).SKILL.md tests, plus a
plugin test, usually tests/unit/skills/test_<name>.py, where the
skill's contract matters.A structural validation test asserts observable content in the skill
file: required sections exist, the referenced modules exist on disk,
tables and examples the skill promises are present. Model on
plugins/imbue/tests/unit/skills/test_proof_of_work.py, which checks
SKILL.md sections, module files, and enforcement tables. The test must
fail if someone deletes the section it guards (see the
tautological-test trap below).
Notes:
run-plugin-tests.sh awk parser reads coverage_threshold from
[tool.nightmarket], never from addopts. Use
scripts/fix_coverage_threshold.py to migrate a plugin still using
the old location.coverage_threshold. If
the key is absent, no --cov-fail-under flag is passed at all, so a
plugin without the key has no coverage gate in the runner.addopts force --cov=scripts plus term and HTML
coverage reports on every run, including single-file runs.PR review here repeatedly catches tests that assert nothing. Evidence
in history: a94240e2 (12 tests of constants tightened to behavioral
coverage), f1cbbcf1 (strengthened tautological assertions),
30e58586 (validation-floor regression test), 42f7ce84 (round-trip
test replacing a structure-only check). The pattern: a test that
restates the code, mocks the unit under test, or asserts a constant
equals itself.
The counter-discipline is the revert test, executed by
sanctum:validate-pr:
When writing a new test, apply the same standard preemptively: write the test so it would catch the bug's return, then confirm it fails before the fix lands (that is the Iron Law's RED step).
These tests lock in lessons from settled incidents. Do not weaken or delete them without understanding the incident they guard.
When you fix an incident of a similar class, add its guard here in the same spirit: an invariant test that fails loudly if the lesson is unlearned.
plugins/<plugin>/tests/ with unit/,
integration/ subdirectories and its own conftest.py and pytest
config in the plugin's pyproject.toml.pyproject.toml sets norecursedirs = ["plugins/*", ...].
Plugin tests MUST run per-plugin. Running them from the repo root
causes ImportPathMismatchError from duplicate module names (the root
conftest.py documents this).# Single test file (fastest loop)
cd plugins/imbue
uv run pytest tests/unit/test_deferred_capture.py -x -q
# Full suite for one plugin
cd plugins/<plugin>
uv run python -m pytest tests/ --tb=short -q
# or, where the plugin has a Makefile target:
make -C plugins/<plugin> test
# Everything (what `make test` at root does)
./scripts/run-plugin-tests.sh --all
# Only plugins with staged changes
./scripts/run-plugin-tests.sh --changed
# Mutation testing for one plugin, locally
cd plugins/<plugin>
uv run mutmut run --paths-to-mutate=scripts/,src/ --tests-dir=tests/
Root pytest runs with --strict-markers, so only registered markers
are legal. Registered in root pyproject.toml: unit, integration,
e2e, slow, network, plugin, skill, hook, command, bdd,
benchmark (skip benchmarks in CI with -m "not benchmark").
unit/ or
integration/ accordingly.uv run python -m pytest tests/ --cov-fail-under=<threshold>.SKILL.md tests, and a skill
whose contract matters has its own structural test.The most recurrent bug class in this repo is the swallowed error. In
scanner-shaped code (anything that walks files and reports findings),
the signature is except-continue: a try/except that skips a file on
malformed input and reports success on the remainder. The scanner
looks healthy while ignoring exactly the inputs most likely to be
broken.
The house convention since commit 666171c3 (issue #575): a scanner
that cannot process an input emits an ADVISORY finding for it instead
of skipping silently. Examples from that commit:
check_hook_modernization.py emits findings on malformed
hooks.json, SyntaxError, or OSError instead of dropping the file.harden/scanner.py appends an ADVISORY finding for
unreadable files under --strict.dora_metrics warns and sets a partial flag on malformed
tag lines instead of silently classifying the repo Elite.When reviewing or writing scanner code, grep for the pattern:
rg -n "except .*:\s*$" -A2 plugins/<p>/scripts/ | rg -B1 "continue|pass"
Any hit that discards an error without emitting a finding or an inline "why it is safe to discard" comment violates Constitution rule 10 (errors are not optional).
night-market-operations (command anatomy lives there).night-market-change-control.night-market-debugging-playbook.night-market-failure-archaeology.Skill(leyline:testing-quality-standards) has the templates (module
pytest-config) and the anti-pattern catalog.[E1]...) with commands and captured output, and carries
a COMPLETE, PARTIAL, or BLOCKED status.[tool.nightmarket] coverage_threshold.SKILL.md tests, and
one whose contract matters has a passing structural test.Compiled 2026-07-02 against repo v1.9.15, branch discussions-fix-1.9.14. Volatile facts and how to re-verify them:
rg -n "fail_under" pyproject.toml
(85 as of 2026-07-02).rg -n "coverage_threshold" plugins/*/pyproject.toml
(90 everywhere except gauntlet at 85, as of 2026-07-02).scripts/run-plugin-tests.sh (search tool.nightmarket).rg -n "cron|matrix" .github/workflows/mutation-testing.yml.cat .claude/quality_gates.json.ls plugins/leyline/tests/test_python39_compat.py plugins/gauntlet/tests/unit/test_challenges.py plugins/herald/tests/unit/test_double_shot_latte.py plugins/abstract/tests/hooks/test_hook_io.py.git log --oneline -1 <hash> for 29081fda,
a94240e2, f1cbbcf1, 30e58586, 42f7ce84, 666171c3,
268cff89.rg -n -A12 "^markers" pyproject.toml.Enforce evidence bar, coverage gates, and regression guards. Use when adding tests or claiming done. Do not use to run suites; use night-market-operations.
---name: night-market-validation-and-qadescription: Enforce evidence bar, coverage gates, and regression guards. Use when adding tests or claiming done. Do not…---# .claude/skills/night-market-validation-and-qa/SKILL.mdFAQ
Download .claude/skills/night-market-validation-and-qa/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/athola/claude-night-market.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.