Review a PR by comparing the Jira ticket requirements against the actual implementation. Only use when working in a project whose path contains "kontrakcja".
Review a pull request by comparing what the Jira ticket requires against what was actually implemented.
Fetch the Jira ticket by invoking the /jira skill (no arguments — let it auto-detect from the current bookmark). Read and internalize the ticket summary, description, acceptance criteria, and any relevant comments.
Determine the PR:
$ARGUMENTS is provided, use it as the PR number.jj log -r 'latest(bookmarks() & ancestors(@) & ~ancestors(trunk()))' --no-graph -T 'bookmarks'
gh pr view to resolve the PR number.Fetch the PR diff and metadata:
gh pr view <PR> --json number,title,body,baseRefName,headRefName,url
gh pr diff <PR>
Read the changed files to understand the full implementation context. Don't rely solely on the diff — read the complete files (or relevant sections) when needed to understand the change in context.
Compare requirements vs implementation and present a structured review:
Keep the review concise and actionable. Focus on whether the PR fulfills the ticket, not on style nitpicks.