project-debug

Diagnoses and iteratively fixes failing tests and runtime errors in built projects.

1|9|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/agenticgogol/Edureka_Coding_Agent_Enabled_Demo_11Jul --skill project-debug-agenticgogol
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-debug
Source: https://github.com/agenticgogol/Edureka_Coding_Agent_Enabled_Demo_11Jul/tree/main/.claude/skills/project-debug
Command: npx skills add https://github.com/agenticgogol/Edureka_Coding_Agent_Enabled_Demo_11Jul --skill project-debug-agenticgogol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a project's tests fail, an end-to-end verification request breaks, or a user reports a bug in an already-built app, this Skill keeps debugging until the failing behavior actually works instead of stopping after reporting the error once. ## Core Features & Use Cases - Reproduce-first debugging: Always re-runs the failing test, endpoint, or user flow to capture the real traceback before editing any code. - Structured diagnosis: Checks cheapest causes first, including missing dependencies, API contract drift between frontend and backend, framework API mismatches (CrewAI, DSPy, MCP, GraphRAG), stale environments, and missing data files. - One-hypothesis iteration: Changes one thing at a time and re-runs the reproduction immediately, repeating until the failure is resolved or the user must decide something. - Use Case: A full-stack app's test suite fails after a backend route change; the Skill diffs the frontend call against the API contract in design.md, fixes the deviating side, and re-runs the full test gate plus end-to-end verification. ## Quick Start Ask the agent to debug the failing test in the current project and keep iterating until the test suite and end-to-end verification pass.

Frequently Asked Questions about project-debug

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

FAQPage Schema
How do I debug a failing test in an AI-built project?▼

Reproduce the failure first by running the exact failing test or endpoint and capturing the real traceback. Then diagnose cheapest causes first, fix one hypothesis at a time, and re-run the reproduction after each change until it passes.

How to fix frontend and backend API contract mismatches?▼

Diff the frontend request against the backend route and response model defined in design.md's API contract section. Fix whichever side deviated from the agreed contract rather than assuming one side is correct.

What should I check when CrewAI, DSPy, or MCP code breaks?▼

Run a research-first pass and check the framework's current documentation before guessing a fix, since these APIs change frequently. Avoid trial-and-error edits against an API whose behavior you have not verified.

Why does debugging stop when an API key is missing or expired?▼

A missing, expired, or rate-limited provider key is a hard stop, not a bug to code around, because there is no mock mode. The user must fix the named key and re-run the require-api-key check before debugging continues.

When should a debugging session stop and ask the user?▼

Stop when the fix requires a decision only the user can make, such as a missing key or ambiguous expected behavior, or when several genuinely different hypotheses produce no change in the error. Report what was tried, the current error, and what is needed to unblock.