When an issue is opened, compares it against the repository's existing open issues and, if it finds likely duplicates, posts a comment linking the candidates so maintainers (or the author) can consolidate. Conservative — it suggests possible duplicates for a human to confirm, it never closes anything.
- Identifier
duplicate-issue-detector- Version
- 1.1.0
- Steps
- 3
- Triggers
- 1
- issues
- duplicates
- triage
- automated
When it runs
issue.opened- Settle delay
- 15s after the event
Only when all hold
- actor.username not in dependabot, dependabot[bot], renovate, renovate[bot], github-actions, github-actions[bot]
- actor.username not contains [bot]
The pipeline
The graph below is the one the workflow opens with in the builder — same steps, same layout, drawn on the same canvas. The run playing through it is a simulation; the branches and conditions are real.
- 01Issue Opened
triggerThe event that starts the run.
- 02Find Duplicate Issues
agent.runOne agent works the task with its toolkit.
- 03Publish Duplicate Report
report.publishPosts or updates a deduplicated report comment.
The agent
Duplicate Issue Detector
- Base type
- Senior Developer
- Temperature
- 0.1
- Max iterations
- 15
- Tools
- 2
Git provider · 1
list_issuesList Issues · read
Status · 1
update_statusUpdate Status · write
Related playbooks
Issue Triage
Labels new issues as bug, feature, question, docs, or task and checks for missing info.
Auto Root Cause Analysis
Investigates bug-labeled issues, traces the root cause in code, and posts the analysis with a fix.
Stale Issue Reaper
Weekly sweep that classifies quiet issues by reason, nudges them, and flags the oldest for closure.