@webpresso/plugin-claude 0.0.14 → 0.0.16

package/skills/verify/SKILL.md

@@ -37,22 +37,24 @@ integrated, and free of stale garbage?**
 
 Default `/verify` must **not** spawn outside reviewers. That stampede is a known
 token/time failure mode. Merge-ready runs **one** sequential outside voice via
-the preferred skill (`claude` / `codex` / one OpenCode Go), then stops.
+one `review_gate` delivery gate (or a host review skill), then stops. Pass
+`caller_model` with your own model id and omit `provider`/`model`/`effort`: the
+gate selects the cross-family reviewer and reports it in `policy_selection`.
 
 ## Tooling map
 
-| Gate                      | Prefer                                                                                   |
-| ------------------------- | ---------------------------------------------------------------------------------------- |
-| Lint / types / tests / QA | `wp_lint`, `wp_typecheck`, `wp_test`, `wp_qa`                                            |
-| Format                    | `wp_format`                                                                              |
-| Audits                    | `wp_audit`, `wp_audits`                                                                  |
-| Blueprint                 | blueprint MCP tools + `wp_audit`                                                         |
-| PR / CI wait              | `wp_pr_status`, `wp_pr_wait` (not multi-sleep loops)                                     |
-| Release                   | `wp_release_progress` for live Release phases; `wp_release_readiness` for package gates  |
-| Large output              | `wp_session_execute` / `batch_execute` / `execute_file`                                  |
-| Continuity                | `wp_session_capture` for verify summary; avoid paste-back walls                          |
-| E2E / act                 | `wp_e2e`, `wp_ci_act` when the change requires them                                      |
-| Outside authority         | `wp_review_gate` (purpose plan or delivery); each new provider verdict is a formal round |
+| Gate                      | Prefer                                                                                |
+| ------------------------- | ------------------------------------------------------------------------------------- |
+| Lint / types / tests / QA | `lint`, `typecheck`, `test`, `qa`                                                     |
+| Format                    | `format`                                                                              |
+| Audits                    | `audit`, `audits`                                                                     |
+| Blueprint                 | blueprint MCP tools + `audit`                                                         |
+| PR / CI wait              | `pr_status`, `pr_wait` (not multi-sleep loops)                                        |
+| Release                   | `release_progress` for live Release phases; `release_readiness` for package gates     |
+| Large output              | `session_execute` / `batch_execute` / `execute_file`                                  |
+| Continuity                | `session_capture` for verify summary; avoid paste-back walls                          |
+| E2E / act                 | `e2e`, `ci_act` when the change requires them                                         |
+| Outside authority         | `review_gate` (purpose plan or delivery); each new provider verdict is a formal round |
 
 ## Iron law — evidence before claims
 
@@ -81,7 +83,7 @@ Not sufficient: "should pass", "looks correct", lint-only evidence for runtime c
 
 Follow the repo's current routing and command surface:
 
-- use MCP `wp_*` / repo-owned quality wrappers first
+- use wp MCP tools / repo-owned quality wrappers first
 - use bounded session-memory tooling for large output
 - reuse fresh logs instead of re-running broad commands just to inspect output
 
@@ -102,7 +104,7 @@ workflow:
 2. Run the repo audit when available:
 
    ```text
-   wp_audit({"kind":"test-smells"})
+   audit({"kind":"test-smells"})
    ```
 
    Use the global `wp audit test-smells` command only when MCP is unavailable.
@@ -137,16 +139,16 @@ Hard stop on any failure.
 
 Run the narrowest checks that prove the touched behavior:
 
-- `wp_lint` / targeted lint
-- `wp_typecheck` / targeted typecheck
-- `wp_test` / targeted tests
-- `wp_qa`, `wp_e2e`, build / package checks only when the change requires them
+- `lint` / targeted lint
+- `typecheck` / targeted typecheck
+- `test` / targeted tests
+- `qa`, `e2e`, build / package checks only when the change requires them
 
 **Before push or PR open/update**, run the pre-push owner end-to-end:
 
 ```text
-start = wp_ci_preflight({})
-wp_ci_preflight_wait({ runId: start.details.operation.runId })
+start = ci_preflight({})
+ci_preflight_wait({ runId: start.details.operation.runId })
 ```
 
 The start result is not a gate verdict. Poll again when wait returns
