gaia-review-perf

To identify performance bottlenecks during a code review, analyze changed files for memory, bundle impact, and caching decisions. This process flags performance regressions and routes findings for deep analysis to generate optimization decisions.

Profiling integration works by analyzing story artifacts containing changed files. It evaluates these files for performance bottlenecks and routes the findings to a performance subagent to generate a machine-readable performance verdict.

Yes, you can automate a PASSED or FAILED verdict for performance regression checks. The system evaluates performance-relevant files and automatically updates the Review Gate with the corresponding machine-readable performance verdict.

Triggering an automated performance review requires changed files located under docs/implementation-artifacts. Providing a story key initiates the review, ensuring only performance-relevant files are analyzed for bottlenecks.

No, the performance review does not analyze all changed files. It ensures only performance-relevant files are analyzed, filtering the changed files under docs/implementation-artifacts to accurately identify actual bottlenecks.