change-validation

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.

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.

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.

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.

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.

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.