@@ -160,19 +162,19 @@ wp ci-preflight
 
 That runs the repository-owned, branch-scoped required-check plan fail-fast.
 Run it after the final commit and make no further worktree or base-ref
-changes before pushing. Agent-kit's `.husky/pre-push` checks the resulting
+changes before pushing. The app repo's `.husky/pre-push` checks the resulting
 exact-state receipt without rerunning the suite after Git opens the remote
 transport; consumer repos may keep pre-push checks user-owned. Do **not** claim
 push-ready if preflight failed. Do **not** bypass hooks to ship red work.
 
 Rules:
 
-- Prefer MCP `wp_*` over raw underlying tools.
+- Prefer wp MCP tools over raw underlying tools.
 - Reuse fresh logs / session-memory indexed output if the runner auto-saves them.
 - Never claim broader correctness than the commands actually proved.
-- If the repo documents a "full QA" bookend, reserve `wp_qa` / `--full` for the final broad pass rather than every iteration.
+- If the repo documents a "full QA" bookend, reserve `qa` / `--full` for the final broad pass rather than every iteration.
 - If CI is already red: read the failed job log, reproduce with the matching
-  local `wp_ci_preflight` + `wp_ci_preflight_wait` flow (or the `wp ci-preflight` CLI fallback), fix, then push **one**
+  local `ci_preflight` + `ci_preflight_wait` flow (or the `wp ci-preflight` CLI fallback), fix, then push **one**
   corrective commit — do not burn another full matrix “to check.”
 
 ## Phase 3 — Cross-surface impact scan
@@ -209,7 +211,7 @@ Check that:
 - UX or operator-facing flows include graceful-degradation coverage when applicable
 
 Run the folded TPH gate for every verification target. At minimum, execute
