QA: Review PR Fix — Autonomous Agents Agentic Workflow

schema_version: 1
id: agent_qa_validate
title: "QA: Review PR Fix"
description: "Review PR code against ticket acceptance criteria — does NOT test live site"
overview: |
  A code-level QA review that checks whether a PR's changes actually satisfy the acceptance criteria on the linked ticket. The agent reads the ticket, then reads the PR diff line-by-line, mapping each requirement to the code that implements it. If something in the criteria has no backing code, that is called out explicitly.

  This workflow never touches a running site — it is a gating step before deploy, not a validation of deployed behaviour. Output is an approval, a request-changes with specific line references, or a block decision with rationale, all posted to the ticket and the PR.

category:
  level: pipeline
  domain: engineering

metadata:
  agent: true
  role: qa

params:
  ticket_url:
    type: string
    description: "Jira ticket URL"
  hint:
    type: string
    default: ""
    description: "Optional extra instructions for the agent"
  entry_path:
    type: string
    default: "~/workspace"
    description: "Working directory for the agent"

steps:
  - type: terminal.open
    title: "Agent: QA Review PR Fix"
    cwd: "{{entry_path}}"
  - type: terminal.run
    cmd: >-
      source ~/.agent-env && claude --dangerously-skip-permissions
      "read ticket with attachments and all comments - {{ticket_url}}. if it fails, stop and report the error.
      learn how to QA relevant parts.
      IMPORTANT — the fix is in a PR branch, NOT deployed to production. do NOT test the live site to verify the fix.
      1. find the PR link in ticket comments.
      2. review the PR diff for correctness against acceptance criteria.
      3. check out the branch locally and build/test if possible.
      4. if not buildable, do a thorough diff review against the ticket requirements.
      5. check edge cases by reviewing code paths changed in the PR.
      you MAY confirm the bug exists on the live site as a baseline, but do NOT expect the fix to be live.
      {{hint}}
      write one comment to the ticket with: pre-fix baseline (optional), PR fix verification, edge case analysis, and verdict (PASS or FAIL)."