Debug Resolve

Use when debugging a bug or incident and you need a strict end-to-end investigation loop from reproduction to verified fix.

41 stars 1 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add wolverin0/claude-skills --skill debug-resolve
Manual install
git clone --depth 1 https://github.com/wolverin0/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/debug-resolve ~/.claude/skills/debug-resolve

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Debug & Resolve - Don't Stop Until Green

Systematic debugging skill that enforces resolution. Use when debugging a bug or investigating an issue.

## Rules
1. **NEVER stop mid-investigation.** Complete the full debug loop or explicitly document blockers.
2. **NEVER guess.** Read logs and code before proposing fixes.
3. **NEVER retry the same approach.** If it failed twice, try something different.

## Debug Loop

### Step 1: Gather Context
- Read the error message / bug report carefully
- Identify which service is affected (check project CLAUDE.md)
- Read relevant source files (entry point -> error location)
- Check logs: server logs, browser console, Supabase logs, Docker logs

### Step 2: Reproduce
- Confirm the bug exists with a concrete test or verification
- If you can't reproduce, gather more context before proceeding
- Write a failing test if possible (this becomes your regression test)

### Step 3: Isolate Root Cause
- Trace the data flow from input to error
- Add temporary logging if needed (remove after)
- Check recent changes: `git log --oneline -10`, `git diff HEAD~3`
- For Supabase: check RLS policies, auth state, table permissions
- For Docker: check if container has latest code (`docker exec cat /app/file.js`)

### Step 4: Fix
- Make the minimal change that fixes the root cause
- Don't refactor surrounding code
- Don't fix other unrelated issues you noticed

### Step 5: Verify (MANDATORY)
Read the full skill on GitHub

Details

Skill name
debug-resolve
Path
skills/debug-resolve/SKILL.md
Repo updated
17 November 2026

FAQ

What does the Debug Resolve skill do?

Use when debugging a bug or incident and you need a strict end-to-end investigation loop from reproduction to verified fix.

How do I install the Debug Resolve skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add wolverin0/claude-skills --skill debug-resolve. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Debug Resolve popular?

It lives in wolverin0/claude-skills, which has 41 GitHub stars and 1 forks.

Related skills

UI UX Pro Max

41

wolverin0/claude-skills

UI/UX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, and HTML/CSS). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, and check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, and mobile app. Elements: button, modal, navbar, sidebar, card, table, form, and chart. Styles: glassmorphism,

Frontend & Design

Audit Blind Spots

41

wolverin0/claude-skills

Walk the B1-B19 AI-to-AI blind-spot catalog systematically. Use during the audit pipeline AFTER hard-stops and Tambon hunt and BEFORE the 13 domain audits. Output: PRESENT / NOT PRESENT for each B-class with evidence. Findings flow into the appropriate domains.

AI, LLMs & Agents

Audit Decisions

41

wolverin0/claude-skills

Standardize remediation decisions, baseline-policy entries, and legal-review banners for accepted, deferred, or policy-blocked audit findings.

Marketing, Sales & Business

Decode Minified Js Gates

45

pjt222/agent-almanac

Classify gate call variants in a minified JavaScript bundle. Covers context-window extraction around a flag occurrence, identification of 4–6 reader variants (sync boolean, sync config-object, bootstrap-aware TTL, truthy-only, async bootstrap, async bridge), default-value extraction (boolean / null / numeric / config-object literal), conjunction detection across `&&` predicates, kill-switch inversion detection, and production of a gate-mechanics record that feeds probe- feature-flag-state. Use when a flag's behavior cannot be inferred from its name alone, when the binary uses multiple reader l

Software DevelopmentIn 1 list

Curate Collection

45

pjt222/agent-almanac

Build and maintain a library collection through acquisitions, weeding (deaccessioning), collection assessment, reader advisory, and interlibrary loan coordination. Covers selection criteria, collection development policies, the CREW/MUSTIE method for weeding, usage analysis, and responsive collection management. Use when building a new collection with a defined scope and budget, assessing an existing collection for gaps or outdated materials, when shelves are overcrowded and systematic weeding is needed, or when establishing a formal collection development policy.

Software DevelopmentIn 1 list

Design CLI Output

45

pjt222/agent-almanac

Design terminal output for a CLI tool with chalk colors, Unicode glyphs, multiple verbosity levels (human, verbose, quiet, JSON), and consistent voice rules. Covers color palette selection, status indicator design, reporter function architecture, ceremony/narrative output variants, and cross-terminal compatibility. Use when building a new CLI reporter module, adding warm narrative output to an existing tool, standardizing output across multiple commands, or designing machine-readable JSON alongside human-readable text.

Software DevelopmentIn 1 list

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.