Highlights
This patch release folds back lessons from three live QA reviews (NRS-4455, SRVGL-242, NRS-4188) where the skill's own guidance was contradictory or silently broken. The most impactful fix is qa-gather.sh discovery: the script searched for utility/qa-gather.py, but jira-integration 3.13 and later ship utility/jira-qa-gather.py, so one-call discovery always failed on current installs and silently fell back to multi-call mode at roughly four extra tool calls per review. The release also closes a notation contradiction — comment-template.md's own examples still used the (-) token that severity.md warns renders as a red forbidden icon in Jira — and codifies how to write findings the reviewer fixes during the review, so a fixed-in-QA issue neither hides behind a bare pass icon nor skews the verdict as an open should-fix.
Fixed
(off)instead of(-)for n/a findings in the comment-template examples, consistent with the existing severity.md warning (#11)qa-gather.shresolvesjira-qa-gather.py(jira-integration >= 3.13) via deterministicfind -type f -print -quitper candidate name — no| headpipeline, no SIGPIPE risk underset -o pipefail(#11)
Added
- Paired-icon notation for findings the reviewer reports and fixes during the review:
(!) finding — (/) fixed <how> during QA(#12) - Sparse praise icons and an optional 1-5 star rating for verdicts (#12)
- Display-text shorthand for pipeline and job links (#12)
- Sanity-scan items 7-9: escape literal block-markup tags in prose (
\{code\}), link attachments with[^filename], and link every MR/commit/repo named in a finding (#11, #12)
Changed
- F1.5 (description currency) now names the concrete drift artifacts to look for: unticked task checkboxes, outdated status tables, superseded version strings (#13)
Full Changelog: v0.4.0...v0.4.1