skills.rest
Pranil9699
Pranil9699COMMUNITY
Explore all skills by this author →
WebsiteGitHub

validation

Register and orchestrate named shell-based validation steps for code quality checks.

Updated Mar 31, 2026
Search Tags:#automation#workflow#validation#lint#ci#tests#typecheck
One-click install
npx skills add https://github.com/Pranil9699/Payroll-Employment-System --skill validation-pranil9699
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validation
Source: https://github.com/Pranil9699/Payroll-Employment-System/tree/main/.local/skills/validation
Command: npx skills add https://github.com/Pranil9699/Payroll-Employment-System --skill validation-pranil9699

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Register shell commands as named validation steps (like CI checks) that can be triggered and monitored to verify code quality.

Core Features & Use Cases

  • Create or update a named validation command with setValidationCommand(name, command).
  • Remove a validation command with clearValidationCommand(name).
  • List all registered validation commands with getValidationCommands().
  • Start a validation run with startValidationRun(commandIds) to execute multiple checks in a CI-like flow.
  • Stop a running validation run with stopValidationRun(runId, graceful?).
  • Retrieve results with getValidationRun(runId) and getValidationRuns().
  • Use conventional names like lint, test, typecheck, and format to map to common tooling across Node.js, Python, and Go projects.

Quick Start

Register validation commands for lint and test, then start a run to execute them.

Frequently Asked Questions about validation

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

FAQPage Schema
How do I run named validation steps for code quality in a CI workflow?▼

You can register shell commands as named validation steps and execute them in a CI-like flow using startValidationRun. This orchestrates multiple checks like lint and test to verify code quality across Node.js, Python, and Go projects.

Can I use shell commands to automate lint, typecheck, and test checks for local development?▼

Yes, you can register shell commands as named validation steps using setValidationCommand. You can then execute these validation runs as local development gates to automate lint, typecheck, and test checks.

How do I monitor and retrieve logs for a running validation run?▼

You can monitor active validation runs and retrieve per-command logs and statuses using getValidationRun with the runId. This provides detailed execution results for each registered validation step.

What is the best way to organize and list all registered code quality checks?▼

You can list all registered validation commands with getValidationCommands. Using conventional names like lint, test, typecheck, and format maps your registered shell commands to common tooling across Node.js, Python, and Go projects.

How do I stop a running CI check if I need to halt a validation run?▼

You can stop a running validation run using stopValidationRun with the specific runId. This allows you to gracefully halt execution of your registered validation steps during a CI-like flow.

Can I remove an outdated validation command from my CI workflow?▼

Yes, you can remove a validation command from your workflow using clearValidationCommand with the command name. This unregisters the shell step from future validation runs.

Related Skills

Explore More Software Engineering Skills→
akhilksap2026akhilksap2026

validation

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

Community
Intermediate
offers-pngoffers-png

validation

Register named validation commands and execute CI-style code quality checks.

Community
Intermediate
adminsairolotech-bitadminsairolotech-bit

validation

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

Community
Advanced
Buntyarora97Buntyarora97

validation

Execute and monitor named shell commands as validation steps.

Community
Advanced