validation

Register and manage named validation commands for code quality checks.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/se1111th/VisionPort-Visual-Refresh_SRC --skill validation-se1111th
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validation
Source: https://github.com/se1111th/VisionPort-Visual-Refresh_SRC/tree/main/.local/skills/validation
Command: npx skills add https://github.com/se1111th/VisionPort-Visual-Refresh_SRC --skill validation-se1111th

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Register shell commands as named validation steps to enforce and monitor code quality.

Core Features & Use Cases

  • Create, update, and remove named validation commands (lint, test, typecheck, etc.) with upsert behavior.
  • List all registered validation commands and their statuses to track project health.
  • Run one or more validation commands in a CI-style validation run and view per-command results.

Quick Start

Register a validation command named lint with the shell command npm run lint.

Frequently Asked Questions about validation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I register shell commands as named validation checks for my CI workflow?

You can register shell commands as named validation checks using an upsert behavior to define, trigger, and monitor quality gates like lint, tests, and type checks within your development workflow.

What is the best way to run multiple quality gates and view per-command status in a CI-style validation run?

Running multiple quality gates in a CI-style validation run allows you to view per-command results, execution status, and logs to track overall project health.

How do I list all registered validation commands and their current statuses?

Listing all registered validation commands and their statuses allows you to monitor project health, ensuring that all defined lint, test, and type check quality gates are properly tracked.

Can I update or remove existing validation commands without breaking my automation workflow?

Yes, you can update or remove existing validation commands using upsert behavior, ensuring your automation workflow adapts dynamically while maintaining consistent quality checks.

Does this validation approach work without external dependencies for code quality enforcement?

Yes, this validation approach works without external dependencies, allowing you to define, run, and monitor named validation checks natively to enforce code quality within your environment.