New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Request Refactor Plan

by fossasia in fossasia/eventyay-interpretation

Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue.

Apache-2.0Auto-check passedDevelopment

Install Request Refactor Plan

skills CLI
$ npx skills add fossasia/eventyay-interpretation --skill request-refactor-plan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install fossasia/eventyay-interpretation request-refactor-plan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/fossasia/eventyay-interpretation.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/request-refactor-plan .claude/skills/request-refactor-plan && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
request-refactor-plan
GitHub stars
1.6k
Used in
10 other repos
Token cost
~678 tokens
SKILL.md length
381 words
Files
1
Skills in repo
41
Repo updated
First seen
Licence
Apache-2.0

At a glance

Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue.

  • Works in 8 steps: Ask the user for a long, detailed… → Explore the repo to verify their… → Ask whether they have considered other… → …
  • User wants to plan a refactor
  • SKILL.md covers Problem Statement, Solution, Commits and Decision Document, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Request Refactor Plan is an agent skill from fossasia/eventyay-interpretation. Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.

Its SKILL.md is about 680 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Refactoring and User research. It works with GitHub. The repository describes itself as: A plugin for live interpretation of video streams. The licence is Apache-2.0.

When your agent uses it

  • User wants to plan a refactor
  • Create a refactoring RFC
  • Break a refactor into safe incremental steps

Example prompts

  • “/request-refactor-plan”

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions.
  2. Explore the repo to verify their assertions and understand the current state of the codebase.
  3. Ask whether they have considered other options, and present other options to them.
  4. Interview the user about the implementation. Be extremely detailed and thorough.
  5. Hammer out the exact scope of the implementation. Work out what you plan to change and what you plan not to change.
  6. Look in the codebase to check for test coverage of this area of the codebase. If there is insufficient test coverage, ask the user what…
  7. Break the implementation into a plan of tiny commits. Remember Martin Fowler's advice to "make each refactoring step as small as possible…
  8. Create a GitHub issue with the refactor plan. Use the following template for the issue description

What it can do on your machine

Read from SKILL.md and the folder at commit 1ca0139. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Request Refactor Plan loads about 678 tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 381 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~678

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from fossasia/eventyay-interpretation at commit 1ca0139, republished under its Apache-2.0 licence (© fossasia). 381 words, ~678 tokens.

