mkl-review-source-change

Reviews upstream documentation changes against dependent skills, agent instructions, and runbooks.

11|1|Updated Sep 13, 2026
One-click install
npx skills add https://github.com/00200200/maintainer-skills-lab --skill mkl-review-source-change-00200200
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mkl-review-source-change
Source: https://github.com/00200200/maintainer-skills-lab/tree/main/providers/cursor/.cursor/skills/mkl-review-source-change
Command: npx skills add https://github.com/00200200/maintainer-skills-lab --skill mkl-review-source-change-00200200

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When upstream documentation changes, it is hard to know which of your skills, agent instructions, or runbooks that cite it are now outdated. This Skill turns a source diff into a clear decision about each dependent instruction, avoiding both blind mass edits and missed updates. ## Core Features & Use Cases - Change Establishment: Tracks source identity (URL, revision, content hash, section) and checks version, platform, and mode alignment before drawing conclusions. - Dependency Tracing: Locates the exact claims, commands, or expectations in owner files that depend on the changed passage, keeping generated copies separate from canonical sources. - Decision Reporting: Classifies each affected claim as supported for update, still valid, or unresolved, with proposed minimal corrections and named validation checks. - Use Case: A Skill Watch check flags that an upstream CLI guide changed its checkpoint behavior. Use this Skill to review the diff, find the runbook instruction that contradicts it, and propose the smallest supported correction without inventing unverified test commands. ## Quick Start Review this supplied documentation diff against the skills and runbooks that cite it and tell me which instructions need updates, which remain valid, and which are unresolved.

Frequently Asked Questions about mkl-review-source-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a documentation change against my agent instructions?▼

Supply the before/after source text or a Skill Watch result, then trace each dependent claim in the canonical owner files. The review classifies every affected instruction as needing an update, remaining valid, or unresolved, with file locations and reasoning.

How do I use Skill Watch to check if a source changed?▼

Use the skill_watch_sources tool to find configured source IDs, then call skill_watch_check with the source ID. In a clone with the CLI, run python3 tools/skill_watch.py --json check --source SOURCE_ID; exit code 1 means review is needed.

Does a changed upstream doc mean my instructions are wrong?▼

Not necessarily. Editorial changes, new examples, or reordered pages may require no instruction change, and a newer doc version may not apply to instructions targeting an older supported version. Each claim is evaluated individually against the evidence.

What does a diff_truncated status mean in Skill Watch?▼

A diff_truncated status means the comparison output was cut off, so you must obtain the complete evidence through the CLI or the supplied source. If full evidence is unavailable, that part of the review stays unresolved rather than being guessed.

When should I not update instructions after a source change?▼

Do not update when the changed documentation targets a different version, platform, or operating mode than your instructions, or when the change is purely editorial. Also avoid creating a patch just to make the review look productive when all instructions remain valid.