skills.rest
fercracix33
fercracix33COMMUNITY
Explore all skills by this author →
GitHub

bug-fixer-diagnostic

Diagnose production bugs across Clean Architecture layers using MCP tools and Context7.

Updated Sep 29, 2025
Search Tags:#Clean Architecture#Troubleshooting#Testing#Debugging#Bug Fix#Root Cause Analysis#Diagnostics
One-click install
npx skills add https://github.com/fercracix33/poli2-clean-architecture --skill bug-fixer-diagnostic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-fixer-diagnostic
Source: https://github.com/fercracix33/poli2-clean-architecture/tree/main/.claude/skills/bug-fixer-diagnostic
Command: npx skills add https://github.com/fercracix33/poli2-clean-architecture --skill bug-fixer-diagnostic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a systematic, research-driven workflow to diagnose, fix, and prevent bugs across all layers of a Clean Architecture application. It eliminates guesswork, reduces debugging time, and ensures fixes are robust and don't introduce regressions, allowing your team to deliver stable, high-quality software faster.

Core Features & Use Cases

  • Systematic Root Cause Analysis: Guides through classifying bugs, deep diagnosis using MCP tools (Chrome DevTools, Supabase), and identifying the true root cause, not just symptoms.
  • Research-Driven Fixes: Mandates Context7 consultation for the latest patterns and best practices before implementing minimal, targeted fixes, ensuring modern and effective solutions.
  • Comprehensive Verification: Ensures fixes work, no regressions are introduced, and performance/security are maintained through extensive unit, integration, and E2E testing.
  • Use Case: When a user reports a UI bug where a form field isn't validating correctly, this Skill uses Chrome DevTools to inspect the live state, consults Context7 for Zod validation patterns, identifies a .parse() vs .safeParse() issue, implements the fix, and verifies all tests pass.

Quick Start

Use the bug-fixer-diagnostic skill to diagnose and fix the reported UI bug on the /settings page where the email field validation is failing, ensuring all tests pass and no regressions are introduced after the fix.

Frequently Asked Questions about bug-fixer-diagnostic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose and fix bugs across all layers of a Clean Architecture application?▼

Root cause analysis in Clean Architecture requires systematic diagnosis across Validation, Database, UI, E2E, and Authorization layers using structured debugging workflows, MCP tools like Chrome DevTools and Supabase inspection, and research-driven fixes validated against comprehensive test suites to prevent regressions.

What's the best way to identify whether a bug is a validation issue or a database problem?▼

Classify bugs by layer using MCP tooling: Chrome DevTools inspects UI state and client-side validation logic; Supabase tools examine database constraints and query results. Context7 consultation ensures you apply current patterns like `.parse()` vs `.safeParse()` distinctions before implementing fixes.

How do I ensure bug fixes don't introduce regressions in testing?▼

Comprehensive verification enforces unit, integration, and E2E test execution after minimal, surgical code changes. All tests must pass before deployment, and MCP tooling validates performance and security implications remain unaffected.

Can I use this debugging workflow with Zod validation and Chrome DevTools together?▼

Yes. The workflow integrates MCP tools including Chrome DevTools for live state inspection and Supabase for database validation. It consults Context7 for current Zod patterns, identifies mismatches like `.parse()` vs `.safeParse()` usage, and verifies fixes across all test layers.

What happens when a form field validation fails on a settings page—how do I trace it?▼

Use Chrome DevTools to inspect live form state and client validation logic, check database constraints via Supabase tooling, consult Context7 for validation best practices, implement targeted fixes, and run comprehensive unit, integration, and E2E tests to confirm resolution and detect regressions.

Do I need prior knowledge of Clean Architecture layers to use this debugging approach?▼

The workflow guides diagnosis across Validation, Database, UI, E2E, and Authorization layers with structured context-guided steps. MCP tooling integration and mandatory Context7 consultation provide current patterns and best practices, reducing the need for deep prior architecture knowledge.

Related Skills

Explore More Software Engineering Skills→
bostonaholicbostonaholic
8

test-driven-bug-fix

Reproduce, isolate, fix, and verify software defects using test-driven methodology.

Community
Advanced
d-o-hubd-o-hub
11

test-runner

Run Rust unit, integration, and doc tests with cargo test.

Community
Intermediate
JKKN-InstitutionsJKKN-Institutions

advanced-debugging

Diagnose Next.js 15 and Supabase issues across UI, Service, and Database layers.

Official
Intermediate
kubrickcodekubrickcode
1

e2e-ui-fix

Reproduce, analyze, fix, and verify Playwright E2E UI bugs with regression tests.

Community
Advanced