القائمة
Use when refactoring code - tracks the refactor in task docs and preserves behavior through small verified changes
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | refactoring-safely |
| description | Use when refactoring code - tracks the refactor in task docs and preserves behavior through small verified changes |
<skill_overview> Refactor in small truth-preserving steps. Keep the refactor tracked in task docs and stop if behavior starts drifting. </skill_overview>
<rigidity_level> MEDIUM FREEDOM - Keep the change→test→document loop strict, but adapt the exact refactor pattern to the codebase. </rigidity_level>
<quick_reference>
plan.mdcontext.md and tasks.md
</quick_reference><when_to_use>
<the_process>
Use task docs to capture:
Each step should be small enough to explain and verify on its own.
Run the smallest relevant tests after each change.
Update discoveries, remaining risks, and next slices as the refactor unfolds. </the_process>
Use when shaping a feature before implementation - turns rough ideas into an approved markdown spec and local task directory
Use to execute an approved local markdown task directory iteratively - work the current Now slice, update docs, then stop
Use when implementation is complete and verified - delete finished local task docs, present integration options, and clean up safely
Use for advanced markdown task-doc operations - split work, reprioritize slices, delete finished local task dirs, and keep docs clean
Use after executing a task directory - verifies implementation against plan.md, acceptance checks, and anti-goals
Use when starting any conversation - establishes skill selection and the local task-doc workflow