smart-bug-fix
starsforks
How to install smart-bug-fix?
dnyoussef/context-cascade/smart-bug-fix
$npx -y skills add DNYoussef/context-cascade --skill smart-bug-fix/*============================================================================*/ /* SMART-BUG-FIX SKILL :: VERILINGUA x VERIX EDITION */ /*============================================================================*/
SKILL.md
| 1 | /*============================================================================*/ |
| 2 | /* SMART-BUG-FIX SKILL :: VERILINGUA x VERIX EDITION */ |
| 3 | /*============================================================================*/ |
| 4 | |
| 5 | --- |
| 6 | name: smart-bug-fix |
| 7 | version: 1.1.0 |
| 8 | description: | |
| 9 | [assert|neutral] Intelligent bug fixing workflow combining root cause analysis, multi-model reasoning, Codex auto-fix, and comprehensive testing. Uses RCA agent, Codex iteration, and validation to systematically fix b [ground:given] [conf:0.95] [state:confirmed] |
| 10 | category: delivery |
| 11 | tags: |
| 12 | - debugging |
| 13 | - rca |
| 14 | - codex |
| 15 | - testing |
| 16 | - essential |
| 17 | author: ruv |
| 18 | cognitive_frame: |
| 19 | primary: evidential |
| 20 | goal_analysis: |
| 21 | first_order: "Execute smart-bug-fix workflow" |
| 22 | second_order: "Ensure quality and consistency" |
| 23 | third_order: "Enable systematic delivery processes" |
| 24 | --- |
| 25 | |
| 26 | /*----------------------------------------------------------------------------*/ |
| 27 | /* S0 META-IDENTITY */ |
| 28 | /*----------------------------------------------------------------------------*/ |
| 29 | |
| 30 | [define|neutral] SKILL := { |
| 31 | name: "smart-bug-fix", |
| 32 | category: "delivery", |
| 33 | version: "1.1.0", |
| 34 | layer: L1 |
| 35 | } [ground:given] [conf:1.0] [state:confirmed] |
| 36 | |
| 37 | /*----------------------------------------------------------------------------*/ |
| 38 | /* S1 COGNITIVE FRAME */ |
| 39 | /*----------------------------------------------------------------------------*/ |
| 40 | |
| 41 | [define|neutral] COGNITIVE_FRAME := { |
| 42 | frame: "Evidential", |
| 43 | source: "Turkish", |
| 44 | force: "How do you know?" |
| 45 | } [ground:cognitive-science] [conf:0.92] [state:confirmed] |
| 46 | |
| 47 | ## Kanitsal Cerceve (Evidential Frame Activation) |
| 48 | Kaynak dogrulama modu etkin. |
| 49 | |
| 50 | /*----------------------------------------------------------------------------*/ |
| 51 | /* S2 TRIGGER CONDITIONS */ |
| 52 | /*----------------------------------------------------------------------------*/ |
| 53 | |
| 54 | [define|neutral] TRIGGER_POSITIVE := { |
| 55 | keywords: ["smart-bug-fix", "delivery", "workflow"], |
| 56 | context: "user needs smart-bug-fix capability" |
| 57 | } [ground:given] [conf:1.0] [state:confirmed] |
| 58 | |
| 59 | /*----------------------------------------------------------------------------*/ |
| 60 | /* S3 CORE CONTENT */ |
| 61 | /*----------------------------------------------------------------------------*/ |
| 62 | |
| 63 | # Smart Bug Fix |
| 64 | |
| 65 | ## Kanitsal Cerceve (Evidential Frame Activation) |
| 66 | Kaynak dogrulama modu etkin. |
| 67 | |
| 68 | |
| 69 | |
| 70 | ## Kanitsal Hata Ayiklama (Evidential Debugging) |
| 71 | |
| 72 | Every bug hypothesis requires evidence. The evidential frame ensures no fix is applied without proof of causation. |
| 73 | |
| 74 | **Evidence Requirements**: |
| 75 | - **GOZLEM** (Observation): Bug observed with concrete reproduction steps |
| 76 | - **HIPOTEZ** (Hypothesis): Theory X based on evidence Y |
| 77 | - **DOGRULAMA** (Verification): Fix verified by test results Z |
| 78 | - **RED** (Rejection): Hypothesis rejected due to counter-evidence W |
| 79 | |
| 80 | **Example**: |
| 81 | ``` |
| 82 | GOZLEM: API timeout after 30s under load (reproduction: 1000 concurrent requests) |
| 83 | HIPOTEZ: Database connection pool exhausted (evidence: pool size=10, active=10, waiting=990) |
| 84 | DOGRULAMA: Increased pool to 100, timeout resolved (evidence: 0 timeouts in 10k requests) |
| 85 | ``` |
| 86 | |
| 87 | ## Al-Itar al-Sarfi li-Tahlil al-Sabab (Root Cause Morphology) |
| 88 | |
| 89 | Symptoms are composed of causes. Decompose systematically using the "Why Chain" until the root is reached. |
| 90 | |
| 91 | **Morphological Decomposition**: |
| 92 | - **SYMPTOM**: Observable error or behavior (surface manifestation) |
| 93 | - **CAUSE-1**: Immediate cause (why-1: "Why did this symptom occur?") |
| 94 | - **CAUSE-2**: Deeper cause (why-2: "Why did cause-1 occur?") |
| 95 | - **ROOT**: True root cause (why-N: "Why did cause-(N-1) occur?" until no further "why" exists) |
| 96 | |
| 97 | **Example**: |
| 98 | ``` |
| 99 | SYMPTOM: Login fails on Firefox |
| 100 | CAUSE-1: JWT token not in cookie (why-1) |
| 101 | CAUSE-2: SameSite=Strict blocks cross-site cookies (why-2) |
| 102 | ROOT: Auth server on different subdomain than app (why-3 - architectural root) |
| 103 | ``` |
| 104 | |
| 105 | **NASA 5 Whys Integration**: |
| 106 | The morphological frame is implemented through the 5 Whys methodology: |
| 107 | 1. Why-1: Immediate cause (technical layer) |
| 108 | 2. Why-2: Systemic cause (design layer) |
| 109 | 3. Why-3: Process cause (architectural layer) |
| 110 | 4. Why-4: Cultural cause (organizational layer) |
| 111 | 5. Why-5: Root cause (foundational layer) |
| 112 | |
| 113 | ## When to Use This Skill |
| 114 | |
| 115 | - **Domain-Specific Work**: Tasks requiring specialized domain knowledge |
| 116 | - **Complex Problems**: Multi-faceted challenges needing systematic approach |
| 117 | - **Best Practice Implementation**: Following industry-standard methodologies |
| 118 | - **Quality-Critical Work**: Production code requiring high standards |
| 119 | - **Team Collaboration**: Coordinated work following shared processes |
| 120 | |
| 121 | ## When NOT to Use This Skill |
| 122 | |
| 123 | - **Outside Domain**: Tasks outside this skill specialty area |
| 124 | - **Incompatible Tech Stack**: Technologies not covered by this skill |
| 125 | - **Simple Tasks**: Trivial work not requiring specialized knowledge |
| 126 | - **Exploratory Work**: Experimenta |
People who liked this also viewed
6 picksType
- azure-diagnosticsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deploySkillsJul 2026
- systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesSkillsJul 2026
- safe-debugRigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training SkillsMay 2026
- explore-runRigor Improve / Rigor Explore run leaf skill for bounded exploratory evidence in deep learning research repositories. Use when the researcher explicitly authorizes exploratory runs such as small-subseSkillsMay 2026
- minimal-run-and-auditRigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation SkillsMay 2026
- insforge-debugUse when diagnosing problems in an InsForge project — reactive failures (SDK error object, HTTP 4xx/5xx, gateway timeout 502/503/504, edge function failure or timeout, login/OAuth/auth errors, RLS denSkillsJul 2026
