New: 98,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

Refactor For Review

by yokki-vans in yokki-vans/InkPointX

Producing small, single-concern, reviewable changes. An agent skill from yokki-vans/InkPointX.

MITAuto-check passedDevelopment

Install Refactor For Review

skills CLI
$ npx skills add yokki-vans/InkPointX --skill refactor-for-review -a claude-code

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

GitHub CLI
$ gh skill install yokki-vans/InkPointX refactor-for-review --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/yokki-vans/InkPointX.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/refactor-for-review .claude/skills/refactor-for-review && 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
refactor-for-review
GitHub stars
107
Token cost
~791 tokens
SKILL.md length
423 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

Producing small, single-concern, reviewable changes. An agent skill from yokki-vans/InkPointX.

  • Preparing a change for PR
  • SKILL.md covers One concern per change, Keep the diff narrow, Decompose oversized units and Comments earn their place, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Especially in this multi-contributor AI-assisted codebase that is prone to sprawl diffs

What it does

Refactor For Review is an agent skill from yokki-vans/InkPointX. Producing small, single-concern, reviewable changes. Use when refactoring, cleaning up, restructuring, decomposing, or preparing a change for PR, especially in this multi-contributor AI-assisted codebase that is prone to sprawl diffs. Covers one-concern-per-commit, extracting helpers without widening scope, not bundling unrelated edits, decomposing oversized activities, comment hygiene, and a pre-handoff self-review checklist.

Its SKILL.md is about 790 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. The repository describes itself as: Firmware for Xteink X3/X4. Personal fork of Crosspoint and CrossInk. The licence is MIT.

When your agent uses it

  • Preparing a change for PR
  • Especially in this multi-contributor AI-assisted codebase that is prone to sprawl diffs

Example prompts

  • “/refactor-for-review”

What it can do on your machine

Read from SKILL.md and the folder at commit d272143. 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

Refactor For Review loads about 791 tokens when it runs. Until then it costs about 113 tokens; SKILL.md has 423 words of instructions outside code blocks.

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

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 yokki-vans/InkPointX at commit d272143, republished under its MIT licence (© yokki-vans). 423 words, ~791 tokens.

