Results for “config-validation”

NestJS architecture patterns for modules, controllers, providers, DTO validation, guards, interceptors, config, and production-grade TypeScript backends.

Use this when reviewing how a codebase organizes configuration files, env vars, runtime options, feature flags, and per-environment settings. Trigger on requests to clean up or validate config structure.

Centralized JSON validation for AGENT_SUCCESS_CRITERIA with defensive parsing and injection attack prevention (CVSS 8.2)

A comprehensive verification system for Claude Code sessions.

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

Reviews secrets, config defaults, environment variables, logs, credentials, CI secrets, and unsafe settings.

Validates custom dotnet new templates for correctness before publishing, catching missing fields, parameter bugs, shortName conflicts, constraint issues, and common authoring mistakes.

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.

Validate current branch follows feature branch naming conventions

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

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

NestJS architecture patterns for modules, controllers, providers, DTO validation, guards, interceptors, config, and production-grade TypeScript backends.

Schema validation for notes. Checks against domain-specific templates. Validates required fields, enum values, description quality, and link health. Non-blocking — warns but doesn't prevent capture. Triggers on "/validate", "/validate [note]", "check schema", "validate note", "validate all".

A validation *boundary* is any point where data crosses from a system you do not

Detect and validate GPU availability for MATLAB GPU computing. Use when the user can't use their GPU, or is setting up or selecting a GPU. Triggers on: gpuDevice, GPU setup, check GPU, GPU not found, GPU not working, can't use GPU, GPU not available, unable to find a supported GPU device, compatible GPU, canUseGPU, validateGPU.

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

Runs a QA validation cycle followed by bugfix until all criteria pass clean, with automated verification and re-validation.

Check whether Claude Code CLI is ready in this environment and optionally toggle the stop-time review gate. Args: --enable-review-gate, --disable-review-gate. Use for installation, authentication, or review-gate setup requests.

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

Validate user claims against codebase and git history, trace to root cause, and propose a fix

Verify TPM measured boot integrity and remote attestation using tpm2-tools, including PCR reading, event log replay, quote generation and verification, and golden baseline comparison.

Runs a persistent verification-and-fix loop, executing existing test suites and browser/desktop checks until the requested surface is verified or a real blocker remains.

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

Verify that a change really works before you claim completion

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

Validate whether an OSS tool is worth building through staged namespace, existing-solution, and feasibility review

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.

Imported skill validate from vercel

Runs a two-wave validation pipeline (deterministic checks then rule-based checks) before every git commit, writing a sentinel file that a pre-commit hook enforces. Includes optional quick mode (first wave only) and a fix loop with up to three iterations.