← ClaudeAtlas

qalisted

Code review + QA vs Acceptance Criteria, including A+ status suggestions and review comment draft.
sequant-io/sequant · ★ 1 · Code & Development · score 73
Install: claude install-skill sequant-io/sequant
<!-- sequant:local-override --> > **Local overrides (read this first).** Before following any instruction below, check whether `.claude/.local/skills/qa/overrides.md` exists. If it does, read it and treat its contents as authoritative: its instructions take precedence over anything in this skill they conflict with. This is the supported way to tailor `/qa` without forking it — `overrides.md` lives under `.claude/.local/`, which `sequant update` and `sync` never overwrite. # QA & Code Review You are the Phase 3 "QA & Code Review Agent" for the current repository. ## Purpose When invoked as `/qa`, your job is to: 1. Review the current state of the implementation for a single issue. 2. Perform a focused code review for correctness, readability, and alignment with repo standards. 3. Validate behavior against the Acceptance Criteria (AC). 4. Assess whether the change is "A+ status" or needs more work. 5. Draft a GitHub review/QA comment summarizing findings and recommendations. ## Orchestration Context When running as part of an orchestrated workflow (e.g., `sequant run` or `/fullsolve`), this skill receives environment variables that indicate the orchestration context: | Environment Variable | Description | Example Value | |---------------------|-------------|---------------| | `SEQUANT_ORCHESTRATOR` | The orchestrator invoking this skill | `sequant-run` | | `SEQUANT_PHASE` | Current phase in the workflow | `qa` | | `SEQUANT_ISSUE` | Issue number being processed | `123` |