一键导入
github-issue-dedupe
// Detect duplicate GitHub issues using semantic search and keyword matching. Use when asked to find duplicates, check for similar issues, or set up automated duplicate detection.
// Detect duplicate GitHub issues using semantic search and keyword matching. Use when asked to find duplicates, check for similar issues, or set up automated duplicate detection.
Generate reproducible analysis artifacts — SQL queries, Python visualizations, and summary tables — as you work through a BigQuery data analysis. Use when asked to conduct a deep dive, exploratory analysis, or investigation that goes beyond a simple data lookup.
Provide a lookup index of dbt models (BigQuery tables) to guide query writing against a data warehouse. Use when you need to query, analyze, or look up data in a dbt-powered data warehouse, or when resolving a vague data question into the right BigQuery tables to query.
Diagnose and fix GitHub Actions CI failures. Inspects workflow runs and logs, identifies root causes, implements minimal fixes, and pushes to a fix branch. Use when CI is failing, red, broken, or needs diagnosis.
Create a GitHub pull request following project conventions. Use when the user asks to create a PR, submit changes for review, or open a pull request. Handles commit analysis, branch management, and PR creation using the gh CLI tool.
Update user-facing documentation when code changes. Use when asked to update docs, review docs, handle documentation changes, run scheduled documentation tasks, or analyze recent commits for documentation needs.
Triage GitHub bug reports for actionability. Use when evaluating whether a bug issue has sufficient detail and identifying missing information from the reporter.
| name | github-issue-dedupe |
| description | Detect duplicate GitHub issues using semantic search and keyword matching. Use when asked to find duplicates, check for similar issues, or set up automated duplicate detection. |
| license | MIT |
Find duplicate GitHub issues using multi-strategy search. Can be run manually or automated via GitHub Actions.
Extract key information from the target issue:
Use gh to search for related issues using multiple strategies:
For each potential duplicate:
gh issue view <number>High confidence indicators:
Low confidence (not duplicates):
If duplicates found:
Post comment on target issue:
gh issue comment <number> --body "This is potentially a duplicate of #123 and #456."
Format rules:
Only comment if high confidence (90%+ certain). When uncertain, do nothing.
Target Issue #150:
Title: "Dropdown menu stays open on mobile Safari"
Body: Clicking menu items doesn't close dropdown on iOS
Search process:
gh issue list --search "dropdown mobile safari"
gh issue list --search "menu doesn't close"
gh issue view 87 # Found similar issue
Issue #87:
Title: "Mobile menu not closing after selection"
Body: On iOS Safari, menu stays open after clicking items
Determination: Duplicate
Target Issue #200:
Title: "Form validation error on submit"
Error: "Cannot read property 'value' of null"
Search process:
gh issue list --search "form validation"
gh issue list --search "Cannot read property value null"
gh issue view 175
Issue #175:
Title: "Form submission fails"
Error: "Cannot read property 'email' of undefined"
Determination: Not duplicate
Target Issue #300:
Title: "Build fails with 'module not found' error"
Error: Error: Cannot find module './config'
Search results:
Action:
gh issue comment 300 --body "This is potentially a duplicate of #250 and #280."