skills.rest
naopensedoit2-design
naopensedoit2-designCOMMUNITY
Explore all skills by this author →
GitHub

validation

Register and execute named validation commands with per-command log outputs.

Updated Apr 25, 2026
Search Tags:#unit tests#validation#lint#typecheck#ci checks#run monitoring
One-click install
npx skills add https://github.com/naopensedoit2-design/Claramente-nao-sou-um-Escritor --skill validation-naopensedoit2-design
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validation
Source: https://github.com/naopensedoit2-design/Claramente-nao-sou-um-Escritor/tree/main/.local/skills/validation
Command: npx skills add https://github.com/naopensedoit2-design/Claramente-nao-sou-um-Escritor --skill validation-naopensedoit2-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of inconsistently verifying code quality by providing a standardized way to register and run validation commands (like linting, tests, and typechecks) and to track their results over time.

Core Features & Use Cases

  • Named validation commands: Register or update reusable command definitions (e.g., lint, test, typecheck) by name so they can be triggered reliably.
  • Repeatable validation runs: Start a run for one or more registered validations and receive structured per-command outcomes (status, exit code, duration, and log paths).
  • Monitoring and troubleshooting: Retrieve individual runs or all past runs to understand whether checks passed or failed, using run summaries for faster diagnosis.

Quick Start

Use the validation skill to start a run of your lint and test checks for the current code state and review any failures via the generated run summary and command logs.

Frequently Asked Questions about validation

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

FAQPage Schema
How do I run and monitor repeatable project checks like lint and typecheck consistently?▼

To run repeatable project checks consistently, you register named validation commands for linting, testing, and typechecking, then execute them to receive structured outcomes including status, exit code, and duration logs.

What is the best way to track CI-style validation runs across project changes?▼

Tracking CI-style validation runs involves starting executions for registered commands and retrieving detailed per-command summaries, allowing you to monitor pass or fail states and review logs across project changes.

How do I register and update reusable unit test commands for consistent execution?▼

You register or update reusable unit test commands by name, ensuring that your testing, linting, and typechecking workflows are tracked and triggered reliably across project changes.

Can I retrieve and stop active validation runs to troubleshoot failing typechecks?▼

Yes, you can retrieve individual runs or stop active validation runs, using the generated run summaries and per-command log outputs to diagnose and troubleshoot failing typechecks or lint errors.

Do I need YAML frontmatter to define validation commands for CI checks?▼

Yes, the validation process requires YAML frontmatter-defined discovery metadata to properly register and execute your CI checks, unit tests, and linting workflows with tracked, repeatable execution.

Related Skills

Explore More Software Engineering Skills→
patrickhaahrpatrickhaahr

agent-creator

Create and configure Opencode Agents with YAML frontmatter and Markdown.

Community
Intermediate
rezosndrezosnd

validation

Register and run named shell validation commands with per-command exit codes and logs.

Community
Intermediate
adminsairolotech-bitadminsairolotech-bit

validation

Register shell commands as named validation steps for code quality checks.

Community
Advanced
canpok1canpok1

quality

Run build, lint:fix, and test commands to resolve code quality issues.

Community
Intermediate