القائمة
Patterns for detecting duplicate GitHub issues before creating new ones.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | issue-duplicate-detection |
| description | Patterns for detecting duplicate GitHub issues before creating new ones. |
This skill provides patterns for detecting and handling duplicate GitHub issues.
From the potential new issue:
# Search open issues
gh issue list --state open --search "keyword1 keyword2" --limit 20
# Search all issues (including closed)
gh issue list --state all --search "keyword1 keyword2" --limit 20
# Search with specific terms
gh issue list --state all --search "in:title error message"
# Search by label
gh issue list --state open --label "bug" --search "keyword"
For each potential match:
## Duplicate Check Results
### Potential Duplicates Found
| # | Title | State | Created | Similarity |
|---|-------|-------|---------|------------|
| #123 | Similar issue title | Open | 2024-01-10 | High |
| #456 | Related problem | Closed | 2023-12-01 | Medium |
### Analysis
**#123** appears to describe the same issue:
- Same error message mentioned
- Same component affected
- Both triggered by same user action
**Recommendation**: Add context to #123 instead of creating new issue.
### If Not Duplicate
If you confirm this is a new issue, I'll proceed with creation.
gh issue list --state all --search "TypeError: Cannot read property"
gh issue list --state all --search "in:title checkout"
gh issue list --state all --search "in:body payment"
gh issue list --state all --author @me --search "keyword"
gh issue list --state open --label "bug" --search "in:title login error"
Action: Recommend adding to existing issue
Action: Recommend linking issues
Action: Proceed with new issue
gh issue comment 123 --body "$(cat <<'EOF'
Additional report:
[New information not in original issue]
Confirming this is still occurring as of [date].
EOF
)"
When related but not duplicate:
In new issue body:
Related to #123
See also #456
gh issue close {number} --comment "Closing as duplicate of #123"
gh issue edit {number} --add-label "duplicate"
| Query | Meaning |
|---|---|
keyword | Search all fields |
in:title keyword | Title only |
in:body keyword | Body only |
is:open | Open issues |
is:closed | Closed issues |
label:bug | With label |
author:username | By author |
assignee:username | Assigned to |
created:>2024-01-01 | Created after |
updated:>2024-01-01 | Updated after |
Combine with AND:
gh issue list --search "is:open label:bug in:title checkout"
Patterns for generating Gamma.app-compatible slide deck markdown from GitHub data for customer-facing account management presentations
Patterns for generating Gamma.app-compatible slide deck markdown from Linear data for customer-facing account management presentations
Patterns and templates for creating sprint/project retrospective reports from Jira data with time tracking and blocker analysis.
Multi-platform Electron build configuration - esbuild bundling, electron-builder setup, and distribution
Integrate external CLI tools (Claude, Node, npx) in Electron apps with proper PATH handling
Handle native Node.js modules in Electron - better-sqlite3, sharp, keytar packaging patterns