Download SKILL.mdSave it as .claude/skills/refactor-for-review/SKILL.md (or your agent's skills folder).
name
refactor-for-review
description
Producing small, single-concern, reviewable changes. Use when refactoring, cleaning up, restructuring, decomposing, or preparing a change for PR, especially in this multi-contributor AI-assisted codebase that is prone to sprawl diffs. Covers one-concern-per-commit, extracting helpers without widening scope, not bundling unrelated edits, decomposing oversized activities, comment hygiene, and a pre-handoff self-review checklist.

Refactor for Review

This is a multi-contributor, AI-assisted codebase, and the dominant failure mode is the sprawl diff: a one-line intent that touches thirty files. The goal is a change a reviewer can verify in one sitting. Cleaner structure that makes the next change easier is the win, not lines added.

One concern per change

  • A commit/PR does one thing. A bug fix is not also a rename is not also a reformat. If you spot an unrelated improvement mid-change, leave it or capture it separately; do not fold it in.
  • When the working tree has bundled two changes, separate them with the copy-affected-files-aside, reset, re-apply one concern, restore the rest pattern, not by committing the tangle.
  • Refactor and behavior change do not ride together. A pure refactor must not alter behavior; a behavior change should not drag a refactor along. If both are needed: two commits, refactor first.

Keep the diff narrow

  • Extract a helper to remove real duplication or to name a concept, not to chase abstraction. Three-plus copies, or a block that needs a name to be understood: extract. Two similar lines: leave them.
  • No "while I'm here" scope creep. A signature or type change that ripples to many call sites is its own PR: map every caller first, update them in one topological pass, and land it separately, not as a rider on a feature.
  • Match the surrounding code: comment density, naming, idiom. The diff should read like the file, not like a different author.
Show full SKILL.md (174 more words)Show less

Decompose oversized units

An activity or function that has outgrown one screen of responsibility (multiple unrelated state machines, or a file far larger than its siblings) is a decomposition candidate. Extract a cohesive sub-responsibility into its own unit, as a standalone behavior-preserving refactor, verified on its own, never mixed into a feature change.

Comments earn their place

Comments explain why: an invariant, a defense, a past incident, a non-obvious constraint. Never what the next line already says. Delete narration, phase-marker comments ("now we loop over..."), and restated function names. If a comment and the code it sits on say the same thing, the comment is the thing to cut.

Self-review before handoff

  • The change does exactly one thing; nothing unrelated rode along.
  • Refactor and behavior change are not mixed in one commit.
  • No "while I'm here" creep; rename/signature ripples are split out.
  • Extractions remove real duplication or name a real concept, not speculative abstraction.
  • New comments say why, not what; no narration or phase markers.
  • A reviewer can understand the diff without running it.

© yokki-vans, MIT. 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 .claude/skills/refactor-for-review of yokki-vans/InkPointX.

Open the folder on GitHubat commit d272143

Compare with similar skills

Refactor For Review 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.

Refactor For Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Refactor For Review this skillyokki-vans/InkPointX107—~791Automated safety check: PassMIT
Guidelinesakash-network/node1.1k20 repos~577Automated safety check: PassMIT
Migrate Core Code to Submodulestinyhumansai/openhuman42k—~2.6kAutomated safety check: PassGPL-3.0
Component Refactoringlangflow-ai/langflow155k—~3.5kAutomated safety check: PassMIT
Ponytail Lazy Developer ModeDietrichGebert/ponytail160k1 repos~873Automated safety check: PassMIT
ast-grep Structural Searchcode-yeongyu/oh-my-openagent70k—~3.3kAutomated safety check: PassMIT

Similar skills

  • Guidelines

    akash-network/node

    Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.

    1.1k GitHub starsUsed in 20 repos~577 tokens
    DevelopmentAuto-check passed

  • Migrate Core Code to Submodules

    tinyhumansai/openhuman

    Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.

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

  • Component Refactoring

    langflow-ai/langflow

    Refactor high-complexity React components in Langflow frontend.

    155k GitHub stars~3.5k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Ponytail Lazy Developer Mode

    DietrichGebert/ponytail

    Makes the agent pick the laziest solution that works: skip unneeded work, reuse what exists, prefer the standard library and platform features, and keep diffs small.

    160k GitHub starsUsed in 1 repo~873 tokens
    DevelopmentAuto-check passed

  • ast-grep Structural Search

    code-yeongyu/oh-my-openagent

    Searches and rewrites code by syntax-tree shape across 25 languages with ast-grep, for codemods, structural queries and YAML lint rules, using a Python wrapper script.

    70k GitHub stars~3.3k tokensUpdated today
    DevelopmentAuto-check passed

  • Systematic Code Refactoring

    luongnv89/claude-howto

    Guides refactoring in phases based on Martin Fowler's method: research, test coverage check, planning and small tested steps, with your approval at each phase.

    42k GitHub stars~3k tokensUpdated today
    DevelopmentAuto-check passed

More from yokki-vans/InkPointX

  • Control Flow Clarity

    yokki-vans/InkPointX

    Branching and state-modeling clarity in C/C++. An agent skill from yokki-vans/InkPointX.

    107 GitHub stars~737 tokensUpdated 17 days ago
    Auto-check passed

  • Hal And Abstractions

    yokki-vans/InkPointX

    Layering and abstraction discipline for the firmware. An agent skill from yokki-vans/InkPointX.

    107 GitHub stars~791 tokensUpdated 17 days ago
    Auto-check passed

  • Heap Discipline

    yokki-vans/InkPointX

    Memory allocation discipline for the ESP32-C3 (~380KB RAM, no PSRAM, single 48KB framebuffer).

    107 GitHub stars~889 tokensUpdated 17 days ago
    Auto-check passed

  • Scope Discipline

    yokki-vans/InkPointX

    Feature-scope discipline for a dedicated e-reader (not a Swiss Army knife).

    107 GitHub stars~691 tokensUpdated 17 days ago
    Auto-check passed

Categories

Questions about Refactor For Review

What does Refactor For Review do?

Producing small, single-concern, reviewable changes. An agent skill from yokki-vans/InkPointX. Refactor For Review is an agent skill from yokki-vans/InkPointX. Producing small, single-concern, reviewable changes.

When should I use Refactor For Review?

Refactor For Review fits situations like: preparing a change for PR; especially in this multi-contributor AI-assisted codebase that is prone to sprawl diffs.

How do I install Refactor For Review in Claude Code?

Run `npx skills add yokki-vans/InkPointX --skill refactor-for-review -a claude-code`. Or copy the skill folder (.claude/skills/refactor-for-review in yokki-vans/InkPointX) into .claude/skills/refactor-for-review in your project. Claude Code loads it when a task matches its description.

How do I install Refactor For Review in Codex?

Run `npx skills add yokki-vans/InkPointX --skill refactor-for-review -a codex`. Or copy the skill folder (.claude/skills/refactor-for-review in yokki-vans/InkPointX) into .agents/skills/refactor-for-review in your project. Codex loads it when a task matches its description.

Can I use Refactor For Review 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 yokki-vans/InkPointX --skill refactor-for-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/refactor-for-review, .gemini/skills/refactor-for-review, .github/skills/refactor-for-review and .opencode/skills/refactor-for-review in your project.

What does Refactor For Review need to run?

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

Does Refactor For Review 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 Refactor For Review 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 Refactor For Review use?

Refactor For Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Refactor For Review use?

About 791 tokens (SKILL.md is roughly 3.2k 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 Refactor For Review?

Skills that share tags, products or a category with Refactor For Review: Guidelines (akash-network/node, 1.1k stars), Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars), Component Refactoring (langflow-ai/langflow, 155k stars) and Ponytail Lazy Developer Mode (DietrichGebert/ponytail, 160k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Refactor For Review?

yokki-vans (a GitHub user) maintains it in yokki-vans/InkPointX, which has 107 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on September 24, 2026.

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