-`wp_audit` with the `test-smells` kind when available (use global `wp audit
+`audit` with the `test-smells` kind when available (use global `wp audit
 test-smells` only as the CLI fallback) and inspect changed tests against the
 `testing-philosophy` checklist. Add E2E or integration evidence when the change
 touches user/operator-facing workflows, batch/list behavior, graceful
@@ -253,7 +255,7 @@ Before claiming **merge-ready** / land:
 
 ### 1. Classify with immutable refs
 
-Run `wp_audit` with `kind: "risk-review-coverage"` using:
+Run `audit` with `kind: "risk-review-coverage"` using:
 
 - immutable PR **base** SHA
 - immutable **authority** (head) SHA
@@ -267,13 +269,13 @@ CI job in `.github/workflows/pr-policy.yml`.
 
 When classification is **sensitive**:
 
-- Require delivery review via `risk-review-coverage` / `wp_review_gate`
+- Require delivery review via `risk-review-coverage` / `review_gate`
   (purpose delivery) / qualifying lane approvals for the current
   review subject until `policySatisfied` (**approval**). A formal **reject** is a terminal automated-review
   outcome but does **not** satisfy land policy: Product status stays
   `incomplete`, Process status stays `sensitive-blocked` until approval.
   Tech-debt is **not** a substitute for delivery approval.
-- Launch **exactly one at a time** `wp_review_gate` delivery attempt with
+- Launch **exactly one at a time** `review_gate` delivery attempt with
   `--base-ref <base-sha>` and `--authority-ref <head-sha>`. Do not substitute
   `HEAD` for the authority SHA, and do not relaunch while the same subject has
   an in-progress gate.
@@ -312,8 +314,8 @@ When classification is **standard**:
   Must be start-of-line. Process label: `standard-skip`.
 
 - Otherwise obtain **exactly one sequential** outside voice: one
-  `wp_review_gate` delivery gate (or host skill). Process label: `outside-approved`.
-- At most **one OpenCode Go reviewer** counts unless the user asks for more.
+  `review_gate` delivery gate (or host skill). Process label: `outside-approved`.
+- At most **one outside reviewer** counts unless the user asks for more.
 - Invoke the selected reviewer **once**. Do not probe, retry, or rotate
   providers automatically, and **never** fan out parallel multi-host review
   swarms.
@@ -322,12 +324,13 @@ When classification is **standard**:
 - These approvals are model outside-voice approvals, not a substitute for human
   GitHub reviews or branch-protection approvals.
 
-Reviewer preference (pick **one** path):
-
-- From Codex → Claude (else one OpenCode Go).
-- From Claude → Codex (else one OpenCode Go).
-- Prefer skills: `claude`, `codex`, or one of `opencode-go` / `qwen` /
-  `deepseek` / `glm` / `kimi` / `minimax` / `mimo`.
+Reviewer preference: the gate owns it. State `caller_model` (your own model
+id) and omit `provider`/`model`/`effort`; `review_gate` selects a
+cross-family reviewer by capability, current provider limits, and measured
+daily cost, and discloses the choice in `policy_selection`. Do not name a
+reviewer host or model, do not probe provider catalogs, and do not rotate
+providers yourself. A human operator may still name an explicit
+`provider`/`model` override; agents must not.
 
 ### 4. Dual product/process labels on every land claim
 
@@ -340,14 +343,14 @@ Never invent a land-now skip. See `land-policy` for the full table.
 
 ### Approval evidence requirements
 
-- Blueprint plan approval: use `wp_review_gate` with the current `bpv1` version.
+- Blueprint plan approval: use `review_gate` with the current `bpv1` version.
   It records the review and promotes an approved draft atomically by default.
   If the gate is still running or the host wait expires, poll the same exact
-  invocation with `wp_review_gate_wait` until a terminal review outcome is
+  invocation with `review_gate_wait` until a terminal review outcome is
   observed; wait timeout/abort/in-progress/not-found are not reviewer verdicts.
   `not_found` means there is no active or terminal gate for that subject; refresh
   state and start the gate again instead of continuing to wait.
-- Implementation / delivery approval: use `wp_review_gate` purpose delivery
+- Implementation / delivery approval: use `review_gate` purpose delivery
   on the immutable subject, exactly once with the selected provider, for
   sensitive and standard PRs alike. The gate has one mode: each newly executed
   provider review that reaches a verdict is one formal round of the slug's
@@ -358,7 +361,7 @@ Never invent a land-now skip. See `land-policy` for the full table.
   spends none). Do not run a separate
   provider probe.
 - Two gates on the same subject cannot run concurrently — every
-  `wp_review_gate` call claims the subject's active marker. If a call reports
+  `review_gate` call claims the subject's active marker. If a call reports
   marker contention, serialize the two calls rather than treating contention
   as an error.
 - Each gate reviewer must return exactly one schema-valid JSON review object;
@@ -377,7 +380,7 @@ Never invent a land-now skip. See `land-policy` for the full table.
 Report:
 
 - mode used (`local` / `full` / `merge-ready`)
-- what was verified and which `wp_*` commands/logs prove it
+- what was verified and which wp MCP tools commands/logs prove it
 - which docs/help/instruction surfaces were refreshed when guidance changed
 - outside models only if merge-ready (with PR comment links when applicable)
 - what remains intentionally out of scope
@@ -388,7 +391,7 @@ If any required check is missing, the correct result is **not done yet**, not a
 
 **Tooling friction (optional):** if this session burned medium+ tokens on MCP/CLI/hooks/CI
 gates (not product code), run `/tooling-friction` once and resolve its capture
-destination with `wp_tooling_friction_path({"file":"<file>"})` — copy the absolute
+destination with `tooling_friction_path({"file":"<file>"})` — copy the absolute
 path from the tool summary (human CLI: `wp tooling-friction path --file <file>`).
 Do not invent fleet folder slugs or worktree-keyed desktop-state paths. Skip when
 the path was smooth. If the surface cannot be resolved or written, report the skip