timothymeadows/post-pr-qa
skills/post-pr-qa/SKILL.md
Run task QA immediately after a confirmed PR is available, then post pass/fail evidence to the PR with inline screenshot references.
$ install --global
skillsauthnpx skillsauth add timothymeadows/opencaw post-pr-qaInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 15, 2026, 4:04 AM89.6s1 file scanned
SKILL.md
- name:
- post-pr-qa
- description:
- Run task QA immediately after a confirmed PR is available, then post pass/fail evidence to the PR with inline screenshot references.
When to use
Use after the human has approved PR creation and the PR number or URL has been confirmed as available.
Output
- QA commands run and pass/fail outcome
- generated report paths
- GitHub PR comment with QA evidence
- inline screenshot URLs in the PR comment when screenshots are part of the evidence
- final user notification that the PR is ready and the agent can move to the next task
Notes
- Confirm the PR exists first using this GitHub tool priority:
gh pr view, then an availablegithubCLI/wrapper, then GitHub MCP/app connector metadata only when both CLI options are unavailable or unsuitable. - Start QA immediately after PR availability is confirmed; do not wait for another user prompt.
- Choose the narrowest meaningful QA first, then broaden when risk or repository conventions require it.
- For browser/UI work, generate non-interactive evidence reports and include screenshot URLs in the PR comment.
- Local screenshot file paths do not render inline on GitHub. Upload screenshots or use CI/repository-hosted URLs before posting inline evidence.
- Mirror or link QA evidence to the task issue when a linked issue exists, but the PR comment is the primary post-PR signal.
- Post the PR QA comment through the same GitHub tool priority:
ghfirst,githubCLI/wrapper second, GitHub MCP/app connector last. - After QA is complete, tell the user whether QA passed or failed, that the PR is ready for review, and that you can continue to the next task if any remain.
Command
../commands/comment-pr-qa-results.sh "<pr_number_or_url>" "<results_summary_file>" [screenshot_or_artifact ...]
Related Skills
timothymeadows/orchestrate-subagents
tools
VerifiedTrustedCommunity
Plan and coordinate parallel subagent lanes using OpenCaw roles, durable task artifacts, and tool-specific execution guidance.
4SKILL.mdUpdated Jun 5, 2026
timothymeadows/goal-flow
development
VerifiedTrustedCommunity
Manage explicitly requested OpenCaw goals as automated multi-task delivery flows with automatic per-task PR creation and required post-PR QA.
2SKILL.mdUpdated May 17, 2026
timothymeadows/pr-readiness-gate
tools
VerifiedTrustedCommunity
Stop before pushing or opening a pull request, summarize readiness, and ask the human to confirm they are ready for PR creation.
2SKILL.mdUpdated May 15, 2026
timothymeadows/playwright-test-refinement
development
VerifiedTrustedCommunity
Refine, rerun, and stabilize Playwright tests using prior failures, traces, screenshots, and source-controlled test code.
2SKILL.mdUpdated May 15, 2026