Skills request-refactor-plan

📦

request-refactor-plan

Name: request-refactor-plan
Author: mattpocock

Content revision r2 Safe

Plan a Safe, Incremental Refactor

Large refactors often fail because scope, testing, and sequencing remain unclear. This skill inspects the repository and creates an incremental plan for a GitHub issue.

Supports: Claude Codex Code(CC)

🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "request-refactor-plan" from https://skillstore.io/skills/mattpocock-request-refactor-plan.md and its manifest at https://skillstore.io/api/skills/mattpocock-request-refactor-plan/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.

Markdown detail GET /skills/mattpocock-request-refactor-plan.md Signed manifest GET /api/skills/mattpocock-request-refactor-plan/manifest Signed lockfile GET /api/skills/mattpocock-request-refactor-plan/lockfile

Test it

Using "request-refactor-plan". Replace duplicated authorization checks with a shared policy service while preserving current behavior.

Expected outcome:

Problem Statement: Authorization rules are duplicated and can diverge.
Solution: Introduce one policy boundary without changing public behavior.
Commits: Capture behavior tests, add the policy service, migrate one caller per commit, then remove duplication.
Out of Scope: New roles, permission redesign, and unrelated endpoint changes.

Using "request-refactor-plan". Separate billing logic from the web controller and improve its test coverage.

Expected outcome:

Decision Document: Preserve controller contracts and move billing decisions behind a focused service interface.
Testing Decisions: Protect observable billing outcomes with service and request tests.
Commits: Add characterization tests, extract calculations, extract persistence coordination, switch the controller, and remove obsolete helpers.

Security Audit

Safe

v5 • 7/23/2026 Open versioned report

No static findings required adjudication, and review of SKILL.md found no prompt injection or malicious intent. The prompt-only workflow contains no executable code or hidden security-sensitive behavior.

Files scanned

Lines analyzed

Review items

False positives ignored

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

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.

Open versioned report

Copy report link

https://skillstore.io/skills/mattpocock-request-refactor-plan/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/mattpocock-request-refactor-plan/security.svg)](https://skillstore.io/skills/mattpocock-request-refactor-plan?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/mattpocock-request-refactor-plan?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/mattpocock-request-refactor-plan/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/mattpocock-request-refactor-plan.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

mattpocock. (2026). request-refactor-plan security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/mattpocock-request-refactor-plan/audits/5

BibTeX citation

@techreport{mattpocock-mattpocock-request-refactor-plan-2026,
  author = {mattpocock},
  title = {request-refactor-plan security audit report (audit version 5)},
  institution = {Skillstore},
  year = {2026},
  number = {5},
  url = {https://skillstore.io/skills/mattpocock-request-refactor-plan/audits/5},
  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: "request-refactor-plan security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
  - name: "mattpocock"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/mattpocock-request-refactor-plan/audits/5"
identifiers:
  - type: other
    value: "skillstore:mattpocock-request-refactor-plan:audit:5"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Plan a Legacy Module Refactor

Convert an unclear cleanup request into scoped, testable commits that keep the application working.

Prepare an Architecture RFC

Compare solution options and document interfaces, contracts, schema changes, and excluded work.

Review Refactor Readiness

Identify unresolved decisions, testing gaps, and sequencing risks before work enters the sprint.

Try These Prompts

Create a Basic Refactor Plan

Plan a refactor for [component]. The problem is [problem]. Ask me for missing context before proposing commits.

Scope a Refactor

Review [repository area]. Verify [assumptions], compare alternatives, and define in-scope and out-of-scope work before creating the plan.

Design a Test-Aware Sequence

Assess test coverage for [area], identify behavior to protect, and create tiny commits where every step leaves the codebase working.

Prepare a Refactoring RFC

Develop a GitHub issue for [refactor], covering decisions, interfaces, contracts, migrations, tests, commit sequence, exclusions, and unresolved questions.

Best Practices

Provide the business problem, known constraints, and attempted solutions before repository exploration.
Answer implementation questions with concrete examples and identify decisions that remain uncertain.
Review the complete plan and confirm the destination repository before creating the GitHub issue.

Avoid

Do not begin with a predetermined solution while withholding relevant constraints.
Do not combine behavior changes, migrations, and cleanup into one large commit.
Do not publish the issue before confirming scope, testing decisions, and excluded work.

Frequently Asked Questions

Does this skill modify code?

No. It analyzes the repository and produces a refactor plan, but it does not implement changes.

Will it create a GitHub issue?

Yes, when GitHub access is available. Review the proposed content and repository destination before publication.

Why does the skill ask many questions?

The interview resolves scope, constraints, alternatives, interfaces, testing expectations, and implementation decisions before sequencing work.

How small are the planned commits?

Each commit should represent one understandable step and leave the codebase in a working state.

Does the final issue include file paths?

No. The template excludes file paths and code snippets because they can become outdated.

Can it plan a refactor without tests?

It can, but it will identify missing coverage and ask how the affected behavior should be protected.

Developer Details

Author

mattpocock

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/mattpocock/skills/tree/main/skills/deprecated/request-refactor-plan/

Ref

ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006

Maintenance freshness

7/25/2026

Usage

8 downloads · 0 views

File structure

📄 SKILL.md