refactor-safely
Plan and execute safe refactoring using dependency analysis
Works with
--- name: refactor-safely description: Plan and execute safe refactoring using dependency analysis license: MIT --- ## Refactor Safely Use the knowledge graph to plan and execute refactoring with confidence. ### Steps 1. Use `refactor_tool` with mode="suggest" for community-driven refactoring suggestions. 2. Use `refactor_tool` with mode="dead_code" to find unreferenced code. 3. For renames, use `refactor_tool` with mode="rename" to preview all affected locations. 4. Use `apply_refactor_tool` with the refactor_id to apply renames. 5. After changes, run `detect_changes_tool` to verify the refactoring impact. ### Safety Checks - Always preview before applying (rename mode gives you an edit list). - Check `get_impact_radius_tool` before major refactors. - Use `get_affected_flows_tool` to ensure no critical paths are broken. - Run `find_large_functions_tool` to identify decomposition targets. ## Token Efficiency Rules - Start with `get_minimal_context_tool(task="<your task>")` before other graph tools. - Use `detail_level="minimal"` on all calls. Only escalate to "standard" when minimal is insufficient. - Target: complete any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens. - Read the implementation and its tests before changing code. The graph narrows scope; it does not replace the source.
More Refactoring skills
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
analyze-project
lllllllama/rigorpilot-skills
Rigor Analyze / Rigor Audit read-only skill for deep learning research repositories. Use when the user wants to read and understand a repository, inspect model structure and training or inference entrypoints, review configs and insertion points, or flag suspicious implementation patterns without modifying code or running heavy jobs. Do not use for active command execution, broad refactoring, speculative code adaptation, or automatic bug fixing.
request-refactor-plan
mattpocock/skills
Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
