Register and run named shell commands as repeatable CI-style validation checks.
npx skills add https://github.com/AmirEmad11/instabot --skill validation-amiremad11
Please help me install this Agent Skill. Skill: validation Source: https://github.com/AmirEmad11/instabot/tree/main/.local/skills/validation Command: npx skills add https://github.com/AmirEmad11/instabot --skill validation-amiremad11
npm run lint or pytest under short names (lint, test, typecheck) with upsert behavior, and list or remove them as needed. - Monitored Validation Runs: Execute one or more registered commands in a single run and receive per-command status, exit codes, durations, log file paths, and an LLM-generated failure summary with log line citations. - Run Management: Stop in-progress runs gracefully or forcefully, and query the status and history of past runs by ID. - Use Case: After implementing a feature in a Node.js project, register lint, test, and typecheck commands, run them together, and immediately read a summarized explanation of any failure without digging through full logs. ## Quick Start Register lint and test as validation commands for my project, then run them and tell me what failed.High-intent search queries and answers about installing and using this skill.
Register each check as a named validation command, such as lint mapped to npm run lint or test mapped to npm test. Then start a validation run with those command names to execute them together and receive structured pass/fail results.
Start a validation run with the command IDs you want, such as lint and test. The run returns per-command status, exit codes, and log paths, plus a runSummary that explains what failed with citations to specific log lines.
Common conventions are ruff check for lint, pytest for test, and mypy for typecheck in Python, and golangci-lint run, go test ./..., and go vet ./... in Go. Use short lowercase names like lint, test, and typecheck.
Yes, call stopValidationRun with the run ID to halt an in-progress run. It stops gracefully by default, but you can pass graceful as false to force an immediate stop.
Avoid them for one-off test runs, where invoking the shell directly is simpler, and for deploy workflows, which belong to a deployment skill. Validation commands are meant for repeatable, named quality checks.
durancristhianSets up Husky pre-commit hooks with lint-staged and Prettier.
brave-experimentsImplement code review feedback on pull requests with automated validation.
nampham2Run pytest suites, verify 100% coverage, and validate pre-commit hooks.
testdriveraiOrchestrate TestDriver tests in CI/CD pipelines with parallel execution across platforms.