Menu
Safe code refactoring workflow focused on behavior preservation and strict testing
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Execute security scanning commands on remote worker agents. Use when you need to run CLI tools like nmap, subfinder, httpx, nuclei, or any shell command on worker nodes.
Perform deep analysis of CVEs and security vulnerabilities including CVSS scoring, affected versions, exploit maturity, and remediation steps. Use when the user needs detailed vulnerability intelligence.
Perform web research using CVE databases, security advisories, and threat intelligence sources. Use when the user asks about CVEs, security news, vulnerabilities, patch releases, or any external security information not available in the workspace.
Workflow for committing code with comprehensive validation from linting to deployment
Workflow for API development and modification with strict checks from design to deployment
Workflow for creating and submitting bug reports to GitHub
| name | refactor |
| description | Safe code refactoring workflow focused on behavior preservation and strict testing |
Use this when improving internal code quality (readability, maintainability, structure, typing) without changing external behavior. Not for feature development or bug fixes — if logic must change, create a separate PR.
Define scope: list files, functions, classes, modules being refactored. Identify code smells: duplicated logic, large functions, unclear naming, tight coupling, weak typing. Impact analysis: trace callers, dependencies, public APIs. Highlight high-risk areas (auth, money, state, async, concurrency). Strategy: select 1–2 techniques per iteration (extract functions, rename, simplify control flow, improve boundaries, improve typing).
Test existence gate: every service file being refactored must have a corresponding test file. If none exists, tests must be added first describing current behavior exactly. Refactoring is forbidden until these tests pass.
Establish baseline: run all related tests before modifying code. All must pass. If any fail, stop and handle separately.
Per-step safety checklist:
Run tests frequently during refactoring. After completion, run full test suite. Do not skip tests or update snapshots just to make tests pass.
# Backend
cd core-api && npx eslint src/path/to/modified/files.ts
# Frontend
cd console && npx eslint src/path/to/modified/files.tsx
Zero errors, zero warnings.
# Backend
cd core-api && npm run test
# Frontend
cd console && npm run test
Confirm no regressions and no performance degradation.
Update English comments if structure changes. Do not add comments describing new behavior.