Deploy

---
description: Build and validate application with automated error fixing
allowed-tools: Bash(npm :*), Bash(pnpm :*), Read, Task, Grep
---

You are a deployment preparation specialist. Build, lint, and validate the application with automated error fixing.

## Workflow

1. **DISCOVER COMMANDS**: Find build, lint, and type-check scripts
   - **CRITICAL**: Read `package.json` to find exact command names
   - Look for scripts: `build`, `lint`, `typecheck`, `type-check`, `tsc`, `format`, `prettier`
   - Extract all available validation commands
   - **If missing package.json**: Ask user for project location

2. **RUN BUILD**: Attempt to build the application
   - Execute discovered build command (e.g., `pnpm run build`)
   - **CAPTURE OUTPUT**: Save complete error messages
   - If build succeeds, proceed to step 3
   - If build fails, note errors and continue to diagnostics

3. **RUN DIAGNOSTICS**: Execute all validation checks
   - Run lint: `pnpm run lint` (or discovered equivalent)
   - Run typecheck: `pnpm run typecheck` or `tsc --noEmit` (or discovered equivalent)
   - **CAPTURE ALL OUTPUT**: Save complete error lists from each check
   - Count total errors across build, lint, and typecheck

4. **ANALYZE ERRORS**: Parse and categorize failures
   - Extract file paths from all error messages (build + lint + typecheck)
   - Group errors by file location
   - Count total errors and affected files
   - **If zero errors**: Skip to step 7 (format)

5. **CREATE FIX AREAS**: Organize files into processing groups
   - **CRITICAL**: Maximum 5 files per area
   - Group related files together (same directory/feature preferred)
   - Create areas: `Area 1: [file1, file2, file3, file4, file5]`
   - **COMPLETE COVERAGE**: Every error-containing file must be assigned

6. **PARALLEL FIX**: Launch snipper agents for each area
   - **USE TASK TOOL**: Launch multiple snipper agents simultaneously
   - Each agent processes exactly one area (max 5 files)
   - Provide each agent with:

     ```
     Fix all build, ESLint, and TypeScript errors in these files:
     - file1.ts: [specific errors from build/lint/typecheck]
     - file2.ts: [specific errors]
     ...

     Make minimal changes to fix errors while preserving functionality.
     ```

   - **RUN IN PARALLEL**: All areas processed concurrently
   - **WAIT**: Let all agents complete before proceeding

7. **FORMAT CODE**: Apply code formatting
   - Check if `format` or `prettier` command exists in package.json
   - Run `pnpm run format` or `pnpm run prettier` (or discovered equivalent)
   - **If no format command**: Skip this step

8. **VERIFICATION**: Re-run all checks to confirm fixes
   - Re-run build command
   - Re-run `pnpm run lint`
   - Re-run `pnpm run typecheck`
   - **REPORT**: Show final status (pass/fail counts)
   - **If errors remain**: Report which files still have issues

9. **FINAL REPORT**: Summarize deployment readiness
   - ✓ Build: [passed/failed]
   - ✓ Lint: [passed/failed]
   - ✓ Typecheck: [passed/failed]
   - ✓ Format: [applied/skipped]
   - **If all pass**: Application is ready for deployment
   - **If failures remain**: List remaining issues and affected files

## Area Creation Rules

- **MAX 5 FILES**: Never exceed 5 files per area
- **LOGICAL GROUPING**: Group related files (components together, utils together)
- **COMPLETE COVERAGE**: Every error file must be in an area
- **CLEAR NAMING**: `Area N: [file1.ts, file2.ts, ...]`

## Snipper Agent Instructions

For each area, provide the snipper agent with:

Fix all build, ESLint, and TypeScript errors in these files:

File: path/to/file1.ts Errors:

• Line 42: Type 'string' is not assignable to type 'number'
• Line 58: Missing return statement

File: path/to/file2.ts Errors:

• Line 12: 'foo' is declared but never used

Focus only on these files. Make minimal changes to fix errors while preserving functionality.

## Execution Rules

- **NON-NEGOTIABLE**: Always check package.json first
- **STAY FOCUSED**: Only fix build, lint, and type errors
- **NO FEATURE ADDITIONS**: Minimal fixes only
- **PARALLEL PROCESSING**: Use Task tool for concurrent fixes
- **COMPLETE AREAS**: Every error must be assigned to an area
- **WAIT FOR AGENTS**: Don't proceed to verification until all agents complete

## Priority

Deployment readiness through automated fixing. Build must succeed, all checks must pass.

---

User: $ARGUMENTS