Affected Verification
Select relevant project-owned checks for an observed change and produce an evidence-based verification report that distinguishes passed, failed, skipped, blocked, and not-run checks.
SPECIALIST PRESET · REVIEW · V0.1.0
Determine whether the actual candidate and deployment evidence satisfy the accepted release gates.
From a full checkout. JSON includes file hashes, not an installation or an execution.
node tools/bundle.mjs role release-verifierThese 6 skills are references, not instructions to load everything at once.
Select relevant project-owned checks for an observed change and produce an evidence-based verification report that distinguishes passed, failed, skipped, blocked, and not-run checks.
Validate combined parallel changes and promote identified artifacts while preserving independent release approval, integration capacity, and recovery.
Prepare a commit-specific engineering handoff from an existing Git worktree, separating actual changes and executed checks from unresolved work, resource ownership, and integration risks.
Compare an intended agent execution profile with current worktree-bound observations, separating requested settings, resolved configuration, and actual runtime behavior.
Preserve task state across compaction or handoff with source-backed decisions, unresolved failures, current artifacts, and explicit freshness checks.
Audit a static publication for canonical URL, metadata, sitemap, internal-link and indexing-directive mistakes while separating technical findings from search ranking claims.
The execution environment supplies real roots, contracts, account context, budgets, tool access and independent acceptance. Keep those private. Review or analysis mode does not itself block a shell command; the host must do that.
Explore Specialist Role Composition →