change-validation

Identify and execute repository-defined validation entrypoints for changed code.

2|Updated May 18, 2022

Search Tags:#automation #testing #linting #validation #makefile #ci

Ready to run

npx skills add https://github.com/alexfalkowski/bin --skill change-validation-alexfalkowski

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: change-validation
Source: https://github.com/alexfalkowski/bin/tree/main/skills/change-validation
Command: npx skills add https://github.com/alexfalkowski/bin --skill change-validation-alexfalkowski

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the guesswork in verifying code changes by identifying and executing the most relevant, repository-defined validation commands, ensuring that tests, linting, and security checks are performed consistently and efficiently.

Core Features & Use Cases

Targeted Validation: Automatically selects the narrowest credible checks for changed packages, features, or files to provide fast feedback.
Environment Awareness: Respects repository-defined Make targets and CI configurations to ensure validation matches the project's established workflow.
Use Case: When you modify a specific Go package, use this skill to run only the relevant unit tests and linting targets instead of executing the entire repository test suite.

Quick Start

Use the change-validation skill to identify and run the appropriate tests and lint checks for the current set of modified files.

Frequently Asked Questions about change-validation

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

FAQPage Schema

How do I run only the relevant unit tests for changed files instead of the entire repository test suite?▼

To run targeted unit tests for modified files, the skill identifies the narrowest credible checks by matching your changes against repository-defined Makefile targets and CI configurations, executing only the relevant validation commands for fast feedback.

What is the best way to automate linting and security scans for specific packages in a CI workflow?▼

Automating linting and security scans for specific packages requires identifying and executing repository-defined validation entrypoints. The skill applies environment-aware command execution based on your project's established Makefile targets and CI configurations.

Does this validation approach work with existing Makefile targets and CI configurations?▼

Yes, the validation approach works directly with existing Makefile targets and CI configurations. It ensures command execution matches your project's established workflow by respecting environment-aware repository-defined validation entrypoints for consistent checks.

How do I verify code changes with trusted repository checks automatically?▼

You can verify code changes automatically by identifying and executing repository-defined validation entrypoints such as linting, unit tests, and security scans. This eliminates guesswork by ensuring tests are performed consistently and efficiently.

Can I validate infrastructure component changes without triggering the full repository test suite?▼

Yes, you can validate infrastructure component changes without triggering the full test suite. The skill selects the narrowest credible checks for changed packages, features, or files to provide fast, targeted feedback for your specific modifications.

Why does executing the entire repository test suite take so long when I only modified a specific feature?▼

Executing the entire repository test suite takes long because it lacks targeted validation. The skill solves this by automatically selecting and running only the relevant checks for your specific feature changes, providing faster feedback.