Troubleshooting backend

Skill ceilidhboy/skills/skills/troubleshooting-backend

Agent skills for Laravel and PHP development. Installable via npx skills@latest add ceilidhboy/skills

Install

npx -y skills add ceilidhboy/skills --skill troubleshooting-backend

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Troubleshooting Laravel, PHP, and backend-related errors.

SKILL.md

2.5 KB, 531 tokens by cl100k_base, as published. Nobody here has run it

Troubleshooting Backend Issues

When to Activate This Skill

Activate this skill when encountering:

Laravel framework errors or exceptions
PHP errors or type errors
Database connection or query errors
Route registration issues
Controller or action problems
Artisan command failures
Type generation failures (PHP → TypeScript)

Common Backend Issues and Solutions

Route Registration Issues

Problem: Wayfinder action file not generated, import fails Cause: Route not registered in routes/web.php Solution:

Check routes/web.php for the route registration
Verify the controller class name matches
Run php artisan wayfinder:generate --no-interaction
Verify the file exists in resources/js/actions/

See the routing-and-controllers skill for detailed workflow.

Type Generation Failures

Problem: TypeScript types not updating after PHP changes Cause: php artisan typescript:transform not run Solution:

php artisan typescript:transform

Then regenerate Wayfinder:

php artisan wayfinder:generate --no-interaction

Artisan Command Failures

Problem: Artisan commands fail or hang Cause: Configuration cache or stale files Solution:

php artisan config:clear
php artisan cache:clear
php artisan view:clear

Then retry the command.

Database Errors

Problem: Database connection fails or queries error Cause: Environment variables, migrations not run, or schema issues Solution:

Check .env file for correct database credentials
Run php artisan migrate if migrations pending
Check database schema with php artisan tinker and query directly

PHP Type Errors

Problem: Static analysis or runtime type errors Cause: Missing type hints or incorrect types Solution:

Run composer fix to check Larastan analysis
Add proper type hints to methods and properties
Check the error message for the exact location and fix

Diagnostic Commands

# Check configuration
php artisan config:show

# Run static analysis
vendor/bin/phpstan analyse

# Check routes
php artisan route:list

# Test database connection
php artisan tinker

When to Activate Other Skills

Frontend errors appearing: Activate troubleshooting-frontend
Routing/controller questions: Activate routing-and-controllers
Testing failures: Activate pest-testing

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most debug triage skills give in 531 tokens

Counted across 839 of the 1,149 authors here whose files we hold, read 2026-08-07

Investigate root cause before proposing any fixin 102 of 839, across 67 files
Read error messages completelyin 89 of 839, across 49 files
Create a failing test case before fixingin 84 of 839, across 46 files
Reproduce the issue consistentlyin 82 of 839, across 41 files
Change one variable at a timein 82 of 839, across 42 files
Check recent changesin 74 of 839, across 36 files
Write the regression test before fixingin 74 of 839, across 40 files
Fix the root cause not the symptomin 60 of 839, across 45 files
Implement a single fix at a timein 59 of 839, across 20 files
Trace data flow backward to the sourcein 50 of 839, across 20 files
Remove all debug instrumentationin 49 of 839, across 13 files
Form a single hypothesisin 48 of 839, across 18 files

Said here and by no other author read

check routes file for the route registration
verify the controller class name matches
verify generated files exist
check environment file for correct database credentials
run pending migrations
add proper type hints to methods and properties

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.