Adversarially review a grooming spec before implementation starts. Finds hidden risks, unvalidated assumptions, and missing dependencies. Standalone entry point for the challenger agent.
中文简介正在准备中。当前显示原文说明。
wp-media/wp-rocket7672026年10月17日 更新
免费在 GitHub 公开
qa
Run QA validation on a pull request — boots the local environment, tests acceptance criteria, and optionally posts the report as a PR comment. Standalone entry point for the qa-engineer agent.
中文简介正在准备中。当前显示原文说明。
集成工具GitHub
查看安装方法包含的文件（1）
- SKILL.md2.2 KB
SKILL.md（原文）
安装前可以查看交给 AI 代理的指令内容。
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:
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:
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:
- 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).- 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
yesto post,noto 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.
评价
还没有评价。欢迎分享你的使用感受。
评论
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
同一仓库的技能
Check a change against WordPress.org plugin rules and PHPCS standards.
中文简介正在准备中。当前显示原文说明。
wp-media/wp-rocket7672026年10月17日 更新
docs
免费Update developer-facing documentation to reflect code changes on the current branch. Runs as an inline skill inside backend-agent and frontend-agent (step 2.5 of the internal sequence) after implementation and before DOD. Receives the explicit list of changed files from the implementation agent. No-op if no public API changes occurred.
中文简介正在准备中。当前显示原文说明。
wp-media/wp-rocket7672026年10月17日 更新
dod
免费Run the Definition of Done checklist for the current wp-rocket branch and report PASS/WARN/FAIL with evidence. Two modes: layer 1 (self-correction inside backend-agent / frontend-agent — resolves FAILs before handoff) and layer 2 (independent orchestrator gate — fresh perspective after handoff). Pass layer: "1" or layer: "2" when invoking.
中文简介正在准备中。当前显示原文说明。
wp-media/wp-rocket7672026年10月17日 更新
e2e
免费Run a basic E2E behavioral probe — one primary scenario smoke test for the grooming step.
中文简介正在准备中。当前显示原文说明。
wp-media/wp-rocket7672026年10月17日 更新
groom
免费Groom a single GitHub issue — produce an implementation spec and optionally post the grooming summary as a GitHub comment. Standalone entry point for the grooming-agent.
中文简介正在准备中。当前显示原文说明。
wp-media/wp-rocket7672026年10月17日 更新