--- name: bug-diagnosis description: "[Fix & Debug] Quick triage skill for initial bug assessment and user-reported issues. Use for bug reports, error reports, quick diagnosis, initial triage, "what's causing", "why is this failing". For systematic multi-file debugging with verification protocols, use `debug` skill instead." allowed-tools: Read, Write, Edit, Bash, Grep, Glob, Task, WebFetch, WebSearch, TodoWrite --- > **Skill Variant:** Use this skill for **quick bug triage and interactive debugging** with user feedback. For systematic autonomous debugging workflows with 4-phase protocol and verification gates, use `debug` skill instead. For feature investigation without fixes, use `investigate`. ## Summary **Goal:** Quick triage and diagnosis of user-reported bugs with external memory-driven analysis and approval gate before fixing. | Step | Action | Key Notes | | ---- | ------------------------- | --------------------------------------------------------------------------- | | 1 | Initialize analysis | Create `.ai/workspace/analysis/[name].analysis.md` with structured sections | | 2 | Discovery & file analysis | Semantic search, batch files in groups of 10, document dependencies | | 3 | Root cause analysis | Rank causes across technical, business logic, data, integration dimensions | | 4 | Approval gate | Present findings and fix strategy -- DO NOT fix without user approval | | 5 | Execute fix | Minimal targeted changes following platform patterns | **Key Principles:** - **Be skeptical. Critical thinking. Everything needs traced proof.** — Never accept code at face value; verify claims against actual behavior, trace data flow end-to-end, and demand evidence (file:line references, grep results, runtime confirmation) for every finding - Always use external memory file for structured analysis -- never rely on context alone - If confidence < 90%, request user confirmation before proceeding - For systematic multi-file debugging, use `debug` skill instead ## Disambiguation - For **systematic multi-file debugging** with verification protocols -> use `debug` - For **feature investigation** without fixes -> use `investigate` - This skill focuses on **quick triage** of user-reported bugs # Bug Diagnosis & Debugging You are to operate as an expert full-stack .NET Angular debugging engineer to diagnose, debug, and fix the bug described in `[bug-description-or-bug-info-file-path]`. **IMPORTANT**: Always think hard, plan step by step to-do list first before execute. Always remember to-do list, never compact or summary it when memory context limit reach. **Prerequisites:** **MUST READ** `.claude/skills/shared/anti-hallucination-protocol.md` before executing. --- ## PHASE 1: EXTERNAL MEMORY-DRIVEN BUG ANALYSIS Build a structured knowledge model in a Markdown analysis file at `.ai/workspace/analysis/[semantic-name].analysis.md`. ### PHASE 1A: INITIALIZATION AND DISCOVERY 1. **Initialize** the analysis file with: Metadata, Progress, Errors, File List, Knowledge Graph sections 2. **Discovery searches**: Semantic and grep search all error keywords. Prioritize: Domain Entities, Commands, Queries, Event Handlers, Controllers, Background Jobs, Consumers, Frontend Components ### PHASE 1B: SYSTEMATIC FILE ANALYSIS 1. Count total files, split into batches of 10 in priority order 2. For each file, document: filePath, type, content, symbols, dependencies, businessContext, errorPatterns, stackTraceRelevance, validationLogic ### PHASE 1C: OVERALL ANALYSIS Write comprehensive summary showing: end-to-end workflows, error propagation paths, integration points and failure points. --- ## PHASE 2: ROOT CAUSE ANALYSIS & FIX STRATEGY ### Root Cause Dimensions 1. **Technical**: Code defects, architectural issues 2. **Business Logic**: Rule violations, validation failures 3. **Data**: Data corruption, integrity violations 4. **Integration**: API contract violations, communication failures ### Generate Fix Strategy Document alternatives with: suggestedFix, riskAssessment, regressionMitigation, testingStrategy, rollbackPlan. --- ## PHASE 3: APPROVAL GATE **CRITICAL**: Present root cause analysis and fix strategy for explicit user approval before implementation. --- ## PHASE 4: DEBUGGING EXECUTION Once approved: execute fix plan, make minimal targeted changes, follow platform patterns. --- ## Platform Error Patterns Reference ### Backend Validation ```csharp return base.Validate() .And(_ => condition, "Error message") .AndAsync(async req => await ValidateAsync(req)); await repository.GetByIdAsync(id).EnsureFound($"Not found: {id}"); await entity.ValidateAsync(repository, ct).EnsureValidAsync(); ``` ### Frontend Error Handling ```typescript this.apiService .getData() .pipe( this.observerLoadingErrorState('loadData'), this.tapResponse( data => this.updateState({ data }), error => this.handleError(error) ), this.untilDestroyed() ) .subscribe(); ``` --- ## Quick Verification Checklist Before removing/changing ANY code: - [ ] Searched static imports? - [ ] Searched string literals? - [ ] Checked dynamic invocations? - [ ] Read actual implementations? - [ ] Traced dependencies? - [ ] Declared confidence level? **If confidence < 90% -> REQUEST USER CONFIRMATION** --- ## Common Bug Categories | Category | Examples | | ------------- | ------------------------------------------------------------ | | Data Issues | Missing null checks, race conditions, stale cache | | Validation | Missing rules, bypassed validation, async not awaited | | Cross-Service | Message bus failures, sync ordering, API contract mismatches | | Frontend | Lifecycle issues, state bugs, missing error handling | | Authorization | Missing role checks, wrong company context | ## Related - `debug` - `code-review` --- **IMPORTANT Task Planning Notes (MUST FOLLOW)** - Always plan and break work into many small todo tasks - Always add a final review todo task to verify work quality and identify fixes/enhancements --- Source attribution: duc01226 Original project: https://github.com/duc01226/EasyPlatform/blob/84eb5f4e42ac5aca0d7b6aab50ef8e68a277e5ce/.claude/skills/bug-diagnosis/SKILL.md License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Dave AI. ## Upstream license notice MIT License Copyright (c) 2021 Dang Phuoc Duc Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Dave AI resource metadata Creator / publisher: duc01226 Original project: https://github.com/duc01226/EasyPlatform/blob/84eb5f4e42ac5aca0d7b6aab50ef8e68a277e5ce/.claude/skills/bug-diagnosis/SKILL.md Attribution basis: Recovered original package and original project license at a pinned revision Fields of work: Development & Engineering, Sales, Customer Support Roles: Customer Success Manager, QA / Test Engineer, Sales Development Rep (SDR), Support Agent, Technical Support Specialties: Specialty not specified Tools: Bash, Glob, Grep, Task, Todowrite, Webfetch, Websearch Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: d2ca511cf8b11d83affd89761f8842182451b2350b544b6fb79de8090571d923 Metadata reviewed: 2026-10-27 This metadata supersedes earlier Dave AI catalog attribution. Original instruction and supporting files are preserved.