dedupe-issue-local
GitHub为warp仓库定制Issue去重指南，规范标题清洗、上下文比对及特定场景（终端/Agent/UI）的重复判定逻辑，辅助维护高效处理问题。
Trigger Scenarios
Install
npx skills add warpdotdev/warp --skill dedupe-issue-local -g -y
SKILL.md
Frontmatter
{
"name": "dedupe-issue-local",
"description": "Repo-specific dedupe guidance for warp. Only the categories declared overridable by the core dedupe-issue skill may be specialized here.",
"specializes": "dedupe-issue",
"specializes_source": "warpdotdev\/oz-for-oss:.agents\/skills\/dedupe-issue"
}
Repo-specific dedupe guidance for warp
Prerequisite: install the parent skill
This skill specializes the core dedupe-issue skill (named in the specializes frontmatter field) and is not functional on its own. Before applying its guidance, confirm the parent skill is installed and resolvable at .agents/skills/dedupe-issue/SKILL.md. If it is missing, install it first by copying the skill directory from the source declared in the specializes_source frontmatter field (warpdotdev/oz-for-oss:.agents/skills/dedupe-issue). Then continue with the guidance below.
This file is a companion to the core dedupe-issue skill. It does not
redefine the duplicate-detection algorithm, the similarity thresholds,
or the output contract. It only specializes the override categories the
core skill marks as overridable.
Repo-specific normalizations
- Strip low-signal title prefixes such as
Bug:,Feature:,Request:,[Bug],[Feature],Warp:, and platform tags like[macOS],[Linux], or[Windows]before comparing titles. - Treat app channel/version, OS version, and shell name as supporting evidence, not as duplicate blockers, when the core symptom and reproduction path are otherwise the same.
- Do not collapse distinct Warp surfaces just because they share a word like "agent", "terminal", "MCP", "settings", "search", or "sync". Require overlap in the actual failing behavior or requested capability.
- For terminal issues, compare shell/session context, command output behavior, prompt rendering, input behavior, and remote/tmux involvement before treating two reports as duplicates.
- For agent or MCP issues, compare the trigger path, local vs cloud execution, MCP server/tool, visible error, and expected workflow before treating two reports as duplicates.
- For UI/rendering issues, compare the affected surface and visible symptom. Similar screenshots or recordings are strong duplicate evidence when the title is vague.
Known-duplicate clusters
No known-duplicate clusters have been captured for this repository yet. The weekly update-dedupe loop will propose additions here over time when maintainers repeatedly close issues as duplicates of the same canonical thread.
Version History
- 726c1b6 Current 2026-07-24 20:21
