recheck-against-upstreamlisted

Re-anchor the discipline that existing state — config, code, docs, infra — is not evidence of its own correctness, then audit the surface in flight against CURRENT official upstream docs and classify each divergence. Use when: 'recheck against upstream', 'check this against the docs', 'is our config still current', 'did upstream change', 'are we still doing this right', 'verify against the official docs', 'this may have drifted from upstream', 'audit our setup against the vendor docs', or at conversation start on config, infra, or integration work.
melodic-software/claude-code-plugins · ★ 13 · AI & Automation · score 73

Install: claude install-skill melodic-software/claude-code-plugins

# Recheck against upstream A drift corrector for the discipline that existing state does not vouch for itself. The method — re-anchor, audit the work in flight, correct forward, report, and the tone that firing this is not an accusation — lives in [`${CLAUDE_PLUGIN_ROOT}/context/re-anchor-audit-correct.md`](../../context/re-anchor-audit-correct.md). Read it; this file adds only what is specific to upstream-conformance discipline. ## The discipline this re-anchors Existing state — a config file, a code path, a runbook, an infra definition — is evidence of *what is*, never proof that it matches the upstream it depends on. Upstream ships new defaults, renames flags, deprecates APIs, and obsoletes yesterday's workaround; the state that was correct when written silently rots. Resolve the source of truth per the method doc's ladder: if the consuming project states an upstream-conformance rule in its own `CLAUDE.md` / `.claude/rules/`, re-anchor THAT. Otherwise re-anchor this portable baseline: - **Present state is not self-justifying.** "It's already configured this way" and "the code does X" describe the state; neither shows it still matches upstream. Conformance is a claim to verify, not to assume. - **Compare against the CURRENT official upstream, fetched now.** Re-read the vendor's live documentation for the surface in play this session — never training-data recall of it, never a stale in-repo summary of it. - **Resolve the applicable upstream version first.** When