Download SKILL.mdSave it as .claude/skills/request-refactor-plan/SKILL.md (or your agent's skills folder).
name
request-refactor-plan
description
Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.

This skill will be invoked when the user wants to create a refactor request. You should go through the steps below. You may skip steps if you don't consider them necessary.

  1. Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions.

  2. Explore the repo to verify their assertions and understand the current state of the codebase.

  3. Ask whether they have considered other options, and present other options to them.

  4. Interview the user about the implementation. Be extremely detailed and thorough.

  5. Hammer out the exact scope of the implementation. Work out what you plan to change and what you plan not to change.

  6. Look in the codebase to check for test coverage of this area of the codebase. If there is insufficient test coverage, ask the user what their plans for testing are.

  7. Break the implementation into a plan of tiny commits. Remember Martin Fowler's advice to "make each refactoring step as small as possible, so that you can always see the program working."

  8. Create a GitHub issue with the refactor plan. Use the following template for the issue description:

<refactor-plan-template>

Problem Statement

The problem that the developer is facing, from the developer's perspective.

Solution

The solution to the problem, from the developer's perspective.

Show full SKILL.md (159 more words)Show less

Commits

A LONG, detailed implementation plan. Write the plan in plain English, breaking down the implementation into the tiniest commits possible. Each commit should leave the codebase in a working state.

Decision Document

A list of implementation decisions that were made. This can include:

  • The modules that will be built/modified
  • The interfaces of those modules that will be modified
  • Technical clarifications from the developer
  • Architectural decisions
  • Schema changes
  • API contracts
  • Specific interactions

Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.

Testing Decisions

A list of testing decisions that were made. Include:

  • A description of what makes a good test (only test external behavior, not implementation details)
  • Which modules will be tested
  • Prior art for the tests (i.e. similar types of tests in the codebase)

Out of Scope

A description of the things that are out of scope for this refactor.

Further Notes (optional)

Any further notes about the refactor.

</refactor-plan-template>

© fossasia, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/request-refactor-plan of fossasia/eventyay-interpretation.

Open the folder on GitHubat commit 1ca0139

Used in 11 other repositories

We found 14 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 10 other GitHub owners. This page covers the copy in fossasia/eventyay-interpretation, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Request Refactor Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Request Refactor Plan compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Request Refactor Plan this skillfossasia/eventyay-interpretation1.6k10 repos~678Automated safety check: PassApache-2.0
Valgocohesivestack/valgo508—~2.4kAutomated safety check: PassMIT
Rust Hygiene Audittsz-org/tsz572—~1.5kAutomated safety check: PassApache-2.0
iOS FixMacMagazine/app-iOS171—~957Automated safety check: PassNone
External Contributor Issuesaxelixlabs/axelix147—~2.2kAutomated safety check: PassLGPL-3.0
Refactor AnalysisSamsung/TizenFX214—~2.6kAutomated safety check: PassApache-2.0

Similar skills

  • Valgo

    cohesivestack/valgo

    Add, refactor, debug, review, explain, or migrate type-safe validation in consumer Go applications using github.com/cohesivestack/valgo.

    508 GitHub stars~2.4k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Rust Hygiene Audit

    tsz-org/tsz

    Run a deep DRY + code-hygiene audit of the Rust workspace and turn the findings into verified, deduplicated, hierarchical GitHub tech-debt issues.

    572 GitHub stars~1.5k tokensUpdated 27 days ago
    DevelopmentAuto-check passed

  • iOS Fix

    MacMagazine/app-iOS

    Bug-fix and refactoring workflow for MacMagazine — root cause analysis, pattern-matching fix, regression verification.

    171 GitHub stars~957 tokensUpdated today
    DevelopmentAuto-check passed

  • External Contributor Issues

    axelixlabs/axelix

    Pick open GitHub issues in the Axelix monorepo that are suitable for unpaid volunteer contributors working in their spare time.

    147 GitHub stars~2.2k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Refactor Analysis

    Samsung/TizenFX

    Automatically scans the TizenFX codebase on a rotating schedule to discover .NET 8 / C 12+ refactoring targets and register them as GitHub Issues.

    214 GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed

  • Deepchat Sdd

    ThinkInAIXYZ/deepchat

    Use before substantial DeepChat code, configuration, documentation, test, build, feature, issue, refactor, or architecture changes that need a durable RFC and an explicit execution path.

    6.4k GitHub stars~2.2k tokensUpdated 4 days ago
    DevelopmentAuto-check passed

More from fossasia/eventyay-interpretation

All 41 skills in this repo

  • Git Guardrails Claude Code

    fossasia/eventyay-interpretation

    Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute.

    1.6k GitHub starsUsed in 12 repos~578 tokens
    Auto-check passed

  • Codebase Design

    fossasia/eventyay-interpretation

    Shared vocabulary for designing deep modules. An agent skill from fossasia/eventyay-interpretation.

    1.6k GitHub starsUsed in 35 repos~1.5k tokens
    Auto-check passed

  • Diagnosing Bugs

    fossasia/eventyay-interpretation

    Diagnosis loop for hard bugs and performance regressions. An agent skill from fossasia/eventyay-interpretation.

    1.6k GitHub starsUsed in 31 repos~2.1k tokens
    Auto-check passed

  • Domain Modeling

    fossasia/eventyay-interpretation

    Build and sharpen a project's domain model. An agent skill from fossasia/eventyay-interpretation.

    1.6k GitHub starsUsed in 29 repos~821 tokens
    Auto-check passed

  • TDD

    fossasia/eventyay-interpretation

    Test-driven development. An agent skill from fossasia/eventyay-interpretation.

    1.6k GitHub starsUsed in 28 repos~1.1k tokens
    Auto-check passed

  • Improve

    fossasia/eventyay-interpretation

    Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute.

    1.6k GitHub starsUsed in 10 repos~3.7k tokens
    Auto-check: warnings

Works with

Categories

Questions about Request Refactor Plan

What does Request Refactor Plan do?

Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Request Refactor Plan is an agent skill from fossasia/eventyay-interpretation. Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue.

When should I use Request Refactor Plan?

Request Refactor Plan fits situations like: user wants to plan a refactor; create a refactoring RFC; break a refactor into safe incremental steps.

How do I install Request Refactor Plan in Claude Code?

Run `npx skills add fossasia/eventyay-interpretation --skill request-refactor-plan -a claude-code`. Or copy the skill folder (.agents/skills/request-refactor-plan in fossasia/eventyay-interpretation) into .claude/skills/request-refactor-plan in your project. Claude Code loads it when a task matches its description.

How do I install Request Refactor Plan in Codex?

Run `npx skills add fossasia/eventyay-interpretation --skill request-refactor-plan -a codex`. Or copy the skill folder (.agents/skills/request-refactor-plan in fossasia/eventyay-interpretation) into .agents/skills/request-refactor-plan in your project. Codex loads it when a task matches its description.

Can I use Request Refactor Plan in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add fossasia/eventyay-interpretation --skill request-refactor-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/request-refactor-plan, .gemini/skills/request-refactor-plan, .github/skills/request-refactor-plan and .opencode/skills/request-refactor-plan in your project.

What does Request Refactor Plan need to run?

SKILL.md names no scripts, command-line tools or credentials: Request Refactor Plan is instructions for the agent only.

Does Request Refactor Plan access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Request Refactor Plan safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Request Refactor Plan use?

Request Refactor Plan is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Request Refactor Plan use?

About 678 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Request Refactor Plan?

Skills that share tags, products or a category with Request Refactor Plan: Valgo (cohesivestack/valgo, 508 stars), Rust Hygiene Audit (tsz-org/tsz, 572 stars), iOS Fix (MacMagazine/app-iOS, 171 stars) and External Contributor Issues (axelixlabs/axelix, 147 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Request Refactor Plan?

fossasia (a GitHub organization) maintains it in fossasia/eventyay-interpretation, which has 1,552 GitHub stars. The repository holds 41 skills in this directory. The repository was last updated on October 5, 2026.

Source: fossasia/eventyay-interpretation on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.