AI-Powered Laravel Pre-Commit Review: route:list, Staged Diff & Custom Prompts

This guide demonstrates how to integrate AI into the Laravel pre-commit review workflow. Instead of having AI write code, the approach uses AI as a reviewer that examines staged changes against the project's routes, environment, and diff to spot common gaps.

Preparation

Run the script from the Laravel project root after staging your changes with git add. If no changes are staged, the diff will be empty and the review will have little value.

Operation Steps

Export Laravel environment summary ( php artisan about).

Export the route table ( php artisan route:list).

Export the staged diff ( git diff --staged).

Generate an AI review prompt that includes the collected files and a checklist.

Laravel AI Review Package Generation Script

#!/usr/bin/env bash
set -euo pipefail
mkdir -p .ai-review
php artisan about > .ai-review/laravel-about.txt
php artisan route:list > .ai-review/routes.txt
git diff --staged > .ai-review/staged.diff
cat > .ai-review/prompt.md <<'EOF'
You are a Laravel code review assistant.
Based on laravel-about.txt, routes.txt, and staged.diff, check:
1. Whether routes lack authentication
2. Whether form requests lack validation
3. Whether database writes need transactions
4. Whether queue jobs are retryable
5. Whether cache keys might conflict
6. Whether FeatureTests are missing
Only output risk points, impact scope, and modification suggestions.
EOF
echo "Generated .ai-review/ review materials"

How to Use the Generated Results

Send the four files — .ai-review/laravel-about.txt, .ai-review/routes.txt, .ai-review/staged.diff, and .ai-review/prompt.md — to an AI model. The AI will follow the checklist and output risk points.

Acceptance Criteria

The AI's output must not be taken as final. Developers must manually verify at least three items: whether authentication is truly missing, whether a transaction is truly required, and whether test coverage already exists. Only after confirmation should code be modified.