Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    laravel bug finder

    1

    Systematic Laravel debugger for fixing Eloquent, routing, authentication, and runtime errors.

    Free

    0 installsSecurity scanned
    laravel bug finder

    laravel bug finder

    Example session with this skill installed

    I am getting a '419 Page Expired' error whenever I try to submit my contact form. Here is my Blade file and my route file.

    • Read your context and instructions
    • Compiled the laravel bug finder
    • Generated the UI component

    I have analyzed your contact.blade.php and web.php files. The error is caused by a missing security token required by Laravel's VerifyCsrfToken middleware.

    🐛 Bug Found

    Severity:
    High

    Problem:
    Form submissions are failing with a 419 status code.

    Root Cause:
    The <form> element in resources/views/contact.blade.php is missing the @csrf Blade directive. Laravel requires a CSRF token for all POST, PUT, PATCH, or DELETE requests to protect against cross-site request forgery.

    Affected File:
    resources/views/contact.blade.php

    🔧 Fix

    Insert the @csrf directive inside your form opening tag:

    <!-- resources/views/contact.blade.php -->
<form action="{{ route('contact.submit') }}" method="POST">
    @csrf
    <div class="mb-3">
        <label for="name">Name</label>
        <input type="text" name="name" id="name" class="form-control">
    </div>
    <!-- ... rest of the form ... -->
    <button type="submit">Send Message</button>
</form>

    🧪 Test

    1. Open the /contact page in your browser.
    2. Fill out the name and message fields.
    3. Click the Send Message button.
    4. Expected result: The form submits successfully and redirects to the success page instead of showing the 419 error.

    💡 Why This Happened

    Laravel includes a middleware that automatically verifies that the user making the request is the one who actually rendered the form. By adding @csrf, Laravel generates a hidden input field containing a unique token that the server checks upon submission.

    Next steps

    • Check other forms in your application (e.g., login, registration) for the @csrf tag.
    • Ensure your session.php config has the correct domain set if the error persists.

    laravel-bug-finder.tsx

    TSX · React component

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The problem

    Laravel errors can be cryptic, often masking simple root causes behind generic 500 pages or BindingResolutionExceptions. Manually tracing a bug across routes, controllers, and Blade templates leads to hours of trial-and-error debugging.

    What it does

    • Analyzes exact error messages to isolate the specific failure point in the Laravel lifecycle.
    • Identifies root causes in Eloquent relationships, route parameters, and middleware authorization gates.
    • Detects PHP ParseErrors and syntax issues, specifically identifying misplaced braces or class structures.
    • Scans for security vulnerabilities like unsafe mass assignment, missing CSRF tokens, and unvalidated inputs.
    • Generates targeted fixes with specific code blocks and clear verification steps for manual testing.

    Frameworks & tools

    Laravel (including Eloquent, Blade, and Migrations), PHP, Vite, npm, and Composer.

    Why this beats prompting it yourself

    Generic prompts often result in broad architectural rewrites or hallucinated file paths. This skill follows a strict "Inspect Before Changing" workflow, ensuring solutions are derived from your actual codebase rather than generic best practices.

    Use cases

    • Fixing 'Route [name] not defined' or 'Target class does not exist' errors.
    • Debugging complex Eloquent relationship queries and mass assignment failures.
    • Resolving Vite manifest errors or asset loading issues in frontend components.
    • Auditing controller methods for missing authorization policies or validation gaps.

    Known limitations

    Requires access to the relevant Laravel project files to provide specific line-by-line fixes. Cannot execute database migrations or terminal commands directly.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scanned

    Verified clean today

    • Free to download with an account

    Listedtoday

    Frequently Asked Questions