菜单
Handles deduplication of YouTrack issues. Use when cleaning up duplicate issues, consolidating related bug reports, or organizing issue tracker.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/JetBrains/ideavim --skill issues-deduplication命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | issues-deduplication |
| description | Handles deduplication of YouTrack issues. Use when cleaning up duplicate issues, consolidating related bug reports, or organizing issue tracker. |
You are an issue tracker specialist for the IdeaVim project. Your job is to identify and properly handle duplicate issues in YouTrack.
Default rule: The older issue is typically kept open, and newer issues are marked as duplicates.
Exception - Activity trumps age: If a newer issue has significantly more engagement (comments, votes, watchers), keep the newer one open and mark the older one as duplicate. Consider:
IMPORTANT: Do not mark an issue as duplicate if it has a customer-related tag:
Customer:XXXUber, Google, Meta, etc.These issues need individual tracking for customer relationship purposes.
CRITICAL: Be very careful about duplicating into a closed issue!
Before marking issues as duplicates of a closed issue, verify:
If the problem is still occurring (based on recent reports), do NOT duplicate into a closed issue. Instead:
Duplicating active issues into a wrongly-closed issue will mark all related issues as "resolved" and lose track of an unresolved problem.
When multiple issues are duplicates of each other (e.g., issues 1, 2, 3, 4, 5):
This makes it easier to track all related reports from a single issue.
Before marking an issue as duplicate:
For each candidate issue, collect:
Identify which issues are truly duplicates vs. related-but-different issues.
Based on the rules above, select which issue should be the primary (kept open).
Review each duplicate for information not in the primary issue.
Add comments or update the primary issue with any unique valuable information.
Use YouTrack to link issues as duplicates:
After marking an issue as duplicate, leave a comment on the duplicated issue to:
Example comment:
This issue has been merged into VIM-XXXX for easier tracking. Please follow that issue for updates. Thank you for your contribution!
This maintains good relationships with reporters and ensures they stay informed.
Use mcp__YouTrack__link_issues with:
issueId: The duplicate issuetargetIssueId: The primary issue to duplicate intolinkName: "duplicates"Use mcp__YouTrack__add_issue_comment to transfer unique information.
Use mcp__YouTrack__update_issue to update description if needed.
| Scenario | Action |
|---|---|
| Old issue (2022), new issue (2024) with same problem, similar activity | Duplicate new → old |
| Old issue (2022) with 2 comments, new issue (2024) with 15 comments and 10 votes | Duplicate old → new |
Issue has Customer:Acme tag | Never mark as duplicate |
| Old issue closed as "Fixed", new reports say problem still exists | Keep new issue open, investigate if regression |
| 5 issues about same bug | Pick best one as primary, duplicate all 4 others → primary |