ticket-duplicate-detection
Detects similar/duplicate tickets before creating new ones.
What this skill does
# Ticket Duplicate Detection Skill Patterns for checking Linear for similar/duplicate tickets before creating new ones. ## Purpose Avoid creating duplicate tickets by: - Searching Linear with multiple query patterns - Presenting potential duplicates to user - Offering options: link, sub-issue, or proceed ## Detection Methodology ### Step 1: Extract Search Keywords From the user's issue description, extract: 1. **Primary keywords**: Main noun/verb (e.g., "drawer", "modal", "z-index") 2. **Technical terms**: Component names, error messages, file names 3. **Synonyms**: Related terms (e.g., "sidebar" for "drawer", "dialog" for "modal") ### Step 2: Search Linear Use `mcp__linear__list_issues` with multiple queries: ``` # Search 1: Primary keywords mcp__linear__list_issues with query="drawer z-index", updatedAt="-P30D", limit=20 # Search 2: Error messages (if applicable) mcp__linear__list_issues with query="handleTabChange undefined", limit=10 # Search 3: Component/file names mcp__linear__list_issues with query="AppDrawer", limit=10 ``` **Time range**: Search issues updated in last 30 days (`updatedAt: "-P30D"`) ### Step 3: Filter Results Check results for: - Open issues (active work) - Recently closed (might be reopened) - Same component/area - Similar symptoms ### Step 4: Present to User If potential duplicates found: ```markdown ## Potential Duplicate Tickets Found I found these similar tickets before creating a new one: 1. **PROJ-123**: "Fix drawer z-index issue" (Open) - Similar: Both about drawer layering 2. **PROJ-100**: "Modal appears behind sidebar" (Done - 2 weeks ago) - Similar: Same UI area **Options:** A) Link to existing ticket (add as related) B) Create as sub-issue of existing ticket C) Proceed with new ticket (different issue) Which option? ``` ### Step 5: Take Action Based on user choice: - **Option A**: Add link/comment to existing ticket - **Option B**: Create with parentId set - **Option C**: Create new ticket as planned ## Search Patterns Reference | Issue Type | Primary Search | Secondary Search | |------------|---------------|------------------| | UI Bug | Component name + symptom | "modal", "dialog", "overlay" | | Error | Error message | Function/file name | | Feature | Feature name | Related features | | Performance | "slow", "performance" | Component name | | Styling | "z-index", "css", "style" | Component name | ## Common Synonym Mappings | Term | Also search for | |------|-----------------| | drawer | sidebar, nav, navigation | | modal | dialog, popup, overlay | | button | btn, click, action | | form | input, field, validation | | error | bug, crash, fail | ## Integration Used by: - `linear-ticket-creator` agent (required first step) - `/ticket-create` command (via agent)
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.