Agent Skills › terzigolu/warp-lite › dedupe-issue-local

dedupe-issue-local

GitHub

为 warp-external 仓库提供 Issue 去重指导，规范标题清洗、上下文比对及特定领域（终端、Agent、UI）的重复判定标准，辅助核心技能优化问题合并。

.agents/skills/dedupe-issue-local/SKILL.md terzigolu/warp-lite

Trigger Scenarios

需要判断两个 Issue 是否为重复项时执行 Issue 去重或合并操作时

Install

npx skills add terzigolu/warp-lite --skill dedupe-issue-local -g -y

More Options

Non-standard path

npx skills add https://github.com/terzigolu/warp-lite/tree/warp-lite/main/.agents/skills/dedupe-issue-local -g -y

Use without installing

npx skills use terzigolu/warp-lite@dedupe-issue-local

指定 Agent (Claude Code)

npx skills add terzigolu/warp-lite --skill dedupe-issue-local -a claude-code -g -y

安装 repo 全部 skill

npx skills add terzigolu/warp-lite --all -g -y

预览 repo 内 skill

npx skills add terzigolu/warp-lite --list

SKILL.md

Frontmatter

{
    "name": "dedupe-issue-local",
    "description": "Repo-specific dedupe guidance for warp-external. Only the categories declared overridable by the core dedupe-issue skill may be specialized here.",
    "specializes": "dedupe-issue"
}

Repo-specific dedupe guidance for `warp-external`

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.