skills.rest
LedgerHQ
LedgerHQOFFICIAL
Explore all skills by this author →
WebsiteGitHub

impacting-prs

Detects open GitHub PRs impacted by a migration and posts blocking reviews or heads-up comments.

615|491|Updated Jan 4, 2022
Search Tags:#deprecation#gh CLI#Monorepo#gitHub#Pull Requests#Migration#Code review
One-click install
npx skills add https://github.com/LedgerHQ/ledger-live --skill impacting-prs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: impacting-prs
Source: https://github.com/LedgerHQ/ledger-live/tree/main/.agents/skills/impacting-prs
Command: npx skills add https://github.com/LedgerHQ/ledger-live --skill impacting-prs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

When a package sunset, API deprecation, or module move lands in a monorepo, dozens of in-flight pull requests silently keep using the old path and break on rebase. This Skill finds those impacted open PRs and notifies their authors with the right severity, so migrations do not blindside other contributors.

Core Features & Use Cases

  • Three notification modes: blocking review (old path already removed from develop), heads-up comment (deprecated or removal still in review), or a silent impact study when the replacement does not exist yet.
  • Automated PR scanning: the scan-prs.sh script filters open PRs by base branch, mergeability, and already-informed markers, then matches a detection regex against added diff lines only, producing per-line hits ready for inline review comments.
  • Draft-first workflow with templates: every comment is drafted from references/comment-templates.md, shown to the user for approval, and posted via the GitHub reviews API with optional committable suggestion blocks.
  • Use Case: After merging a PR that drops a legacy import from develop, run the scan to find 6 open PRs still adding that import, then post a REQUEST_CHANGES review on each with an inline suggestion showing the replacement import.

Quick Start

Ask the agent to check which open PRs are impacted by the migration in PR #12345 and draft notifications for their authors.

Frequently Asked Questions about impacting-prs

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

FAQPage Schema
How do I find open PRs affected by a breaking change on GitHub?▼

Run the scan-prs.sh script with a detection regex matched against added diff lines of open PRs. It filters by base branch and mergeability, excludes already-informed PRs, and outputs a hits.tsv file with exact line numbers for review comments.

How to notify PR authors about a deprecation without blocking them?▼

Post a review with event COMMENT instead of REQUEST_CHANGES when the old path still works on develop. The heads-up template explains the deprecation, links the migration PR, and includes inline notes with committable suggestion blocks.

When should a migration impact check block a pull request?▼

Block with REQUEST_CHANGES only when the old path is already removed from develop, so the PR would fail to build after rebase. If removal is still in review or only deprecated, post a non-blocking comment instead.

Does the scan avoid commenting twice on the same PR?▼

Yes, the script checks issue comments, review bodies, and inline comments for an already-informed marker such as 'On behalf of @' and excludes matching PRs. You can narrow the marker with the -m flag when multiple migration campaigns overlap.

Why does the scan only match added lines in PR diffs?▼

Matching added lines ensures a PR that removes the old import is recognized as doing the migration, not breaking it. It also provides RIGHT-side line numbers that map directly to the line parameter of the GitHub reviews API.

What happens if the replacement API does not exist on develop yet?▼

The skill switches to study mode and posts nothing on impacted PRs, since authors cannot act on a target API that does not exist. It delivers a single impact report to the migration author, grouped by required action.

Related Skills

Explore More Software Engineering Skills→
smarmen86smarmen86

review

Analyze git diffs against base branches for SQL vulnerabilities and code defects.

Community
Advanced
santhank8santhank8

prcheckloop

Automate GitHub PR check repair by monitoring head SHA and pushing fixes.

Community
Advanced
mdelapenyamdelapenya
2

pr-nurse

Monitor and fix PR CI failures and merge conflicts on GitHub and GitLab.

Community
Advanced
dyad-shdyad-sh
21.4k

dyad:pr-fix

Resolves GitHub pull request review comments and failing CI checks automatically.

Official
Advanced