Test After Changes

What problem does it solve?

This Skill provides a rapid, standardized workflow to validate code changes immediately after they are made, catching common issues like broken imports, syntax errors, and service startup failures before they are committed. This prevents costly bugs from propagating and saves significant debugging time.

Core Features & Use Cases

• Progressive Validation: Runs checks in order of speed (syntax, imports, service startup, unit tests), failing fast to pinpoint issues quickly.
• Actionable Fixes: Provides clear pass/fail reports with specific error messages and commands to fix problems.
• Service-Specific Checks: Adapts validation to different applications within a monorepo (e.g., Resume Agent, LangGraph).
• Use Case: Automatically invoked after refactoring, adding new features, or fixing bugs. Can also be manually invoked by asking "Validate the changes I just made" to ensure code integrity.

Quick Start

Run the complete validation workflow

./scripts/validate-changes.sh

Or for a quick syntax and import check

python -m compileall -q . && pytest --collect-only -q

Manually invoke after making changes

I just made some changes to the graph_registry.py file. Can you validate that everything still works?