validate

Automate linting, formatting, and testing for services affected by file changes.

381|261|Updated May 7, 2026
One-click install
npx skills add https://github.com/nudgebee/nudgebee --skill validate-nudgebee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate
Source: https://github.com/nudgebee/nudgebee/tree/main/.gemini/skills/validate
Command: npx skills add https://github.com/nudgebee/nudgebee --skill validate-nudgebee

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the validation process for services affected by file changes, ensuring code quality and functionality before deployment.

Core Features & Use Cases

  • Automated Validation: Validates affected services based on changed files, including linting, formatting, and tests.
  • Service-Specific Commands: Executes different validation commands for various services.
  • Use Case: After a code commit, this Skill can be used to validate the api-server service, ensuring that changes do not break existing functionality.

Quick Start

Run validation for all affected services with the 'validate' skill.

Frequently Asked Questions about validate

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

FAQPage Schema
How do I automate service validation for changed files in a CI/CD pipeline?

Automated service validation for changed files runs linting, formatting, and testing commands within your CI/CD pipeline to ensure code quality before deployment.

What is file change-based validation for multiple software services?

File change-based validation is a process that automatically detects affected services from recent commits and executes service-specific linting and testing commands.

Can I run different validation commands for each affected service?

Yes, service-specific validation commands can be configured to execute distinct linting, formatting, and testing rules for various services affected by file changes.

What's the best way to validate an API server after a code commit?

Validating an API server after a commit is handled by running automated validation commands that check the affected service for formatting, linting, and test failures.

Why does service validation not trigger for unrelated file changes?

Service validation targets only services directly affected by file changes, ensuring that unrelated services are skipped to optimize CI/CD workflow execution time.