issue-dedup

Search open and closed GitHub issues before creating new ones.

10|Updated Sep 24, 2025
One-click install
npx skills add https://github.com/FriendlyInternet/nuxt-crouton --skill issue-dedup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-dedup
Source: https://github.com/FriendlyInternet/nuxt-crouton/tree/main/.claude/skills/issue-dedup
Command: npx skills add https://github.com/FriendlyInternet/nuxt-crouton --skill issue-dedup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that no duplicate GitHub issues are created by requiring a search for existing related issues before new ones can be created.

Core Features & Use Cases

  • Prevent Duplicate Issues: Before creating a new issue, the Skill searches for existing related issues.
  • Search for Open and Closed Issues: It searches both open and closed issues to catch duplicates that have been resolved.
  • Force Decision Making: It forces a decision on whether to reuse, replace, or create a new issue based on the search results.
  • Automated Check: It uses a PreToolUse hook to enforce the search before allowing an issue to be created.

Quick Start

Run the /issue-dedup command before creating a new GitHub issue.

Frequently Asked Questions about issue-dedup

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

FAQPage Schema
How do I prevent duplicate GitHub issues from being created?

You can prevent duplicate GitHub issues by enforcing an automated search gate that scans existing open and closed issues before allowing new issue creation. This forces a decision on whether to reuse, replace, or proceed with creating a new issue.

Why should I search closed GitHub issues before creating a new one?

Searching closed GitHub issues before creating a new one catches duplicates that have already been resolved. This prevents redundant work by forcing users to decide whether to reuse or replace existing issues instead of creating duplicates.

Can I enforce a search check before a GitHub issue is created automatically?

Yes, you can enforce an automated search check before a GitHub issue is created by using a PreToolUse hook. This gate intercepts the creation process and requires searching for related issues before allowing the action to proceed.

How do I set up a hard gate for duplicate issue prevention on GitHub?

You set up a hard gate for duplicate issue prevention by running the /issue-dedup command, which utilizes a PreToolUse hook to intercept issue creation and mandate a search for existing related open and closed issues.

What happens when a duplicate GitHub issue is found during the search?

When a duplicate GitHub issue is found during the search, the workflow forces a decision on whether to reuse the existing issue, replace it, or proceed with creating a new issue based on the search results.