refactor — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited refactor (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
This skill is invoked when the user wants to create a refactoring request. Walk through the steps below. Some steps may be skipped if you consider them unnecessary.
<refactor>
The problem the developer faces, from the developer's perspective.
The solution to the problem from the developer's perspective.
A LONG, detailed implementation plan. Write the plan in plain English, breaking the implementation into the tiniest possible commits. Each commit must leave the codebase in a working state.
A list of accepted implementation decisions. This may include:
Do NOT include concrete file paths or code snippets. They can become stale very quickly.
A list of accepted testing decisions. Include:
A description of what is outside the scope of this refactor.
Any additional notes about the refactor.
</refactor>
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.