Change Validation Planner
Skill Verified ActivePlans the narrowest trustworthy validation path for a scoped code change or diff. Use when a user asks what to run before merging, how to validate a specific change, whether the current checks are enough, or wants a bounded command order from narrow to broad. Do NOT use for writing tests, fixing the code change itself, broad QA sweeps, or generic debugging that needs root cause analysis.
To help users and agents create focused validation plans for code changes, ensuring the right checks are run in the correct order to gain confidence before merging.
Features
- Plans validation paths for scoped code changes
- Identifies narrowest trustworthy command sequences
- Distinguishes between proven and unproven aspects of a change
- Reuses repo-native commands and conventions
- Avoids generic debugging and test writing
Use Cases
- When asking what to run before merging a PR
- When needing to validate a specific diff or local edit
- When comparing narrow vs. broad validation options
- When understanding what a code change does NOT prove
Non-Goals
- Implementing the code change itself
- Writing or expanding tests as the primary task
- Generic QA across the whole repo
- Root-cause debugging
- Architecture planning
Practical Utility
- info:Usage examplesThe SKILL.md and README do not contain explicit end-to-end usage examples demonstrating input, invocation, and output.
Installation
/plugin install swe-skills@ckorhonen-swe-skillsQuality Score
VerifiedTrust Signals
Similar Extensions
Claude Handoff
100Run /handoff to capture session data, then write a phased implementation plan that references it. Creates beads for tracking.
Openclaw Testing
100Choose, run, rerun, or debug OpenClaw tests, CI checks, Docker E2E lanes, release validation, and the cheapest safe verification path.
Crabbox
100Use Crabbox for OpenClaw remote validation across Linux, macOS, Windows, and WSL2. Default to Blacksmith Testbox for broad Linux proof; includes direct Blacksmith and owned AWS/Hetzner fallback notes when Crabbox fails.
Plugin Test Runner
100Runs automated tests to validate plugin integrity across 14 categories. Use before creating PRs, after making changes to skills or templates, or to verify plugin health.
Review Pull Request
100Review a pull request end-to-end using GitHub CLI. Covers diff analysis, commit history review, CI/CD check verification, severity-leveled feedback (blocking/suggestion/nit/praise), and gh pr review submission. Use when a pull request is assigned for review, performing a self-review before requesting others' input, conducting a second review after feedback is addressed, or auditing a merged PR for post-merge quality assessment.
Oh My Claudecode
100Process-first advisor routing for Claude, Codex, or Gemini via `omc ask`, with artifact capture and no raw CLI assembly