refactor-validate

Validate refactor reports, run tests, and archive completed reports.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/KevounC/claude-kanban --skill refactor-validate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: refactor-validate
Source: https://github.com/KevounC/claude-kanban/tree/main/.claude/skills/refactor-validate
Command: npx skills add https://github.com/KevounC/claude-kanban --skill refactor-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the verification of refactor report completion and archiving, ensuring code quality post-refactor implementation.

Core Features & Use Cases

  • Cross-Finding Regression Checks: Verifies that all findings in a refactor report are resolved without causing new issues.
  • Test Suite Execution: Runs the full test suite for affected modules and reports pass/fail counts.
  • Pattern Compliance Updates: Updates the Pattern Compliance table to reflect resolved issues.
  • Backlog Extraction: Moves deferred items into a persistent backlog for future reference.
  • Report Archiving: Moves the completed refactor report to the archive directory.
  • Pipeline Completion Confirmation: Confirms the completion of the refactor cycle.

Quick Start

Run the /refactor-validate <scope> command after implementing all findings for a refactor report.

Frequently Asked Questions about refactor-validate

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

FAQPage Schema
How do I validate a refactor report after implementation?▼

Validate a refactor report by running cross-finding regression checks to confirm all findings are resolved without new issues, executing the test suite for affected modules, and updating pattern compliance tables.

What is cross-finding regression checking in refactoring?▼

Cross-finding regression checking is a validation process that verifies all findings identified in a refactor report are fully resolved without introducing new issues into the software pipeline.

How do I archive completed refactor reports automatically?▼

Archive completed refactor reports by moving them to a dedicated archive directory after confirming all findings are resolved, tests pass, and pattern compliance is updated, finalizing the pipeline cycle.

Do I need a test suite to validate refactored code?▼

Yes, a test suite is required to validate refactored code. The validation process runs the full test suite for affected modules to report pass and fail counts, ensuring code quality post-implementation.

What's the best way to track deferred items from a refactor report?▼

Track deferred items from a refactor report by extracting them into a persistent backlog during the validation process, ensuring future reference for unresolved issues without blocking the current pipeline completion.

Can I update pattern compliance tables after refactoring?▼

Yes, you can update pattern compliance tables after refactoring. The validation process automatically updates these tables to reflect which code quality issues have been successfully resolved post-implementation.