feature-validate

Execute tests, lint, type checks, and custom validation gates on completed features.

415|44|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/notque/claude-code-toolkit --skill feature-validate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-validate
Source: https://github.com/notque/claude-code-toolkit/tree/main/skills/feature-validate
Command: npx skills add https://github.com/notque/claude-code-toolkit --skill feature-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Run quality gates on implemented feature: tests, lint, type checks, and custom validation. Use after /feature-implement completes. Use for "validate feature", "run quality gates", or "/feature-validate".

Core Features & Use Cases

  • Run language-specific quality gates (tests, lint, type checks)
  • Verify all planned files were created/modified
  • Check for regressions
  • Produce validation report

Quick Start

After implementing a feature, run /feature-validate to execute the quality gates and generate a validation report.

Frequently Asked Questions about feature-validate

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

FAQPage Schema
How do I run quality gates on a completed feature?▼

You can run quality gates on a completed feature by executing tests, lint checks, type checks, and custom validation to verify quality and check for regressions. This automated feature validation produces a comprehensive report.

What is feature validation in software development?▼

Feature validation is the process of enforcing feature quality through automated gates. It executes language-specific tests and lint checks to detect regressions, ensuring all planned files were created before release.

Can I use automated quality gates across different programming languages?▼

Yes, automated quality gates can be applied across languages. The validation process features language-detection to integrate with your existing tools and enforce that all gates pass before release.

When do I need to run quality gates and lint checks?▼

You need to run quality gates and lint checks immediately after feature implementation completes. This ensures all planned files were modified correctly and catches regressions before generating a validation report.

What is the best way to check for regressions after implementing a feature?▼

The best way to check for regressions is to run an automated feature validation process that executes tests, lint, and type checks. This enforces quality gates and produces a comprehensive validation report.