Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From frontend-skills
DEPRECATED. Guides creation of GitHub issues for refactoring plans with problem/solution, commits, and decisions. Only triggers on explicit `/request-refactor-plan`.
npx claudepluginhub redpanda-data/ui-harness --plugin frontend-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/frontend-skills:request-refactor-planThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> Deprecated: prefer replacement named in description. Keep only for backward compatibility.
Creates structured, incremental refactoring plans broken into tiny working commits. Use when planning a refactor or breaking down large changes.
Interviews the user to create a detailed, incremental refactor plan and files it as a GitHub issue. Useful for scoping safe, step-by-step refactoring work.
Plans structural refactors as ordered, commit-grain tasks with test-suite-green-at-every-step acceptance criteria. Use for extractions, renames, dependency-inversion, or any no-behaviour-change improvement.
Share bugs, ideas, or general feedback.
Deprecated: prefer replacement named in description. Keep only for backward compatibility.
Ask problem + solution ideas. What wrong? What "better" mean?
Agent(subagent_type=Explore) verify claims vs codebase. Check real state.
Ask other approaches + trade-offs.
Scope, interface contracts (before/after), data migrations, backcompat, incremental path.
Assess coverage. Insufficient -> ask test plan first.
Each step: deployable alone, tests green, one change.
gh issue create:
## Problem Statement
What wrong and why.
## Solution
Chosen approach and rationale.
## Commits
1. [description] -- what changes, tests green
2. [description] -- what changes, tests green
## Decisions
Key decisions + rationale from interview.
## Testing
New tests needed, existing tests changed.
## Out of Scope
What NOT touched.