minimal-revision
Revise an already accepted article, essay, paper, statement, or manuscript under strict minimal-change constraints while still satisfying reviewer comments, supervisor feedback, or requested edits. Use when the user asks for minimal edits, smallest necessary changes, preserve the current voice, keep the existing style, avoid broad rewriting, or implement requested revisions without unnecessary polishing.
zxzin · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add zxzin/runpro --skill minimal-revisionAbout this skill
name: minimal-revision description: Revise an already accepted article, essay, paper, statement, or manuscript under strict minimal-change constraints while still satisfying reviewer comments, supervisor feedback, or requested edits. Use when the user asks for minimal edits, smallest necessary changes, preserve the current voice, keep the existing style, avoid broad rewriting, or implement requested revisions without unnecessary polishing.
Minimal Revision
Overview
Use this skill to revise a draft that is already acceptable in its current state. Treat the current draft as the approved baseline, complete all newly requested revisions, and make only the minimum changes needed.
Core Goal
Follow these priorities in order:
- Treat the current draft as an already qualified baseline.
- Satisfy every new explicit revision requirement.
- Minimize the total edit footprint while completing those requirements.
- Preserve the draft's existing wording habits, rhythm, structure, and tone.
- Avoid polished rewriting that changes the approved voice without need.
Non-Target Freeze Rule
Only modify text that is directly required by a new revision request.
If a word, phrase, sentence, paragraph, citation, or section is not part of the required change, leave it exactly as it is.
Do not touch nearby text just because it could be smoother, cleaner, more consistent, or more natural.
Default Mindset
Assume the current draft is intentionally shaped and should not be re-optimized.
Do not "improve" the article unless the requested revision requires it. Preserve the existing level of roughness, repetition, sentence cadence, and wording texture whenever they do not block the requested change.
Treat every requested edit as a constrained repair task on top of an already acceptable baseline, not as a writing-improvement task.
Required Inputs
Work from these inputs when available:
- the current article or manuscript draft
- the requested revisions, comments, tracked changes, or feedback list
- any user constraint about sections that must remain untouched
If a request is ambiguous, ask only the narrowest question needed to avoid unnecessary rewriting. Do not guess and then compensate with broad cleanup.
Revision Triage
Sort revision requests before editing:
- must-fix items that are explicitly required by the user, teacher, reviewer, or supervisor
- should-fix items that block correctness, consistency, or obvious compliance with the comment
- leave-as-is items that are merely awkward but do not block the requested revision
Do not convert a leave-as-is issue into an extra rewrite task.
Edit Budget
Always start with the smallest possible edit scope. Escalate only when the smaller scope cannot satisfy the request.
Use this escalation ladder:
- punctuation, spacing, marker, or formatting adjustment
- single-word replacement
- short phrase replacement
- local clause rewrite
- one-sentence rewrite
- two adjacent sentences
- paragraph-level rewrite only when the requested revision cannot be completed any other way
Do not jump to sentence or paragraph rewriting if a word-, phrase-, or clause-level edit is enough.
Protected Content
Preserve these items unless the revision request explicitly targets them:
- names of people, places, institutions, and works
- dates, numbers, percentages, article numbers, citations, and references
- established technical terms and key terms already used in the draft
- headings, numbering, list structure, and section order
- quotations, cited wording, and terminology that must stay aligned with source material
If a requested change appears to alter protected content accidentally, stop and flag it instead of silently rewriting around it.
Revision Workflow
Use this workflow every time:
- Read the current draft and the revision request together.
- Break the request into discrete required changes.
- For each change, locate the narrowest affected text span.
- Choose the lowest edit level from the edit budget that can satisfy the request.
- Apply the revision only to that span.
- Freeze all non-target text and leave it untouched.
- Preserve surrounding wording, sentence order, paragraph order, and local phrasing unless changing them is necessary for grammatical completeness.
- If new text must be added, build it from nearby wording patterns instead of inserting a freshly polished style.
- After all edits, run a preservation pass and revert any accidental smoothing, expansion, or stylistic normalization.
Preservation Rules
Preserve these features by default:
- sentence length pattern and pacing
- paragraph order and paragraph boundaries
- punctuation habits and citation placement
- repeated wording patterns that are already in the draft
- terminology already used in the draft
- the draft's current register, including slightly blunt or uneven phrasing
- formatting, numbering, headings, and list structure
When a revision adds content, match the local sentence texture of the surrounding passage instead of writing in a cleaner or more uniform register.
Forbidden Default Behaviors
Do not do any of the following unless the user explicitly requests them:
- rewrite a full paragraph for fluency
- globally polish tone or academic style
- edit nearby text that was not part of the requested change
- add transitions just to make the writing smoother
- replace several local edits with one cleaner full rewrite
- normalize terminology across the whole document
- remove repetition only because it sounds awkward
- expand explanations beyond what the revision request requires
- make the article sound more formal, balanced, or textbook-like
- silently restructure argument flow when the request only asks for local corrections
Handling Different Revision Types
Apply these defaults:
- For factual corrections, change only the incorrect factual fragment and keep the surrounding sentence shape.
- For logic or clarity comme