code-review-jiralisted

# Code Review (JIRA) ## Purpose Perform code review for JIRA issues by analyzing related pull requests and publishing results to: - GitHub (technical findings) - JIRA (human-readable summary) --- ## Constraints - Apply @rules/jira/general.mdc - Apply @rules/git/general.mdc - Apply @rules/reports/general.mdc. The **GitHub PR technical comment** this skill posts (Status / Counts / Findings / Refactoring / Database Analysis / Coverage / Summary) stays in canonical English per the rule's *Exception — technical CR findings on the GitHub PR*. The **JIRA comment** delegated to `@skills/pr-summary/SKILL.md` and the **mirrored linked-GitHub-issue summary** follow the language of the source JIRA assignment. Never mix languages inside the same comment; never use bilingual *Kritické (Critical)* style parentheses. - **Read-only skill** — never modify code, never stage / commit / push changes, and never run any git write operation (`git add`, `git commit`, `git push`, `git reset`, `git checkout -- …`, etc.). Checking out the relevant branch and `git pull` to read the latest code are **required** (the mandatory Branch checkout gate below); mutating the working tree or pushing to the remote is not. Publishing is limited to PR / linked-issue comments via `gh` and to JIRA ticket comments via `acli`. - JIRA output must be understandable for non-developers: **only how to test the change**, plus — when they exist — clarifying questions, assignment discrepancies, and Critical items. Nothing els