refactor-probe

Identify tech debt themes and refactoring opportunities across a codebase.

1|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/dev32-io/ccToolBox --skill refactor-probe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refactor-probe
Source: https://github.com/dev32-io/ccToolBox/tree/main/plugins/offline-research/skills/refactor-probe
Command: npx skills add https://github.com/dev32-io/ccToolBox --skill refactor-probe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Explore codebase tech debt and refactoring ideas through structured experimentation and collaborative refinement, enabling safer and measurable improvements.

Core Features & Use Cases

Guide freeform tech debt discovery, structured problem framing, rubric co-design, and PoC seed generation across a project using a staged workflow: Intake, Quick Survey, Assessment + Refinement, Rubric Co-Design, and Seed Generation.

Quick Start

Provide a guided workflow to intake the codebase, survey patterns, design a scoring rubric, and generate seed PoC files that can be iterated with the user.

Frequently Asked Questions about refactor-probe

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

FAQPage Schema
How do I identify tech debt and refactoring opportunities in my codebase?

To identify tech debt and refactoring opportunities, use a structured exploration workflow that surveys codebase patterns like module boundaries and test coverage, assesses findings, and generates traceable PoC seed files for safer improvements.

What is rubric co-design for codebase refactoring?

Rubric co-design for codebase refactoring is a collaborative refinement stage where you create a structured scoring system to evaluate tech debt themes, ensuring measurable and safer improvements through guided assessment before generating PoC seeds.

Can I use a structured probe to refactor code without disrupting existing behavior?

Yes, you can use a structured probe to refactor code without disrupting existing behavior by applying intake and quick survey stages that avoid disruptive actions, preserving functionality while surfacing tech debt themes and PoC seed files.

What's the best way to generate PoC seed files for tech debt resolution?

The best way to generate PoC seed files for tech debt resolution is through a staged workflow encompassing intake, survey, assessment, and rubric co-design, which produces traceable seed files adaptable to patterns like authentication and module boundaries.

When should I not use a structured probe for codebase refactoring?

You should avoid using a structured probe for codebase refactoring when immediate disruptive code changes are required, as the probe prioritizes safe execution, robust rubric design, and preserving existing behavior over rapid, unchecked modifications.