Turn repo-governance PR/check JSON into concrete companion-test advice without claiming semantic coverage. Use for API, DTO, state, UI, interaction, command, build, or packaging changes and for RG001 test-evidence findings.
Scanned 9/28/2026
Install to Claude Code
Skills Directorynpx -y skills add CoaseEdge/repo-governance --skill plan-change-test-impact --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Plan Change Test Impact?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/coaseedge-plan-change-test-impact)More formats (shields.io, HTML) on the badges page.
---
name: plan-change-test-impact
description: Turn repo-governance PR/check JSON into concrete companion-test advice without claiming semantic coverage. Use for API, DTO, state, UI, interaction, command, build, or packaging changes and for RG001 test-evidence findings.
---
# Plan Change Test Impact
1. Run `repo-governance prepare-pr --json`, or an explicit `check --base ... --head ... --json`.
2. Read [references/playbook.md](references/playbook.md); in the source repository, use `playbooks/plan-change-test-impact.md`.
3. Inspect changed behavior and nearby tests, then recommend concrete test files and observable assertions.
4. Preserve `semanticCoverageVerified: false` and the CLI capability boundary.
Do not copy path mappings or turn advisory analysis into a new RG finding.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
