npx agentspec-cli install 04acc213-fa5a-410b-8b32-18a9c273044a --framework ClaudeCode→ .claude/skills/qa/SKILL.md
# QA Standalone QA run for any PR. Boots the local environment, validates every acceptance criterion, and produces a test report. Posting to GitHub is your choice — you are prompted at the end. ## Step 1 — Config This skill targets `wp-media/wp-rocket`. Specs live at `.TemporaryItems/Issues/wp-rocket/issues/<N>-spec.md`. ## Step 2 — Resolve the PR Use `$ARGUMENTS` as the PR number or URL. If empty, resolve from the current branch: ```bash gh pr list --head "$(git branch --show-current)" --json number,url -q '.[0] | "\(.number) \(.url)"' ``` If no PR is found, tell the user and stop. Get the base branch: ```bash gh pr view <PR_NUMBER> --json baseRefName -q .baseRefName ``` ## Step 3 — Invoke the qa-engineer agent Invoke the `qa-engineer` sub-agent with: - PR number and PR URL - Base branch from Step 2 - Repo: `wp-media/wp-rocket` > **STANDALONE MODE** — two differences from the normal pipeline run: > 1. **Skip the PR-comment posting step.** Instead, output the full QA report as > formatted Markdown in your response, in a section titled `## QA Report`. Use the same > format the pipeline would post (including the `<!-- ai-pipeline:qa-report -->` marker). > 2. **Skip the StructuredOutput JSON return.** Output a short human-readable summary > instead: overall result, pass/fail per criterion, and any blockers. All other steps run normally — the local environment is booted, acceptance criteria are tested, and the full validation is performed. ## Step 4 — Offer to post After the agent responds, display its `## QA Report` and ask: > **Post this QA report to PR #\<PR_NUMBER\>?** > Reply `yes` to post, `no` to finish here. **If yes** — post with dedup: check for an existing `<!-- ai-pipeline:qa-report -->` comment, update it with `gh api --method PATCH repos/wp-media/wp-rocket/issues/comments/$EXISTING_ID` if found, otherwise create a new comment. **If no** — confirm the QA run is complete and finish.
Built on the Agent Skills standard
pr
Create a pull request with full validation. Use when ready to submit work for review.
by AgentHub Crawler
qa
Run the E2E QA test suite against the live application using Playwright MCP and nREPL. Use when testing the app end-to-end.
by AgentHub Crawler
pr
Create a pull request
by AgentHub Crawler
Sign in to leave a comment.
pr
Use when the user wants to open a pull request or finish a branch handoff. Read the PR template, inspect changes vs main, run the release skill first if the branch name looks like a version, validate the branch with the shared repo checks, open a draft PR targeting main, and return the preview deployment URL when one applies.
by AgentHub Crawler