wp-ci-qalisted

Use when a pull request has QA failures, a "Testing Failed" label, or QA comments reporting broken features — reading QA feedback and PR comments, tracing root cause using root-cause-patterns.md, applying scoped conventional-commit fixes, swapping labels (Testing Failed to Need Testing), and posting a structured QA re-test comment. Triggers: "QA failed my PR", "Testing Failed label on my PR", "fix the QA comments on PR", "QA says feature X is broken", "post a re-test comment", "how do I respond to QA feedback", "CI is failing on my PR", "QA reopened the ticket", "update the PR label after fixing", "testing failed label", "QA comment says the button is broken", "phpcs failing in CI", "yarn lint error on the PR", "npm run build failing in CI", "root cause of the QA failure", "write a re-test instruction comment", "fix failing checks on this PR", "QA triage workflow", "phpcs prints nothing and exits 0", "composer run test produces no output", "phpstan workers keep crashing", "did my static checks actually run",
mralaminahamed/wp-dev-skills · ★ 27 · Testing & QA · score 77

Install: claude install-skill mralaminahamed/wp-dev-skills

# Fix PR QA Failures > **Model note:** This skill traces non-obvious root causes across PHP, JS, and CI — run on `sonnet` or `opus`. Do not downgrade to `haiku`; cause identification requires reasoning across multiple files. ## When to use - "QA marked my PR as Testing Failed", "fix the bugs in QA comments", "address QA feedback". - "A PR has a 'Testing Failed' label", "QA left comments saying features are broken". - "Trace the root cause of a QA-reported bug and fix it with scoped commits". - "Post a QA re-test comment after fixing the reported issues". **Not for:** Writing new features or fresh code — use `wp-github-flow`. Setting up a CI pipeline from scratch — this skill triages failures in existing CI. ## Overview Full workflow for diagnosing and fixing bugs reported by QA on an open PR. Starts from the GitHub PR URL, ends with labels updated and a QA re-test comment posted. ## Supporting files - `scripts/fetch-pr-context.sh <pr> [owner/repo]` — Step 1 in one command: prints PR metadata, labels, and the full QA comment thread (newest last). - `references/root-cause-patterns.md` — catalog of recurring bug patterns (symptom → cause → detect → fix). **Read before tracing; append after.** - `references/qa-comment-template.md` — the Step 8 re-test comment template + rules. - `references/github-actions-wp-matrix.md` — PHPUnit/PHPCS/PHPStan workflow configs, PHP×WP version matrix, caching, and CI failure triage. ## Workflow ```dot digraph fix_qa { rankdir=TB;