Results for “postgrid-verify”

Verify project behavior anchors — compilation, tests, and interaction checks after autonomous runs. NOT the Claude Code built-in /verify (which runs the app to observe a single change working) — this one walks the CLAUDE.md "Features (Behavior Anchors)" list.

Validates that a Dynamo deployment's NIXL/UCX/NCCL interconnect is ready for disaggregated serving over RDMA/NVLink. Use after deploying a disagg or multi-node recipe to confirm KV transport is correct, or use troubleshoot for already-failed pods.

Run pre-deployment validation checks for Azure readiness, including configuration, infrastructure (Bicep or Terraform), RBAC role assignments, and managed identity permissions.

Verifies suspected security bugs to eliminate false positives, producing a TRUE POSITIVE or FALSE POSITIVE verdict with documented evidence for each.

Verify a GitHub pull request against a Jira issue's goals, requirements, and acceptance criteria, then post a PR comment with the findings. Use when a user asks Codex or MoonMind to compare a PR to a Jira story/task/bug, confirm whether a PR satisfies Jira requirements, audit implementation coverage from Jira, or publish a Jira-vs-PR verification summary.

Verify code changes work by running them. Proves through execution, not just inspection.

Combined verification — recite (description quality via cold-read prediction) + validate (schema compliance) + review (health checks). Use as a quality gate after creating notes or as periodic maintenance. Triggers on "/verify", "/verify [note]", "verify note quality", "check note health".

Find sources for every numerical claim in the draft, add inline hyperlinks, and add internal links to brand-reference articles. Triggered after /draft.

Conduct cybersecurity assessments of electric power grid infrastructure, including NERC CIP compliance verification, substation automation security, and IEC 61850 protocol analysis.

Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.

Verifica que una implementación cumpla los specs del ciclo SDD ejecutando tests reales, revisando cobertura y emitiendo un veredicto de aprobación o rechazo.

A comprehensive verification system for Claude Code sessions.

Lock any ERC-20 token on Base for GitHub-gated vesting, linking wallet and repo to release tokens on verified pushes.

Perform a non-destructive post-implementation verification gate validating the implementation against spec.md, plan.md, tasks.md, and constitution.md.

Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).

Verifica la reproducibilidad y consistencia de un análisis de datos antes de presentarlo, validando contra la pregunta original y documentando limitaciones.

Verify the article’s factual, product, citation, and link integrity before visual production.

Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style), not a decorative one. Encodes the discipline — columns + modules + baseline, grotesque type, flush-left ragged-right, restrained black/white/red — AND the front-end engineering that makes the grid load-bearing: one CSS-variable source of truth, a grid-toggle overlay that lives in the SAME content box as the content, subgrid 'bands' so every element snaps to a column line, an 8px baseline lock, and runtime optical alignment that puts display type's ink (not its box) on the line. Ships a scaffold generator and a Puppeteer harness that proves 0px adherence. Use when: building any editorial, magazine, report, or longform page that must read as rigorously grid-aligned, Swiss, International Typographic Style, or 'Müller-Brockmann'. Triggers: magazine spread, grid system, Swiss design, editorial layout, show the grid, grid overlay toggle, baseline grid, modular grid, 12-column layout, 瑞士网格, 版面网格.

EmailVerify API skill. Use when working with EmailVerify for sendCode, checkCode. Covers 2 endpoints.

Runs a read-only pre-deploy verification gate covering git status, builds, tests, migrations, secrets, and commit conventions, then reports READY or NOT READY.

Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

Verify implemented work meets acceptance criteria — run tests, check PHPCS, validate Blade output, lando phpunit, lando phpcs, lando yarn test, Playwright tests, accessibility check, post-implementation verification, done criteria validation, checklist review, verification phase

Verification-before-completion discipline ensuring all success criteria are met, tests pass, and reviews complete before declaring work done.

Validates Claude Ads contracts, bundles, scores, runs, capabilities, repositories, and releases with deterministic checks and recovery steps.

Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.

Verify an MarketingClaw release is fully published across GitHub, npm, plugins, ClawHub, package smoke, and live Gateway agent turns.

Runs bottom-up type-chain validation across database, hooks, and UI layers, then fixes errors at the failing layer for project health checks before large changes.

Claude Code 会话的全面验证系统。

Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when asked to "review this PR", "code review", "pre-landing review", or "check my diff". Proactively suggest when the user is about to merge or land code changes. (gstack)

Provisions third-party services and retrieves API keys using the Stripe Projects CLI plugin, with catalog search and project initialization.

Provides grep-based patterns to verify that code artifacts are real implementations rather than stubs or placeholders, covering React components, API routes, database schemas, and hooks.

Verify that a change really works before you claim completion

Verify a Jira issue against the current repository state, then post a Jira comment with a PASS, PARTIAL, FAIL, or BLOCKED verdict. Works in two modes: (a) feature-branch mode, comparing a checked-out branch to its base ref; or (b) main/trunk mode, verifying that an issue is already implemented on the current default branch (typical for stories that have already merged). Use when a user asks whether a branch or merged change completes a Jira ticket, or needs a Jira-visible verification comment.

Scaffolds a per-task verification skill for a repo, including a dev-local launcher, a browser driver, and a verification SOP that spawns a sub-agent to drive the app and produce proof.

Build, relaunch, and observe the Claudence menu bar app to verify a change end-to-end.