What problem does it solve? Coordinating code review across a multi-issue Jira workflow is tedious: reviewers must find the right PRs for each issue, check them against consistent criteria, record verdicts in both GitHub and Jira, and keep issue statuses in sync. This Skill automates that review pass from the current git worktree, deriving the issue from the branch name and walking the correct PR set. ## Core Features & Use Cases - Worktree-scoped PR discovery: Derives the Jira issue from the current branch, then reviews the parent PR, every in-review sub-task PR, or a single sub-task PR depending on where you run it. - Structured verdicts with idempotency: Evaluates diffs against six review dimensions (correctness, pattern consistency, scope creep, regressions, test coverage, build hygiene) and posts a canonical review report as a GitHub comment and Jira comment, skipping PRs already approved by the same identity. - Workflow gating via Jira transitions: Sends rejected issues back to In Progress, continues past rejections to report full state, and never merges — it ends by offering to move approved issues to Done. - Use Case: After sub-task executors open PRs against a parent feature branch, run this Skill from the parent's worktree to review each in-review PR, post verdicts, and get a single run-level report on the parent Jira issue. ## Quick Start Run the jira-task-reviewer skill from the issue's git worktree to review its open pull requests and post verdicts to GitHub and Jira.
