Modernise a Stale Pull Request
By Cameron Chen · Published · Updated
Decides whether an old pull request can be brought onto today's base branch, needs a rework, or should be closed, and does the work when it can.
Prompt template
## Modernise a Stale Pull Request Assess an old pull request and bring it up to date if it is worth saving. - Pull request: [text: Link or number] - Age and original goal: [textarea: When opened and what it was for] - Current base branch: [text: e.g. main] - Known conflicts or failures: [textarea: Paste conflict or test output] - Original author available: [toggle: Yes, No] - Preferred outcome: [dropdown: Update it, Rework it, Close it, Decide for me] Start with relevance. Check whether the base branch already solved the problem, changed the area, or removed the code. If the goal is already met, recommend closing and say which commit did it. Otherwise compare the PR against the current base and list conflicts, API changes, and dependency drift. Rebase or merge the base in, resolve conflicts keeping the original intent, update code that calls changed APIs, and rerun the tests. If more than about half the diff needs rewriting, recommend a rework as a new branch rather than patching. Give a decision of Update, Rework, or Close with the evidence, describe what changed in the update, and write a short comment for the original author explaining the outcome.