skills.rest
KhaledMKhaled
KhaledMKhaledCOMMUNITY
Explore all skills by this author →
GitHub

validation

Register and run named shell validation commands for lint, tests, and typechecking.

Updated Dec 10, 2025
Search Tags:#validation#lint#test execution#typecheck#ci checks#run monitoring#log summaries
One-click install
npx skills add https://github.com/KhaledMKhaled/FodaStore --skill validation-khaledmkhaled
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validation
Source: https://github.com/KhaledMKhaled/FodaStore/tree/main/.local/skills/validation
Command: npx skills add https://github.com/KhaledMKhaled/FodaStore --skill validation-khaledmkhaled

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of running repeatable code-quality checks consistently and knowing which checks passed or failed.

Core Features & Use Cases

  • Register named validation commands: Create or update reusable steps like lint, tests, and typechecks using short IDs.
  • Start and monitor validation runs: Execute one or more registered commands, then track run status, per-command outcomes, exit codes, and log paths.
  • Summarize failures with log citations: Use an LLM-generated runSummary to understand what failed without manually inspecting every full log.

Use Case: You want quality gates for every change—register lint, test, and typecheck once, then run them together to quickly determine whether a commit is healthy.

Quick Start

Ask the AI to register your checks as validation commands and then start a run for the ones you want to verify today.

Frequently Asked Questions about validation

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

FAQPage Schema
How do I run lint, test, and typecheck validation commands together for a commit?▼

You can register named validation commands for lint, tests, and typechecks, then start a multi-command validation run to execute them together and verify if a commit is healthy.

What is the best way to track CI check results and identify which validation step failed?▼

Tracking CI check results is done by retrieving run status, which provides per-command outcomes, exit codes, and log paths to pinpoint exactly which validation step failed.

Can I get a summarized report of test execution failures without reading the full logs?▼

Yes, validation runs provide an LLM-generated runSummary that highlights summarized failures with log citations, allowing you to understand errors without manually inspecting full logs.

How do I register reusable shell commands for code quality checks?▼

You can create or update reusable validation commands by assigning short IDs to shell commands, enabling consistent execution of code quality checks across your workflows.

Does the validation skill support stopping or querying active validation runs safely?▼

Yes, the skill runtime provides operational functions to safely query the status of active validation runs and stop them when needed within the execution environment.

Related Skills

Explore More Software Engineering Skills→
ovachieverovachiever
52

shellcheck-configuration

Configure ShellCheck static analysis with .shellcheckrc for CI/CD integration.

Community
Basic
rezosndrezosnd

validation

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

Community
Intermediate
C-RossC-Ross
2

llmeval-tracking

Aggregate LLM evaluation results and generate per-test trend reports.

Community
Intermediate
tamnguyentommy-rgbtamnguyentommy-rgb
2

validation

Define and run named validation commands for code quality checks.

Community
Advanced