Menu
GitHub pull request review workflow using available GitHub CLI, local git diff, checks, and CI evidence.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Built-in browser automation and E2E verification workflow. Use for Claude /wf-browser, Codex $wf-browser or /skills wf-browser, Browser Use, Playwright, Chrome DevTools/CDP, screenshots, forms, UI verification, and browser-visible acceptance.
Codex compatibility: use $wf-help or /skills wf-help in Codex to show the Harness WF command table. Claude Code and OpenCode use the direct /wf-help command.
Use for /wf-max in Claude Code, $wf-max or /skills wf-max in Codex. WF-MAX is explicit only — the user must type /wf-max, $wf-max, or /skills wf-max.
Use when work needs bounded subagent coordination, parallel read-only exploration, independent review gates, broad context partitioning, or controlled handoffs.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Source-backed CLI invocation guide for Claude Code, Codex, and OpenCode automation. Use when invoking peer CLIs, writing batch tests, collecting cache telemetry, debugging command-line flags, or documenting cross-runtime agent usage for Harness workflows.
| name | github-pr-review |
| description | GitHub pull request review workflow using available GitHub CLI, local git diff, checks, and CI evidence. |
Use this skill when reviewing a GitHub pull request, responding to PR feedback, checking CI status, or summarizing review findings.
Harness/workflows/github-pr-review.mdHarness/PROGRESS.md and current task tasks/<id>/PLAN.mdtasks/<id>/PLAN.md when tracking review work.Return findings first by severity with file and line references, then open questions, tests/checks run, and change summary if edits were made.
Update Harness/tasks/<task-id>/PLAN.md only when the PR review is part of a tracked implementation plan.
Use Harness/specs/runtime/dispatch.md when independent review areas can be assigned separately, such as backend, frontend, and CI.