dedupe-issue-local

Apply repository-specific normalization rules to Warp issue reports for duplicate detection.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/89jobrien/warpx --skill dedupe-issue-local
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dedupe-issue-local
Source: https://github.com/89jobrien/warpx/tree/main/.agents/skills/dedupe-issue-local
Command: npx skills add https://github.com/89jobrien/warpx --skill dedupe-issue-local

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Repo-specific dedupe guidance for warp-external reports. It provides targeted normalization and override options to align duplicate detection within a single repository without altering the core dedupe-issue algorithm.

Core Features & Use Cases

  • Repo-specific normalizations to strip noisy title prefixes and treat environment metadata as supporting evidence rather than primary signals.
  • Fine-grained override of dedupe categories to tailor the comparison behavior to the repository's conventions.
  • Use Case: When multiple Warp issues describe the same underlying failure across different surfaces, this skill ensures they are evaluated against the same signals for accurate deduplication within that repo.

Quick Start

Apply repo-local normalization rules to a set of Warp issues in your project.

Frequently Asked Questions about dedupe-issue-local

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

FAQPage Schema
How do I apply repository-specific rules to deduplicate Warp issues during triage?

To deduplicate Warp issues during triage, you can apply repository-specific normalization rules that strip noisy title prefixes and treat environment metadata as supporting evidence to improve duplicate detection accuracy.

What is issue normalization and how does it help with duplicate detection in a single repo?

Issue normalization standardizes titles and context within a single repository so that multiple Warp issues describing the same underlying failure are evaluated against the same signals, ensuring accurate duplicate detection across different surfaces.

Can I override dedupe categories to match my repository's conventions for Warp issues?

Yes, you can fine-tune dedupe behavior by overriding dedupe categories to match your repository's conventions, which tailors the comparison logic without altering the underlying core dedupe-issue algorithm.

What's the best way to handle duplicate Warp issue reports that describe the same failure across different surfaces?

The best way to handle duplicate Warp issue reports across different surfaces is to evaluate them against repository-local normalizations and override categories, aligning duplicate detection within that specific repository.

Do I need to modify the core dedupe-issue algorithm to support repo-local normalization rules?

No, you do not need to modify the core dedupe-issue algorithm; repo-local normalizations and override categories specialize the core behavior by introducing repository-local rules without altering the underlying algorithm.