li3p/refactor-safe
skills/refactor-safe/SKILL.md
Refactor internal implementation without changing public API or behavior. Use when improving structure, readability, duplication, or complexity while preserving exported signatures, return shapes, errors, and tests.
development
Updated Apr 23, 2026
$ install --global
skillsauthnpx skillsauth add li3p/skills refactor-safeInstall 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: Apr 23, 2026, 11:10 PM42.6s1 file scanned
SKILL.md
- name:
- refactor-safe
- description:
- Refactor internal implementation without changing public API or behavior. Use when improving structure, readability, duplication, or complexity while preserving exported signatures, return shapes, errors, and tests.
Refactor Safe
Refactor the internals of: $ARGUMENTS
Hard Constraints
- Preserve exported names, signatures, types, and return shapes.
- Preserve public routes, CLI flags, schemas, events, and config keys.
- Preserve error messages and edge-case behavior unless the user explicitly approves a behavior change.
- Do not add dependencies.
- Do not mix unrelated cleanup into the refactor.
- Do not rewrite working code into a different architecture without a clear local pattern and user need.
Preferred Improvements
Use small, local changes:
- extract private helpers for repeated or nested logic
- simplify branches with clear guard clauses
- name intermediate values when it reduces mental load
- isolate validation, transformation, side effects, and formatting
- remove unreachable code only when clearly proven
- replace magic literals with local constants when it clarifies intent
Verification
After editing, verify:
- Public API is unchanged.
- Existing tests still represent the same behavior.
- No new dependencies or broad file churn were introduced.
- The refactor is easier to review than the original.
Run the relevant tests when feasible. Summarize what changed and what was verified.
Related Skills
li3p/notion-search
documentation
VerifiedTrustedCommunity
Search Notion for pages or databases by query using marknotion. Use when the user references a Notion page by name rather than URL, when locating a page to publish to or pull from, or when discovering what trackers and docs exist in the connected workspace.
SKILL.mdUpdated May 27, 2026
li3p/notion-pull
documentation
VerifiedTrustedCommunity
Export a Notion page to local Markdown using marknotion. Use when the user wants to pull a spec, design doc, meeting notes, or any Notion page into the repository as a Markdown file, or wants to read Notion content as context for a task.
SKILL.mdUpdated May 27, 2026
li3p/notion-publish
documentation
VerifiedTrustedCommunity
Publish a local Markdown file to a Notion page using marknotion. Use when the user wants to push README, docs, changelogs, or any Markdown content to Notion, either updating an existing page or creating a new one under a parent page.
SKILL.mdUpdated May 27, 2026
li3p/testmatch
testing
VerifiedTrustedCommunity
Generate tests that match an existing project's testing style. Use when adding coverage for a target file, function, bug fix, or edge case while preserving local conventions.
SKILL.mdUpdated Apr 23, 2026