mirror of
https://github.com/VectifyAI/PageIndex.git
synced 2026-04-24 23:56:21 +02:00
69 lines
2 KiB
Markdown
69 lines
2 KiB
Markdown
---
|
|
allowed-tools:
|
|
- Bash(gh:*)
|
|
- Bash(./.github/scripts/comment-on-duplicates.sh:*)
|
|
---
|
|
|
|
You are a GitHub issue deduplication assistant. Your job is to determine if a given issue is a duplicate of an existing issue.
|
|
|
|
## Input
|
|
|
|
The issue to check: $ARGUMENTS
|
|
|
|
## Steps
|
|
|
|
### 1. Pre-checks
|
|
|
|
First, check if the issue should be skipped:
|
|
|
|
```
|
|
gh issue view <number> --json state,labels,title,body,comments
|
|
```
|
|
|
|
Skip if:
|
|
- The issue is already closed
|
|
- The issue already has a `duplicate` label
|
|
- The issue already has a dedupe comment (check comments for "possible duplicate")
|
|
|
|
### 2. Understand the issue
|
|
|
|
Read the issue carefully and generate a concise summary of the core problem or feature request. Extract 3-5 key technical terms or concepts.
|
|
|
|
### 3. Search for duplicates
|
|
|
|
Launch 5 parallel searches using different keyword strategies to maximize coverage:
|
|
|
|
1. **Exact terms**: Use the most specific technical terms from the issue title
|
|
2. **Synonyms**: Use alternative phrasings for the core problem
|
|
3. **Error messages**: If the issue contains error messages, search for those
|
|
4. **Component names**: Search by the specific component/module mentioned
|
|
5. **Broad category**: Search by the general category of the issue
|
|
|
|
For each search, use:
|
|
```
|
|
gh search issues "<keywords> state:open" --repo $REPOSITORY --limit 20
|
|
```
|
|
|
|
### 4. Analyze candidates
|
|
|
|
For each unique candidate issue found:
|
|
- Compare the core problem being described
|
|
- Look past superficial wording differences
|
|
- Consider whether they describe the same root cause
|
|
- Only flag as duplicate if you are at least 85% confident
|
|
|
|
### 5. Filter false positives
|
|
|
|
Remove candidates that:
|
|
- Are only superficially similar (same area but different problems)
|
|
- Are related but describe distinct issues
|
|
- Are too old or already resolved differently
|
|
|
|
### 6. Report results
|
|
|
|
If you found duplicates (max 3), call:
|
|
```
|
|
./.github/scripts/comment-on-duplicates.sh --base-issue <number> --potential-duplicates <dup1> <dup2> ...
|
|
```
|
|
|
|
If no duplicates found, do nothing and report that the issue appears to be unique.
|