tdd-workflows-tdd-refactor
Refactor Code with TDD Safety
Refactoring can break behavior when tests and measurements are weak. This skill guides incremental TDD refactoring with test baselines, code smell checks, and verification steps.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "tdd-workflows-tdd-refactor" from https://skillstore.io/skills/sickn33-tdd-workflows-tdd-refactor.md and its manifest at https://skillstore.io/api/skills/sickn33-tdd-workflows-tdd-refactor/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "tdd-workflows-tdd-refactor". Refactor a long order processing method with passing tests.
Expected outcome:
A test baseline, an extract-method plan, applied refactor steps, final green test status, and remaining technical debt notes.
Using "tdd-workflows-tdd-refactor". Improve a slow service without changing behavior.
Expected outcome:
A measurement-first plan, likely bottlenecks, proposed data structure changes, regression checks, and before-and-after performance notes.
Using "tdd-workflows-tdd-refactor". Prepare a risky module for a safer pull request.
Expected outcome:
A checklist covering coverage gaps, incremental commits, rollback points, documentation updates, and final reviewer summary.
Security Audit
SafeAll six static alerts are false positives caused by Markdown backticks, TypeScript example code, and testing terminology. I found no prompt injection, exfiltration intent, or unsafe command execution in SKILL.md.
Risk Factors
⚙️ External commands (4)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-tdd-workflows-tdd-refactor/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-tdd-workflows-tdd-refactor?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-tdd-workflows-tdd-refactor?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-tdd-workflows-tdd-refactor/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-tdd-workflows-tdd-refactor.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). tdd-workflows-tdd-refactor security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-tdd-workflows-tdd-refactor/audits/4BibTeX citation
@techreport{sickn33-sickn33-tdd-workflows-tdd-refactor-2026,
author = {sickn33},
title = {tdd-workflows-tdd-refactor security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/sickn33-tdd-workflows-tdd-refactor/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "tdd-workflows-tdd-refactor security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/sickn33-tdd-workflows-tdd-refactor/audits/4"
identifiers:
- type: other
value: "skillstore:sickn33-tdd-workflows-tdd-refactor:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Refactor Legacy Modules
Plan small behavior-preserving changes before changing risky legacy code.
Prepare Safer Pull Requests
Use test baselines, code smell checks, and final verification before review.
Teach Refactor Discipline
Show teams how to separate behavior changes from structure improvements.
Try These Prompts
Review this module and create a TDD refactor plan. Identify tests to run, safe first steps, and expected verification.
Apply the TDD refactor phase to this code. Keep behavior unchanged, make small changes, and report test results after each step.
Analyze this service for code smells, SOLID issues, and performance risks. Propose measured refactors with rollback checkpoints.
Plan a large legacy refactor using branch-by-abstraction or Mikado planning. Map dependencies, verify coverage, and separate behavior changes.
Best Practices
- Start with a green test baseline before changing structure.
- Make one small refactor at a time and verify after each change.
- Measure performance before optimizing algorithms, queries, or caching.
Avoid
- Mixing new behavior with refactoring in the same change.
- Applying design patterns without a clear maintainability benefit.
- Continuing after a failing test without isolating the breaking change.
Frequently Asked Questions
What does this skill help with?
Does it run tests automatically?
Can it choose design patterns?
Is it useful for performance work?
Which tools can use it?
What should I provide?
Developer Details
Author
sickn33License
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Repository
https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/tdd-workflows-tdd-refactorRef
9f814fc6a43fd99946f2da5e0df231c65a38bc76
Maintenance freshness
7/20/2026
Usage
8 downloads · 114 views
File structure
📄 SKILL.md