Find Linear issues reporting the same underlying bug, compare their evidence, and propose which issue to keep. After approval, transfer unique findings and relevant people’s details, then close duplicates with links to the surviving issue.
Find and merge duplicate Linear issues — group reports of the same underlying bug, pick the survivor, and move the evidence across. Use when the backlog has grown noisy, someone asks whether an issue is already reported, or you are cleaning up before planning.
Run score Not tested
See how to installSearches Linear bug reports using several terms, such as error messages, feature names, and user descriptions, and includes closed issues in the review. It compares likely causes and evidence to identify potential duplicates. For each group, it proposes which issue to keep, giving priority to a useful reproduction and discussion over age alone. When the cause is uncertain, it links issues as related instead of merging them.
Use it when reports are scattered across duplicate issues, when you need to check whether a bug has already been reported, or when organizing unresolved issues before planning. It helps bring relevant evidence together so investigations and decisions are easier to follow.
A Linear tool connection is required. Before making changes, the skill presents the issue to keep, the issues to merge, and the information to move, then waits for explicit approval. It transfers unique reproduction steps, customer details, logs, and requested subscriber information before closing duplicates with a comment linking to the surviving issue. It does not delete issues, and it reports candidates it leaves separate along with the reasons.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 29, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Two issues for one bug means two people investigate it and neither sees the other's findings. The goal is one issue per underlying problem, holding everything anyone learned.
The same bug gets filed as "export is broken", "CSV download 500s", and "can't get my data out". No shared vocabulary. Run several searches — the error string, the feature name, the user-facing verb — and pool the results rather than trusting one query.
Include closed issues. A closed one is not evidence the bug came back — triage closes far more issues than fixes do. Treat it as a regression only when the issue records a fix that shipped or was reopened; otherwise it is just another report of the same open problem.
Group only when the underlying cause is plausibly identical. Two issues that both say "page is slow" are the same report only if they are slow for the same reason; merging them buries whichever one nobody reproduced.
When you are unsure, link them as related and say why rather than merging. An incorrect merge loses an issue silently, and nobody goes looking for what they think is already tracked.
Not simply the oldest. Prefer the one with the best reproduction, then the most discussion, then the earliest. If the oldest is a one-line report and a later one has steps, logs, and three participants, the later one survives.
Show the user each group you intend to merge: the survivor, the issues folding into it, and what you will move across. Merging is destructive in the way that matters — an issue closed as a duplicate stops being found by the people watching it, and an incorrect merge is only discovered when someone re-reports the bug months later. Get an explicit go-ahead per group, or on the set if the user prefers, before the first write.
Anything only present on the duplicate — reproduction steps, a customer name, a log line, a subscriber who wants to know when it is fixed — goes onto the survivor first. Then close the duplicate with a comment pointing at it, so someone arriving from a search or an old link lands somewhere useful.
Never delete. A closed issue with a pointer is how the next person's search finds the survivor.
List each group: the survivor, what was merged into it, and what you moved across. Flag the pairs you deliberately did not merge and why — those are the judgment calls someone may want to overturn.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Review how you use Superset and identify unused features that fit your workflow. Get a short list of suggestions, learn about each option, and set up selected features such as scheduled agents, parallel workspaces, or shared tasks.
Set up recurring tasks in Superset with an agent prompt, a schedule or event trigger, and a chosen execution workspace. After explicit confirmation, create the automation, check its saved settings, and review a real first run.
Browse pages, click controls, fill fields, and inspect screenshots or console messages through Superset's browser pane. Use it to preview a running web app, check interface behavior, and work through browser tasks in a visible session.
Build Stripe payments, subscriptions, and invoicing using verified documentation and API parameter definitions. The skill guides product selection, sandbox testing, and webhook handling, where server notifications determine payment and subscription state.
Verify a UI change or reproduce a bug in the running desktop app using the Chrome DevTools Protocol (CDP), a browser debugging interface. Follow the real user journey and compare screenshots with measurements such as route, scroll position, and persisted state.
Diagnose failed GitHub Actions runs by finding the first meaningful error, separating code problems from infrastructure issues and intermittent failures, and comparing the base branch. Get a focused report explaining the PR’s involvement and recommended next steps.