laravel-debugging-prompts

Generate structured Laravel debugging prompts with error messages and stack traces.

Updated Jun 8, 2025
One-click install
npx skills add https://github.com/noartem/kawa --skill laravel-debugging-prompts-noartem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: laravel-debugging-prompts
Source: https://github.com/noartem/kawa/tree/main/ui/.ai/skills/laravel-debugging-prompts
Command: npx skills add https://github.com/noartem/kawa --skill laravel-debugging-prompts-noartem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Laravel debugging can be hindered by incomplete error reports. This Skill helps generate structured prompts that collect error messages, stack traces, context, and attempted solutions to guide AI in diagnosing Laravel issues.

Core Features & Use Cases

  • Structured prompts: capture error messages, stack traces, and environment details.
  • Context enrichment: include relevant code snippets and reproduction steps.
  • Use Case: when facing a QueryException or foreign key constraint failure, the AI has actionable data to propose fixes.

Quick Start

Provide a complete Laravel error, including stack trace and context, to generate a focused debugging prompt.

Frequently Asked Questions about laravel-debugging-prompts

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

FAQPage Schema
How do I write a prompt for AI-assisted Laravel debugging?

A Laravel debugging prompt should capture error messages, stack traces, environment details, and reproduction steps to give the AI actionable data for diagnosing controllers, models, and database interactions.

What should I include in an AI prompt for a Laravel QueryException?

For a Laravel QueryException, include the full error message, stack trace, relevant code snippets, reproduction steps, and attempted solutions to provide the AI with actionable diagnostic data.

Can I use structured prompts to fix Laravel foreign key constraint failures?

Yes, structured prompts capture the constraint failure error message, stack trace, and database context, providing the AI with actionable data to propose fixes for foreign key issues.

Does this approach work for debugging Laravel controller and model errors?

Yes, this approach applies a structured template to capture error details, stack traces, and reproduction steps for typical Laravel errors across controllers, models, and database interactions during development and QA.

Why does my AI assistant fail to fix Laravel stack trace errors?

AI assistants fail to fix Laravel stack trace errors when prompts lack complete error details, environment context, or reproduction steps, resulting in insufficient data to propose actionable fixes.