characterization-testing
Create tests that describe what legacy code actually does (not what it should do) as safety net before refactoring
Explorez les skills IA publiés de spacholski1225 et consultez leurs instructions source.
Skills indexés
13Étoiles des dépôts des skills indexés
26Forks du dépôt
0Moyenne des étoiles par skill indexé
2Les étoiles d’un dépôt peuvent se répéter entre ses skills.
Create tests that describe what legacy code actually does (not what it should do) as safety net before refactoring
Skills for legacy code analysis, explanation, and safe refactoring - mandatory workflows and search tools
Map dependencies and coupling in legacy codebase to understand what breaks when you change something and identify refactoring risks
Safely replace legacy system piece by piece by building new implementation around it, routing traffic gradually, like a strangler fig tree
Systematic techniques for reading and understanding unfamiliar legacy code without documentation
Transform markdown notes into engaging technical blog posts for both programmers and non-technical readers
Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context
TDD for process documentation - test with subagents before writing, iterate until bulletproof
Creating documentation from legacy code when none exists, focusing on what future maintainers need to know
RED-GREEN-REFACTOR for process documentation - baseline without skill, write addressing failures, iterate closing loopholes
Execute detailed plans in batches with review checkpoints
Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.
Write the test first, watch it fail, write minimal code to pass
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.