validate

Execute lint, build, and test scripts sequentially from package.json.

7|1|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/Nirusan/claude-config --skill validate-nirusan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate
Source: https://github.com/Nirusan/claude-config/tree/main/skills/validate
Command: npx skills add https://github.com/Nirusan/claude-config --skill validate-nirusan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of checking code quality and functionality by running linting, building, and testing procedures in sequence.

Core Features & Use Cases

  • Sequential Validation: Executes lint, build, and test scripts in a defined order, stopping on the first failure.
  • Adaptive Workflow: Detects available scripts in package.json (lint, build, test:e2e, test) and adjusts the validation process accordingly.
  • Use Case: Before committing code, use this Skill to ensure it passes all quality checks, preventing potential integration issues and bugs.

Quick Start

Run the validate skill to check the code quality and functionality.

Frequently Asked Questions about validate

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

FAQPage Schema
How do I run lint, build, and tests sequentially before committing code?

To validate code sequentially, execute an automated workflow that runs lint, build, and test scripts in order, stopping immediately upon the first failure to ensure code quality.

What is the best way to automate checking code quality and build functionality?

Automating code quality checks is best achieved by running a validation sequence that detects available scripts in package.json and executes lint, build, and test workflows to provide a comprehensive validation summary.

How does validation adapt when only some scripts are defined in package.json?

Validation adapts to package.json by detecting available scripts such as lint, build, test:e2e, and test, adjusting the sequential validation process to run only the scripts present in the configuration.

Can I use this to prevent integration issues by validating code before pushing?

Yes, you can validate code before pushing to prevent integration issues by running sequential lint, build, and test scripts, ensuring functionality passes all quality checks.

What happens when a linting or testing script fails during the validation process?

When a linting or testing script fails during the validation process, the sequential execution stops immediately on the first failure, providing a summary of validation results up to that point.