qa

Run a QA review for a Linear issue by executing the /qa command with your issue identifier when it is in In Review status, which analyzes comments and generates a structured checklist to gate merges.

A structured QA review checklist covers SOLID principles, security audit findings, code quality checks, and removal candidates to determine branch merge readiness before transitioning Linear issues.

Yes, you can transition Linear issue states automatically by issuing approval commands that move the issue to Done on approval or back to In Progress when major issues are found during the merge gate review.

Yes, the QA review and merge gate workflow requires the Linear issue to be in the In Review status to properly analyze PR readiness and generate the structured checklist report.

When major blockers are found during the security audit or code review, the Linear issue transitions back to In Progress instead of being approved for a merge, enforcing a remediation loop.

Code review findings determine merge readiness by evaluating SOLID, security, code quality, and removal candidate checklists to decide whether a branch is ready to merge, needs caution, or must be blocked.