← ClaudeAtlas

plumb-line-remediatelisted

Use when applying findings from a plumb-line audit report — the builder has a report (or pasted findings) and wants the fixes made. Opt-in and separate from the audit, which is read-only and never fixes.
slopstopper/plumb-line · ★ 4 · Code & Development · score 70
Install: claude install-skill slopstopper/plumb-line
# Remediate plumb-line audit findings REQUIRED READING FIRST: `reference/portable-principles.md` (plugin root). If this file cannot be read, stop immediately and report: "Cannot remediate: `reference/portable-principles.md` is missing or unreadable. Do not proceed from memory — the principles file is the source of truth for what a fix must honor." The audit finds; this skill fixes. The two never blur: remediation runs only on an explicit invitation, consumes a report the audit produced (any `report-format: v1`+; v4 is current), and applies nothing the builder has not seen. If there is no report, offer to run `plumb-line-audit` first, or accept findings pasted in the findings-table shape (Path / Line / Function / Status / Issue / Suggested Fix / Principle; a v3 or earlier table has no Status). **Validate the report before consuming it.** This skill acts on a contracted input, so check the contract. The checker ships inside this plugin (`<plugin root>/scripts/check_report_format.py`; `scripts/check_report_format.py` inside the plumb-line repo): ``` python3 <plugin root>/scripts/check_report_format.py <the report> ``` A violation is **not** a reason to refuse the run — it is a reason to say what is wrong before acting on it. Report the violations, then ask whether to proceed; the risk a malformed report carries is that a column means something other than you assume, and the builder is the one who can tell. If the checker is unavailable, say the input was not mechanically va