refactor-with-tests
Use when splitting files, improving architecture, reducing duplication, changing internals, or preserving behavior through focused tests during refactors.
- License 许可
- MIT
- 最近更新
- 2026-05-04
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- refactor-with-tests
- metadata
- { "internal": true }
- description
- Use when splitting files, improving architecture, reducing duplication, changing internals, or preserving behavior through focused tests during refactors.
03 SKILL.md 正文
Refactor With Tests
Workflow
- Identify the exact behavior to preserve.
- Add or locate tests that cover the behavior.
- Make the smallest useful refactor.
- Run relevant tests and typecheck.
- Update docs only when behavior, architecture, or setup changes.
- Summarize changed files and validation.
Guardrails
- Do not combine unrelated refactors.
- Do not rename public APIs without an explicit migration reason.
- Do not weaken validation, auth, error handling, or observability to simplify code.
- Preserve user changes in a dirty worktree.
04 同仓库更多 Skills
dangerous-helper
Unsafe fixture skill for supply-chain audit tests.
benign-helper
Safe fixture skill for supply-chain audit tests.
skill-supply-chain-auditor
Use when reviewing installed skills, adding third-party skills, hardening agent workflows, checking skill correctness, removing duplicate skills, or investigating supply-chain, prompt-injection, secret-leakage, dependency-install, webhook, destructive-shell, manifest-quality, or resource-discovery risks.
python-mcp-server-quality
Use when creating, auditing, or improving Python MCP servers, FastMCP tools, resources, prompts, stdio transports, streamable HTTP transports, MCP Inspector setup, or Python tool schemas.
python-backend-quality
Use when reviewing, creating, or improving Python services, CLIs, libraries, FastAPI, Django, Flask, pytest, uv, pyproject, typing, Pydantic, SQLAlchemy, async code, packaging, or deployment.
official-docs-grounding
Use when current framework, SDK, API, MCP, cloud, security, or version-specific behavior matters and implementation decisions need official documentation grounding.