Agent Reference
Echo — QA Agent
Echo is the QA engineer agent. It writes tests, validates builds, and catches regressions.
Echo — QA Agent
Echo is your QA engineer. It specializes in testing, build validation, and quality assurance across your entire codebase.
Capabilities
- Test writing — Creates unit tests, integration tests, and end-to-end tests
- Build validation — Runs builds after changes to catch compilation errors
- Regression detection — Monitors test suites for failures after other agents' commits
- Coverage analysis — Identifies untested code paths and adds coverage
Default boundaries
| Access | Paths |
|---|---|
| Can modify | tests/, __tests__/, test config files |
| Can read | All project files (for test writing) |
| Cannot modify | Source code (reports issues instead) |
Example output
[10:30] Echo reported: "All 14 tests passing"
[10:45] Echo committed: "test: add auth middleware unit tests" (1 file)
- tests/lib/auth/middleware.test.ts (new)
[11:00] Echo warning: "Build failed after Alex's commit a1b2c3d"
How Echo works
Echo follows a unique pattern compared to other agents:
- Monitor — After each commit from Alex or Pixel, Echo runs the test suite
- Report — If tests fail, Echo logs a warning and notifies the team
- Write — Echo identifies untested code and writes new tests
- Validate — Echo runs a full build to ensure everything compiles
Echo never modifies source code directly. If it finds a bug, it reports it as an issue for Alex or Pixel to fix.
Tools
Echo has access to:
- Test runners (Vitest, Jest, Playwright)
- Build tools (Next.js build, TypeScript compiler)
- Code coverage tools (c8, istanbul)
- Git operations (within safeguard rules)
Configuration
# Echo (QA)
## Focus Areas
- Unit test coverage for new code
- Integration tests for API routes
- Build validation after every commit
## Thresholds
- Minimum test coverage: 80%
- Maximum build time: 5 minutes
- Fail-fast on type errors: true