ci: harden trusted PR review evidence (#1896)

This commit is contained in:
Carlos Florêncio
2026-07-23 16:22:50 +01:00
committed by GitHub
parent 1c70495689
commit a225fbac3e
57 changed files with 2193 additions and 425 deletions
+11 -7
View File
@@ -1,5 +1,5 @@
---
description: Run Kandev format, typecheck, tests, and lint before commit, then report failures without fixing source or test logic.
description: Verify committed changes before push, reusing proven hook coverage and using full mode only for broad or ambiguous impact.
mode: subagent
temperature: 0.1
permission:
@@ -9,16 +9,20 @@ permission:
"*": ask
---
Run the monorepo verification pipeline and report issues found.
Follow `.agents/agents/verify.md`, its impact matrix, and hook-evidence
reference. Run after commit and before push. Default to changed scope; validate
any supplied receipt, run only uncovered commands, and report PR/scope bases,
receipt eligibility, omissions, changed paths, commands, limits, and
`changed-scope PASS` versus `full PASS`. Never infer hook success, and never
rerun an eligible hook-covered command for reassurance.
Install `apps` dependencies when missing. Resolve the current PR base with
`gh pr view --json baseRefName`, fetch and report ancestry when it resolves;
do not rebase, resolve conflicts, or infer stacked-PR bases from Git upstream.
Generate web metadata, then run `make fmt`, `make typecheck`, `make test`, and
`make lint` through `scripts/run-quiet`. Full verification requires every test
subtarget, including CLI, scripts, and desktop smoke coverage; run scoped Rust
tests for Rust/Tauri changes after checking the required `rust-version`.
Run only uncovered matrix-selected commands. Full mode is for explicit,
ambiguous, broad, release/toolchain, or no-PR-CI delivery; ignore hook
omissions and cover every relevant subtarget.
Do not fix source or test logic. Retry environment-only failures with normal
sandbox escalation and invocation-specific writable temp/Go/lint caches. For
@@ -27,7 +31,7 @@ an implementer. Finish with a compact pass/fail report.
If required filesystem, network, or loopback escalation is unavailable, denied,
cancelled, or interrupted, stop and report verification as blocked. Explain
that mandatory verification is preventing commit and PR creation. Include a
that mandatory verification is preventing push and PR delivery. Include a
required user action telling the user to enable the runtime's full access mode,
then retry verification. Do not offer to proceed unverified or imply that the
agent or repository host cannot create PRs. Recommend full access only after