One-click install
npx skills add https://github.com/4tie/fortiesr --skill validation-4tie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validation
Source: https://github.com/4tie/fortiesr/tree/main/.local/skills/validation
Command: npx skills add https://github.com/4tie/fortiesr --skill validation-4tie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns ad hoc shell checks into named, repeatable validation workflows that are easy to run, monitor, and compare over time.

Core Features & Use Cases

  • Named Validation Commands: Register reusable checks like lint, test, typecheck, and format with simple command names.
  • Run Monitoring: Start one or more checks together and track their pass, fail, timeout, or stop status with per-command logs.
  • Use Case: A developer updates code and wants to verify quality gates by running lint and tests as a single monitored validation run.

Quick Start

Register your project’s validation commands and start a run for the checks you want to verify.

Frequently Asked Questions about validation

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

FAQPage Schema
How do I run CI-style checks like linting and type checking on demand?

You can run CI-style checks on demand by registering named validation commands for linting, type checking, and testing, then starting a monitored validation run to track their pass, fail, or timeout status with per-command logs.

What is the best way to monitor multiple code quality checks at the same time?

The best way to monitor multiple code quality checks is to group registered validation commands into a single run, allowing you to track pass, fail, timeout, or stop status for each command with individual logs.

Can I reuse ad hoc shell commands for repeatable software testing workflows?

Yes, you can turn ad hoc shell commands into repeatable software testing workflows by registering them as named validation commands, enabling easy execution and status monitoring for your project's quality gates.

How do I track the status and logs of individual shell commands in a validation run?

You can track the status and logs of individual shell commands by starting a validation run that monitors pass, fail, timeout, or stop status for each registered check, providing per-command logs for review.

Does this validation tool require any external dependencies to run typecheck and lint commands?

No, this validation tool has no external dependencies, allowing you to directly register and run your project's existing lint, typecheck, and test shell commands to verify code quality.

Why use named validation workflows instead of running shell checks manually?

Named validation workflows replace manual shell checks by providing repeatable, monitored runs that track status, capture per-command logs, and make it easy to compare code quality verification over time.