safe-refactor-80d406 100/100

Is safe-refactor-80d406 safe to install?

SaferSkills independently audited safe-refactor-80d406 (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.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

plugins/codebase-maintenance/skills/safe-refactor/SKILL.md · 1 file

plugins/codebase-maintenance/skills/safe-refactor/SKILL.md1.9 KB · Markdown

name: safe-refactor

description: Use when code needs restructuring without changing observable behavior.

Purpose

Restructure code in small, safe steps while preserving all externally observable behavior. Prevents refactor regressions where behavior silently changes.

When to Use

Code needs structural improvement but its public API must remain unchanged.
Naming, organization, or duplication needs cleanup after a feature is complete.
Technical debt needs reduction without introducing risk.

Do not use this skill if there are no existing tests — write tests first.

Inputs

Code to refactor.
Existing test suite (required).
Optional: specific goals (extract function, rename module, remove duplication).

Workflow

Confirm behavior — Run the test suite. All tests must pass before starting.
Plan — List the structural changes. Check each for API impact.
Refactor in small steps — One change at a time, each independently reversible.
Avoid interface changes — Do not alter public APIs, exported types, or CLI behavior unless explicitly intended.
Validate after each step — Re-run targeted tests after each meaningful change.

Output

Changed:
- <structural change 1>
- <structural change 2>

Behavior unchanged because: <reasoning>

Validated by: <test commands run>

Verification

[ ] Tests pass before starting
[ ] Each step is small and independently reversible
[ ] No unintended API or interface changes introduced
[ ] Tests pass after each meaningful step
[ ] Final test suite fully green

Failure Modes

Missing tests — Stop. Write tests before refactoring. Behavior cannot be verified otherwise.
Silent API change — If a refactor touches public interfaces, stop and confirm this is intentional.
Bundled unrelated changes — Keep each step focused. Mixed changes make rollback and blame impossible.

safe-refactor-80d406— agent skill

Is safe-refactor-80d406 safe to install?

Purpose

When to Use

Inputs

Workflow

Output

Verification

Failure Modes

Audit the pieces. Scan the whole. Decide.