alexei-led/refactoring-code
plugins/dev-workflow/skills-pi/refactoring-code/SKILL.md
Behavior-preserving refactoring in Pi using local search, edit, tests, and disciplined batching. Use when the user asks to refactor code without changing behavior.
$ install --global
skillsauthnpx skillsauth add alexei-led/claude-code-config refactoring-codeInstall 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
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 11, 2026, 4:36 AM120.0s1 file scanned
SKILL.md
- description:
- Behavior-preserving refactoring in Pi using local search, edit, tests,
- name:
- refactoring-code
<!-- generated by scripts/build/generate-skills.py — edits to this file will be overwritten by `make build`. Edit the canonical SKILL.md (or add a SKILL.codex.md / SKILL.pi.md sidecar to diverge). -->
<!-- Pi platform guidance -->
<!-- Use Pi tool names exactly: read, bash, edit, write, ask_user_question, structured_output, todo, Agent, get_subagent_result, steer_subagent, web_search, web_answer, web_research. -->
<!-- Use Agent, get_subagent_result, and steer_subagent for delegated work. -->
<!-- Use ctx7 or npx ctx7@latest through bash when Context7 documentation lookup is required. -->
Refactoring Code in Pi
Refactor in small, verified batches. If behavior changes, it is not a refactor; it is a feature wearing a fake mustache.
Preconditions
- Understand the current behavior and test coverage.
- Identify the smallest safe batch.
- Run or add tests before broad edits when risk is non-trivial.
- Confirm before large mechanical changes across many files.
Workflow
- Define the refactor goal and non-goals.
- Use
rgandfdto find all affected sites. - Read representative files and tests.
- Add characterization tests when behavior is under-specified.
- Apply one coherent batch with
editorwrite. - Run narrow tests.
- Run broader lint/type/test checks before the next batch.
- Delete dead code introduced or exposed by the refactor.
Safe Batches
Good batches:
- rename one public symbol and all callers
- move one function/module with tests unchanged
- extract one adapter or seam with existing behavior preserved
- remove one duplicate implementation after tests prove equivalence
Bad batches:
- rename everything while changing logic
- reorganize modules and change APIs in one pass
- add abstractions for imagined future callers
- edit generated files by hand
Output Contract
## Refactor Result
### Changed
- `path` — what changed
### Behavior
- preserved by <tests/checks>
### Verification
- `<command>` — pass/fail
### Follow-up
- remaining safe batches, if any
Related Skills
alexei-led/spec-flow
tools
VerifiedTrustedCommunity
Use when planning, executing, checkpointing, finishing, or inspecting lightweight spec-driven work. Runs one task at a time using `.spec/` markdown files and the bundled `specctl` helper. NOT for broad product discovery beyond a short requirement interview. NOT for generic implementation planning that does not read or write `.spec/` files.
35SKILL.mdUpdated Jul 18, 2026
alexei-led/writing-web
development
VerifiedTrustedCommunity
Simple web development with HTML, CSS, JS, and HTMX. Use when working with .html, .css, or .htmx files, web templates, stylesheets, or vanilla JS scripts. NOT for React/Vue/Angular (use writing-typescript) or Node.js backends.
35SKILL.mdUpdated Jul 18, 2026
alexei-led/writing-typescript
tools
VerifiedTrustedCommunity
Idiomatic TypeScript development. Use when writing TypeScript code, Node.js services, React apps, or TypeScript design advice. Emphasizes strict typing, boundary validation, composition, fast feedback, behavior tests, and project-configured tooling. NOT for Go, Python, Rust, plain HTML/CSS/JS, or server-rendered templates (use writing-web).
35SKILL.mdUpdated Jul 18, 2026
alexei-led/writing-shell
tools
VerifiedTrustedCommunity
Idiomatic shell development for POSIX sh, Bash, Zsh, Fish, hooks, CI shell steps, and scriptable CLI glue. Use when writing or changing `.sh`, `.bash`, `.zsh`, `.fish`, `.bats`, shell functions, shell pipelines, CI `run:` shell bodies, or command-runner recipes. Emphasizes portability, quoting, safe filesystem/process handling, non-TUI CLI tools, ShellCheck, shfmt, Bats, and ShellSpec. NOT for Python, Rust, TypeScript, Go, web code, or GitHub Actions workflow/job/permissions semantics; use operating-infra.
35SKILL.mdUpdated Jul 18, 2026