verify-changes
Verify Changes
Run declared commands directly. This skill does not load a model preview for a command only branch. If another branch dispatches a worker, that branch must bind one exact approved snapshot to its request, reservation, and report. Nested calls reuse that snapshot and do not add workers.
Produce captured evidence for the repository's required gates and the requested change. Discover commands, select the relevant checks, run their actual prerequisites, and report results. This skill does not repair code.
Modes
- Manual: honor the user's requested check set. An explicit request for all checks runs every required gate; otherwise select the affected checks and applicable repository gates.
- Pipeline (
mode:pipeline): use the caller's scope and acceptance contract without questions. Return the structured result fromreferences/checks-schema.jsonand one verdict. Required repository gates still apply.
Discover and scope
Read references/command-discovery.md. Prefer the repository's named scripts and read-only CI configuration over reconstructed commands. Record detected build systems and command sources in commandSurface.
Reuse the explicit caller base and the approved source snapshot's base before default discovery. When both are supplied, require the resolved commit and intended comparison scope to agree; a mismatch or an unresolvable supplied base blocks affected checks until corrected. Only when neither supplies a base, resolve origin/HEAD, code-host metadata, then main. Save the selected ref, resolved commit, selection source, and supplied snapshot reference in scope.json inside the returned evidenceDir. Name that scope-record path in the human report. Keep base metadata in this separate artifact; do not add undeclared properties to checks-schema.json results. Include committed, staged, and unstaged changes for the current worktree. A branch diff alone is incomplete. Preserve the snapshot's scope; prepare a new snapshot when current edits change it. Use native affected-package support when available. Without it, identify safe package or file checks from the repository's commands; use whole-repository checks when required or when a narrower valid check is unavailable. Record workspacesScoped.supported: false when native scoping is absent.