skills.rest
jdeweedata
jdeweedataCOMMUNITY
Explore all skills by this author →
GitHub

Bug Fixing Assistant

Diagnose and fix bugs in the CircleTel codebase using a five-phase debugging workflow.

1|Updated May 5, 2025
Search Tags:#workflow#debugging#validation#root-cause#bug-fixing#CircleTel
One-click install
npx skills add https://github.com/jdeweedata/circletel --skill bug-fixing-assistant
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Bug Fixing Assistant
Source: https://github.com/jdeweedata/circletel/tree/main/.claude/skills/bug-fixing
Command: npx skills add https://github.com/jdeweedata/circletel --skill bug-fixing-assistant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Bug Fixing Assistant guides engineers through a disciplined, end-to-end debugging workflow to rapidly identify, reproduce, and resolve issues in the CircleTel codebase. It reduces guesswork, accelerates root-cause analysis, and standardizes how fixes are proposed and validated.

Core Features & Use Cases

  • Systematic debugging workflow: a five-phase process (Understand, Investigate, Analyze, Fix, Validate) to pinpoint root causes and document decisions.
  • CircleTel-specific patterns: reference patterns for common issues like API errors, Next.js 15 params, RLS policies, and memory heap considerations.
  • Templates & checklists: ready-to-use prompts, templates for different bug types, and comprehensive validation checklists to ensure quality.
  • Knowledge reuse: examples from production bugs and a living knowledge base to accelerate future debugging sessions.

Quick Start

  1. Identify bug type based on symptoms (runtime error, infinite loading, API error, or performance issue).
  2. Choose the appropriate prompt template from templates/prompt_templates.md and fill in relevant details.
  3. Follow the 5-phase workflow to reproduce, analyze, propose a fix, and validate results.

Frequently Asked Questions about Bug Fixing Assistant

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

FAQPage Schema
What is a systematic debugging workflow for fixing bugs in a CircleTel codebase?▼

A systematic debugging workflow guides you through five phases—Understand, Investigate, Analyze, Fix, and Validate—to pinpoint root causes and document decisions for CircleTel bug fixing. It reduces guesswork and standardizes how fixes are proposed.

How do I debug Next.js 15 params and API errors in a CircleTel application?▼

To debug Next.js 15 params and API errors, identify the bug type based on symptoms, choose a prompt template, and follow the disciplined workflow to reproduce and isolate the issue. The assistant provides CircleTel-specific patterns for common API and Next.js errors.

What's the best way to reproduce and isolate database RLS policy issues?▼

The best way to reproduce and isolate RLS policy issues is applying the systematic debugging workflow to analyze root causes and validate fixes with tests. The assistant references CircleTel-specific patterns for common RLS policy problems.

Does this bug fixing approach work for frontend, API, and database issues?▼

Yes, this bug fixing approach works across frontend, API, and database issues. It applies a disciplined, reproducible debugging workflow to reproduce, isolate, analyze root causes, and validate fixes with tests across the entire CircleTel stack.

How do I validate bug fixes and document decisions to ensure long-term reliability?▼

You validate bug fixes using comprehensive validation checklists and document decisions by recording traces and verification steps. This ensures long-term reliability by proposing minimal, CircleTel-aligned changes and contributing to a living knowledge base.

Why does my CircleTel application experience memory heap issues and infinite loading?▼

Memory heap issues and infinite loading are common bug types addressed by identifying symptoms and applying the debugging workflow. The assistant provides specific CircleTel memory heap considerations and performance issue templates to investigate and resolve them.

Related Skills

Explore More Software Engineering Skills→
tsenseitsensei
3

investigate

Guide structured four-phase root-cause debugging for software issues.

Community
Advanced
FrogAiFrogAi
1

release-checklist-builder

Generate phase-aware release readiness checklists with verification commands in Markdown and JSON.

Community
Advanced
Globaly-IncGlobaly-Inc

gh-implementation-plan

Convert approved architecture specifications into layer-by-layer implementation plans.

Official
Advanced
adolfoaranaes12adolfoaranaes12
2

fix-issue

Reproduce bugs, identify root causes, and validate minimal fixes with the full test suite.

Community
Advanced