1---2name: oc-tooling-audit3description: "Trigger: tooling audit, test tooling gaps, tooling compatibility matrix, mutation coverage tooling. Detect build/test/coverage/mutation tooling and pick compatible baselines for refactor safety plans."4license: Apache-2.05metadata:6 author: gentle-ai7 adapted_by: andresnator8 source: https://skillmd.com/skills/andresnator/oc-tooling-audit9 upstream: gentle-ai/plan-refactor10 version: "3.0.0"11 status: testing12---1314# Tooling Audit1516## Intent1718- **Goal:** Identify existing test infrastructure, missing safety tooling, installation tasks, verification commands, and compatibility checks.19- **Limits:** Read-only detection. Never fetch versions; web fetch remains denied for harness workers. Prefer existing project conventions when present. `references/matrix.md` owns offline version/tool baselines; load it only when a gap needs an install task or a compatibility check.20- **Fails if:** A gap lacks an install task with an exact verify command, more than 5 gaps are emitted, a version without evidence or uncertain compatibility is not marked `hypothesis`, or an emitted version lacks `verify_latest_at_execution: true` and an executor task to verify it is current and CVE-free before installation.2122## Context2324- **Reads:** Prefer direct reads/globs for these files only when they are in or above the resolved target scope:25 - `pom.xml`, `build.gradle`, `build.gradle.kts`, `gradle/wrapper/gradle-wrapper.properties`26 - `package.json`, `package-lock.json`, `pnpm-lock.yaml`, `yarn.lock`, `tsconfig.json`, `vite.config.*`, `jest.config.*`, `vitest.config.*`27 - `pyproject.toml`, `requirements*.txt`, `setup.cfg`, `tox.ini`, `pytest.ini`, `poetry.lock`28 - `.java-version`, `.sdkmanrc`, `.tool-versions`, Maven compiler properties, Gradle Java toolchain declarations29- **Never reads:** Build files unrelated to the resolved target scope; network sources.30- **Persona:** Read-only tooling detector.31- **Scope:** Hardening and refactor planning at high or critical risk.3233## Expectations3435- **Scenarios:**36 - WHEN detecting THEN record language version and build tool with evidence, and present `test_framework`, `assertion_lib`, `coverage`, and `mutation` tooling.37 - WHEN a gap exists THEN load `references/matrix.md`, pick the matching row and snippet template, and create an install task with an exact verify command.38 - WHEN version evidence is missing, or version or plugin compatibility is uncertain, THEN mark it `hypothesis` and require verification before install.39- **Done means:** The compact `tooling_audit` YAML below, with max 5 gaps prioritized by safety impact and compatibility checks such as Java/PIT requirements or Node/Python floors.40- **Quality needs:** Every claim has evidence. Do not migrate tests or runners as safety-plan work unless required for execution.4142## Method4344```yaml45tooling_audit:46 language: "" # include version and evidence file:line47 build_tool: ""48 present:49 test_framework: {}50 assertion_lib: {}51 coverage: {}52 mutation: {}53 gaps: [] # max 554 install_tasks:55 - tool: ""56 matrix_ref: ""57 build_file: "file:line insertion point"58 snippet: ""59 verify_command: ""60 verify_latest_at_execution: true61 compatibility_checks:62 - "PIT >=1.15 requires Java 11+; detected Java 17: OK"63```