Changes explain
Skill yarlson/yarstack/plugins/yarstack/skills/changes-explain
Explain a pull request, commit range, branch, or local diff from a system-design perspective. Use for practical understanding of changed behavior, boundaries, flow, ownership, operations, risks, and verification rather than defect review.From its SKILL.md
npx -y skills add yarlson/yarstack --skill changes-explainAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.3 KB, 205 tokens by cl100k_base, as published. Nobody here has run it
Explain Changes
Translate a confirmed code comparison into system effects without inventing intent or exposing sensitive content.
Workflow
- Confirm the comparison scope; stop or qualify the explanation when it cannot be isolated.
- Read the diff, full changed files, relevant surrounding code, tests, configuration, and linked in-scope brief.
- Group edits by changed behavior or responsibility rather than file mechanics.
- Explain previous and new behavior, affected owner or boundary, data and control flow, external interactions, and user, developer, runtime, or operational effects.
- Describe materially changed failure, compatibility, rollout, CI, verification, and residual-risk behavior.
- Distinguish observed evidence, documented intent, and inference.
Keep the task read-only. Redact secrets and sensitive diff content. Use code-review for defect findings and rollout-readiness-review for operational-readiness judgment.
Finish when every material change group is explained and evidence limitations are stated. Omit syntax trivia and empty sections.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.