Rewrite Plan Agent Skill

Author a long-running multi-file rewrite plan that subsequent patch-edit + diff-review + build-test stages will execute, with explicit ownership boundaries and patch-safety guarantees.

519 tokens

context cost

SKILL.md, read when the skill is used

files

plus reference files

copies elsewhere

how many repositories repackaged it

83 386

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/nexu-io/open-design --skill rewrite-plan

What comes with it

865 bytes besides the instruction

open-design.json

The instruction itself

6 sections, as written by the author

Rewrite plan

Spec §20.3 / §21.3.2: scenario 4 (design → deliverable production

code) requires a contract-shaped rewrite plan before the agent

starts editing files. The plan is the audit trail every

subsequent stage references; without it the patch path slides into

"refactor everything that looks wrong" and the build breaks in

unreviewable ways.

Inputs

code/index.json from code-import.
token-map/*.json from token-map.
The active design system DESIGN.md (already in prompt).
The user's tune intent (typically a short brief).

Output

project-cwd/
└── plan/
    ├── plan.md           # human-readable narrative
    ├── ownership.json    # { file: '...', layer: 'leaf' | 'shared' | 'route' | 'shell' }
    ├── steps.json        # ordered { id, files[], rationale, risk: 'low' | 'medium' | 'high' }[]
    └── meta.json         # { generatedAt, atomDigest, tokenMapDigest }

steps.json is the input patch-edit reads one entry per

iteration. ownership.json is the source of truth for "which

files belong to a single component vs. shared infrastructure";

patch-edit refuses to touch a shell-tier file unless the

matching step has risk: 'high' and the user explicitly confirmed.

Convergence

The atom completes when plan.md is non-empty AND steps.json

contains at least one step.

Anti-patterns the prompt fragment forbids

Plans that include "rewrite the whole component library" as a

single step. Break into per-component steps.

Plans that don't classify ownership.
Plans that don't list a build-test step at the end.

Status

Implemented by the daemon runner in

apps/daemon/src/plugins/atoms/rewrite-plan.ts. It classifies ownership and

writes plan.md, steps.json, and ownership.json.

Other skills for the same job

different authors, same section of the catalogue

Receiving Code Review

by ZhanlinCui

×9

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

1.6k tokens

Requesting Code Review

by ZhanlinCui

×8

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

Comprehensive GitHub code review with AI-powered swarm coordination

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

621 tokens

How to use it

Copy the folder

Take nexu-io/rewrite-plan from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.