update-dedupe

Update the repo-local dedupe-issue-local skill from closed-as-duplicate signals.

292|39|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/warpdotdev/oz-for-oss --skill update-dedupe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-dedupe
Source: https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/update-dedupe
Command: npx skills add https://github.com/warpdotdev/oz-for-oss --skill update-dedupe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Update the repo-local dedupe-issue-local companion skill using closed-as-duplicate signals. Use when maintainers repeatedly close issues as duplicates of the same canonical thread and that pattern should feed back into triage duplicate detection.

Core Features & Use Cases

  • Ingests closed-as-duplicate signals from recent issues and maps them to canonical threads.
  • Proposes minimal edits to the dedupe-issue-local surface to summarize canonical clusters.
  • Maintains the core dedupe contract by limiting changes to the local companion surface.

Quick Start

Run the update-dedupe script to process recent signals and generate a payload for surface updates.

Frequently Asked Questions about update-dedupe

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub issue triage using closed duplicate signals?

Automating GitHub issue triage with closed duplicate signals works by ingesting recently closed threads, mapping them to canonical issues, and proposing minimal edits to your local dedupe surface to improve future duplicate detection.

What is the best way to feed closed-as-duplicate patterns back into open-source issue management?

Feeding closed-as-duplicate patterns back into issue management requires processing recent signals, inferring the canonical thread, and generating a concise update payload for the repo-local dedupe companion skill.

Do I need a local dedupe-issue companion skill to update duplicate detection?

Yes, updating duplicate detection requires access to the local SKILL.md and the dedupe-local files, as the script enforces a strict boundary that all generated edits remain within the local companion skill surface.

How does the update-dedupe script handle canonical thread inference for issue management?

The update-dedupe script handles canonical thread inference by ingesting recent closed-as-duplicate signals, identifying the canonical thread, and mapping duplicate clusters to generate concise updates for the dedupe surface.

What are the limitations of integrating closed duplicate signals into a repo-local dedupe skill?

The limitation of integrating closed duplicate signals is that a canonical thread must be inferred for updates to apply, and all proposed changes are strictly limited to the local companion skill to preserve the core dedupe contract.