Results for “license-verification”

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.

Use when incorporating or distributing code, libraries, assets, or content with licensing requirements. This skill provides procedures for identifying, tracking, and complying with licenses across all dependencies and third-party materials.

Use when sources must stay traceable across sessions and years, when each reference needs a passport recording where it was found, how it was verified, and where it is cited, or when a draft needs a cited-but-unverified sweep before submission.

Verify signed artifacts and SLSA build provenance with Sigstore cosign and slsa-verifier, enforce keyless OIDC identity, and apply SLSA Build levels to harden the software supply chain.

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".

Testing Verification Skill

A comprehensive verification system for Claude Code sessions.

Runs a multi-phase verification pipeline including build, type-check, lint, tests, security scan, and diff review to ensure code quality before creating a PR.

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

Detect abuse of legitimate Windows binaries (LOLBins) like certutil, regsvr32, mshta, and rundll32 using process telemetry, Sigma rules, and parent-child process analysis.

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

Guides open source license selection, comparison, compliance review, and drafting of LICENSE/NOTICE files using canonical texts.

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.

Verify that a change really works before you claim completion

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.

Runs a comprehensive verification pipeline for Django projects including migrations, linting, tests with coverage, security scans, and deployment readiness checks before PRs or releases.

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

Validates observable behavior of apps, CLIs, APIs, and generated artifacts against a prewritten contract without inspecting source code.

Lint and Validate Skill

Enforces running verification commands and confirming output before claiming work is complete, fixed, or passing, ensuring evidence precedes any success claims.

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

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.

Plan structure validation, phase completeness checks, reference integrity verification, and artifact existence confirmation. Provides the structured verification layer ensuring GSD artifacts are well-formed and complete.

Stops fantasy approvals, evidence-based certification - Default to "NEEDS WORK", requires overwhelming proof for production readiness

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.

This skill should be used when the user asks to "validate a plugin", "optimize plugin", "check plugin quality", "review plugin structure", or "run plugin optimizer".

Generate comprehensive checklists to validate requirements quality (Unit Tests for Specs). Critically examine the spec for clarity, completeness, and consistency before implementation starts.