revert
Revert Merged PR
When to Use This Skill
- A developer wants to revert a PR that has already been merged
- The revert should be delivered as a new branch and PR
- The revert may need to be applied to more than one base branch, such as
mainand a release branch
Inputs To Confirm
- The PR URL or PR number
- The target base branch to revert onto, such as
mainorrelease/v4.81.0 - The desired revert branch name, if the user already has a naming convention
If any of those are missing and cannot be inferred safely, ask.
Workflow
Step 1: Check repository state
More from lmcjt37/skills
cosmograph
Walks a codebase and produces a render-ready Cosmograph architecture dataset by extracting meaningful points, typed links, config, and optional layout under architecture/output/.
7dev-plan
Maintains a per-project engineering plan (plan.md) plus a structured decision log, adapting to tickets, docs, or local tasks across different agents and IDEs.
5map-architecture
Maps a project or domain by tracing screens, interfaces, functions, callsites, branches, and data flow into Mermaid-based architecture notes. Use when the user asks for architecture analysis, domain mapping, dependency tracing, touchpoint discovery, or wants diagrams written under architecture/.
5journal
Maintains a per-project engineering journal (journal.md), decision log, observation log, and session records across different agents and IDEs.
3dev-journal
Maintains a per-project engineering journal (journal.md) plus a structured decision log and full conversation transcripts.
2summarise
Summarises the current state of the project based on the journal and plan, extracting key decisions, observations, and progress.
2