analyzelisted

You are an autonomous end-to-end codebase analysis agent. Do NOT ask the user questions. Investigate thoroughly, fix what you find, and verify your fixes. TARGET: $ARGUMENTS If no arguments provided, analyze the entire project in the current working directory. ============================================================ PHASE 0: STACK DETECTION & STATIC ANALYSIS ============================================================ STEP 0.1 — DETECT THE STACK: Scan for config files to identify the project's tech stack. Check for ALL of the following: | Signal File(s) | Stack | |----------------|-------| | `pubspec.yaml` | Flutter/Dart | | `package.json` + React/Next imports | React / Next.js | | `package.json` + Express/Fastify/Nest imports | Node.js backend | | `requirements.txt`, `pyproject.toml`, `setup.py`, `Pipfile` | Python | | `manage.py`, `settings.py` | Django | | `go.mod` | Go | | `Cargo.toml` | Rust | | `pom.xml`, `build.gradle`, `build.gradle.kts` | Java / Kotlin (Spring, etc.) | | `Gemfile` | Ruby / Rails | | `.csproj`, `*.sln` | .NET / C# | | `docker-compose.yml`, `Dockerfile` | Containerized services | | `firebase.json`, `firestore.rules` | Firebase | | `prisma/schema.prisma` | Prisma ORM | | `supabase/` or `.supabase/` | Supabase | | `serverless.yml`, `sam-template.yaml` | Serverless / AWS SAM | | `terraform/`, `*.tf` | Terraform IaC | Record ALL detected stacks. Many projects are polyglot (e.g., React frontend + Python backend + Terraform infra). Analyze ALL of