harness-frontend-races-reviewer

Role

Activate when the TypeScript-strict reviewer is active AND the diff contains an async-UI signal (.tsx, useEffect, useState, setTimeout, setInterval, addEventListener, data-controller= for Stimulus). Hunt for lifecycle cleanup gaps (listeners and timers outliving the owner), hook-timing mistakes (state in the wrong hook, async after unmount), concurrent-interaction bugs (overlapping clicks/requests, impossible-state booleans), and promise/timer flows that leave stale work behind. Emit ReviewFinding[] with domain: 'bug', subagent: 'frontend-races', and numeric confidence per the shared confidence rubric.

Skills

• harness-code-review

Steps

1. Execute harness-code-review skill (manual)
2. Execute harness-code-review skill (on_pr)

Methodology

Harness Code Review

Multi-phase code review pipeline — mechanical checks, graph-scoped context, parallel review agents, cross-agent deduplication, and structured output with technical rigor over social performance.

When to Use

• When performing a code review (manual invocation or triggered by on_pr / on_review)
• When requesting a review of completed work (see Role A at the end of this document)
• When responding to review feedback (see Role C at the end of this document)
• NOT for in-progress work (complete the feature first)
• NOT for rubber-stamping (if you cannot find issues, look harder or state confidence level)
• NOT for style-only feedback (leave that to linters and mechanical checks)

Argument Resolution

When invoked by autopilot (or with explicit arguments), resolve paths before starting:

1. Session slug: If session-slug argument provided, set {sessionDir} = .harness/sessions/<session-slug>/. Pass to gather_context({ session: "<session-slug>" }). All handoff writes go to {sessionDir}/handoff.json.
2. Commit range: If commit-range argument provided (e.g., abc123..HEAD), use as diff scope in Phase 2 MECHANICAL and Phase 7 OUTPUT. Otherwise, auto-detect from git environment.