kicad-tools: Command for Claude Code

Judge Reference

Detailed reference material for the Judge role, split out of judge.md (the largest prompt in the repo) to keep the main workflow scannable — mirroring how champion.md references champion-reference.md / champion-common.md.

Read the relevant section when judge.md points you here.

---

Scoped Test Execution

When running quality checks (step 7), use scoped test execution to run only the tests relevant to changed files. This reduces evaluation time while maintaining confidence that changed code is correct.

Step 1: Detect Changed Files

# Use gh API to list changed files — avoids local git dependency and
# exit-128 errors when the branch is checked out in a worktree or when
# concurrent builder operations hold a git lock. (issue #2828)
CHANGED_FILES=$(gh pr diff $PR_NUMBER --name-only 2>/dev/null)
if [ -z "$CHANGED_FILES" ]; then
    echo "Warning: Could not detect changed files via gh pr diff — running full test suite"
    # Fall through to full suite
fi
echo "$CHANGED_FILES"

Step 2: Check for Config File Changes

If the PR touches configuration files that affect the entire project, skip scoping and run the full test suite:

# Config files that should trigger full suite
CONFIG_PATTERNS="pyproject.toml|setup.cfg|setup.py|package.json|pnpm-lock.yaml|yarn.lock|Cargo.toml|Cargo.lock|tsconfig.json|jest.config|vitest.config|.eslintrc|Makefile|CMakeLists"

if echo "$CHANGED_FILES" | grep -qE "($CONFIG_PATTERNS)"; then
    echo "Config files changed — running full test suite"
    # Run full suite (skip to Fallback section below)
fi

Step 3: Classify Changed Files by Language

Classify the changed files to determine which scoped test strategies to apply:

Extension/Path	Language	Scoped Strategy
.py, .pyi	Python	pytest --testmon or full pytest
.ts, .tsx	TypeScript	jest --changedSince or vitest --changed
.js, .jsx, .mjs, .cjs	JavaScript	jest --changedSince or vitest --changed
.rs	Rust	cargo test -p <crate>
Other	Unknown	Full test suite