skill-ao92265-claude-code-playbook-refactor · by Install
$ agentstack add skill-ao92265-claude-code-playbook-refactor ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-ao92265-claude-code-playbook-refactor) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Focused Refactor
Improve code structure without changing behavior. Zero behavior change is non-negotiable.
Steps
- Establish green baseline:
- Run the full test suite and confirm all tests pass
- Run the type checker (
tsc --noEmit,go vet,cargo check,mypy) - If tests don't exist for the code being refactored, stop and suggest using
/test-first - Record the test results as the baseline
- Identify the refactoring:
- Clarify what the user wants to improve (or suggest based on code smells)
- Common refactorings: rename, extract function/method, inline, simplify conditionals,
remove duplication, split file, consolidate imports
- Scope the change — one refactoring at a time
- Apply the refactoring:
- Make the minimum changes necessary
- Update all references (imports, call sites, type definitions)
- Preserve all public API contracts
- Don't change test assertions — tests are the behavior contract
- Verify behavior is preserved:
- Run the full test suite again
- Run the type checker again
- Compare results to baseline — must be identical pass/fail
- If tests fail — revert immediately:
git checkout -- .to discard changes- Analyze why the refactoring broke tests
- Try a different, safer approach
- Never fix tests to accommodate refactoring — that means behavior changed
- Final checks:
- Run linter to confirm no new warnings
- Show the diff summary to the user
- Confirm the refactoring achieved the intended improvement
Important
- Zero behavior change is the rule. If any test fails after refactoring, revert. No exceptions.
- Don't combine refactoring with feature work. Refactor in one commit, features in another.
- Tests are the contract. If you need to change tests, you're not refactoring — you're changing behavior.
- One refactoring per pass. Don't rename AND extract AND simplify in one go.
- If no tests exist, stop. Refactoring without tests is guessing. Write tests first.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ao92265
- Source: ao92265/claude-code-playbook
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.