00PrabalK00/refactor-without-breaking-behavior
skills/refactor-without-breaking-behavior/SKILL.md
Plan and execute behavior-preserving refactors by identifying safe structural changes, staging edits incrementally, adding regression coverage, and validating outcomes. Use for legacy cleanup, module extraction, renames, or simplification where behavior must stay the same.
development
Updated Mar 23, 2026
$ install --global
skillsauthnpx skillsauth add 00PrabalK00/claude-skills refactor-without-breaking-behaviorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
70%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 24, 2026, 12:58 AM185.2s2 files scanned
SKILL.md
- name:
- refactor-without-breaking-behavior
- description:
- Plan and execute behavior-preserving refactors by identifying safe structural changes, staging edits incrementally, adding regression coverage, and validating outcomes. Use for legacy cleanup, module extraction, renames, or simplification where behavior must stay the same.
Refactor Without Breaking Behavior
Overview
Favor disciplined cleanup over clever rewrites.
Core Workflow
- Establish the current behavior from tests, docs, logs, or direct inspection.
- Choose a safe seam for change: extraction, rename, split, dedupe, or dead-code removal.
- Add characterization or regression tests before touching risky code when coverage is weak.
- Refactor in small, reviewable steps and validate after each meaningful change.
- Summarize what changed structurally and why behavior should remain the same.
Deliver
- Produce an incremental refactor plan when the code is especially messy.
- Add or update tests that protect the existing behavior.
- Call out any incidental bug fixes separately from the refactor itself.
Guardrails
- Do not change public behavior unless the user explicitly asks for it.
- Prefer extraction and simplification over broad rewrites.
- Stop and surface the tradeoff if the safest path requires larger architectural movement.
Related Skills
00PrabalK00/vendor-evaluation-scorecard
tools
VerifiedTrustedCommunity
Compare vendors or tools using weighted criteria, tradeoffs, risks, and recommendation logic. Use when selecting platforms or partners.
SKILL.mdUpdated Mar 23, 2026
00PrabalK00/user-interview-synthesizer
data-ai
VerifiedTrustedCommunity
Extract needs, pain points, quotes, and behavioral patterns from user interviews. Use when synthesizing qualitative research.
SKILL.mdUpdated Mar 23, 2026
00PrabalK00/user-feedback-clusterer
databases
VerifiedTrustedCommunity
Group user feedback into themes, bugs, requests, sentiment, and confusion points. Use when analyzing feedback corpora.
SKILL.mdUpdated Mar 23, 2026
00PrabalK00/test-writer-coverage-closer
testing
VerifiedTrustedCommunity
Find missing coverage, design useful unit or integration tests, add fixtures or mocks, and explain remaining edge cases. Use when a feature lacks tests, a bug needs regression coverage, or coverage gaps block confidence.
SKILL.mdUpdated Mar 23, 2026