AI Skill Report Card
Generated Skill
Quick Start
Bash# Run discovery phase pnpm lint > lint.json 2>&1 & pnpm tsc --noEmit > tsc.json 2>&1 & pnpm build > build.json 2>&1 & wait # Parse results and start parallel fixing # (See workflow for full orchestration)
Recommendation▾
Consider adding more specific examples
Workflow
Phase 1: Parallel Discovery
Progress:
- [ ] Spawn ESLint sub-agent: `pnpm lint`
- [ ] Spawn TypeScript sub-agent: `pnpm tsc --noEmit`
- [ ] Spawn Build sub-agent: `pnpm build`
- [ ] Wait for all reports
- [ ] Aggregate JSON arrays of issues
Phase 2: Issue Categorization
Progress:
- [ ] Group issues by file path
- [ ] Count total issues per file
- [ ] Sort files by issue count (descending)
- [ ] Create fix queue
Phase 3: Parallel Fixing (Max 5 concurrent)
Progress:
- [ ] Spawn sub-agent for file 1
- [ ] Spawn sub-agent for file 2
- [ ] Spawn sub-agent for file 3
- [ ] Spawn sub-agent for file 4
- [ ] Spawn sub-agent for file 5
- [ ] As each completes, spawn next file
- [ ] Continue until queue empty
Phase 4: Verification
Progress:
- [ ] Run `pnpm lint` - check remaining
- [ ] Run `pnpm tsc --noEmit` - check remaining
- [ ] Run `pnpm build` - check remaining
- [ ] If issues remain, return to Phase 3
Phase 5: Final Report
Progress:
- [ ] Generate build health summary
- [ ] List fixed vs skipped issues
- [ ] Confirm final build status
Recommendation▾
Include edge cases
Examples
Example 1: ESLint Sub-agent Output
JSON[ { "file": "src/utils/helper.ts", "line": 42, "rule": "no-unused-vars", "message": "'unusedVar' is assigned a value but never used" } ]
Example 2: Fix Queue Prioritization
Fix Queue (by total issues):
1. src/components/App.tsx (12 issues)
2. src/utils/api.ts (8 issues)
3. src/types/index.ts (3 issues)
Example 3: Sub-agent Fix Report
File: src/components/App.tsx
Fixed:
- Removed unused import 'React' (line 1)
- Added missing return type (line 23)
- Fixed no-explicit-any violation (line 45)
Skipped:
- Line 67: Suppressing 'any' would break component props interface
Status: ✓ Passes lint and typecheck
Best Practices
Orchestration:
- Limit concurrent sub-agents to 5 to avoid resource conflicts
- Always wait for discovery phase completion before fixing
- Track file assignments to prevent concurrent edits
- Retry failed sub-agents once before marking manual
Sub-agent Guidelines:
- Work only on assigned files - no cross-file imports/exports
- Fix issues in priority order: build → TypeScript → ESLint
- Preserve functionality - only fix errors, don't refactor
- Verify fixes with local lint/typecheck runs
Error Handling:
- If build fails, prioritize compilation errors first
- Skip issues that would break functionality
- Document why issues were skipped for manual review
Common Pitfalls
Don't:
- Fix files directly as orchestrator - always delegate to sub-agents
- Modify business logic or test files unless they have lint errors
- Use
eslint-disablecomments without strong justification - Change dependencies or add new packages during fixing
- Rush verification - always run full lint/build after parallel fixes
Avoid:
- Starting Phase 3 before Phase 1 is complete
- Running more than 5 sub-agents concurrently
- Skipping the categorization step (leads to inefficient fixing order)
- Assuming first verification pass will be clean (often needs iteration)