Skill
pr-impact-scan
Before opening a PR, enumerate every caller / reference / test / config that touches the symbols or files you changed, so you can decide (a) whether your change is source-compatible, (b) whether tests exist for every affected path, and (c) whether the PR description should call out any behaviour del
Claim this listing
Connect your GitHub to prove you own or maintain this listing. We verify repo access automatically — most publishers are confirmed in seconds.
1Connect GitHub
2Submit your claim
3Auto-verified, or reviewed within 48h