rw-revision-patch

Original：🇨🇳 Chinese

Translated

2 scripts

Split Markdown documents into paragraph blocks with stable IDs and hashes, only replace blocks approved by the user, and output the retention ratio, modification reasons, and issue tracking report. Use when the user asks for "only modify these paragraphs", "partial modification according to review comments", "keep other content unchanged", "generate reviewable modification patch", or requests the rw-revision-patch workflow.

8installs

Sourcerolandwonglonam/rw-research-skill

Added on2026-07-20

NPX Install

npx skill4agent add rolandwonglonam/rw-research-skill rw-revision-patch

SKILL.md Content (Chinese)

View Translation Comparison →

RW Revision Patch

Restrict modification scope. The first version only replaces existing Markdown blocks, without silently adding, deleting, or rearranging sections.

Startup

Read

references/method.md

and

references/patch-format.md

.

Keep the original document, run
```
scripts/revision_patch.py anchor
```
to generate a copy with block IDs and a manifest.
Create a Patch JSON based on the approved modification scope.
Run
```
check
```
to verify the hash, block ID, modification ratio, and issue ID.
Run
```
apply
```
to generate the new document and report.
Review the content of modified blocks and check the preserved ratio of unmodified blocks.

Commands

bash

python3 scripts/revision_patch.py anchor draft.md --output draft.anchored.md --manifest draft.manifest.json
python3 scripts/revision_patch.py check draft.anchored.md --manifest draft.manifest.json --patch revision.patch.json
python3 scripts/revision_patch.py apply draft.anchored.md --manifest draft.manifest.json --patch revision.patch.json --output draft.revised.md --report revision.report.json

Stop when modified blocks exceed 60% of the full text. Add

--allow-large-patch

only after the user explicitly approves large-scale modifications.

Work Stages

Fix the base document and version hash.
Number headings, paragraphs, lists, or code blocks by blank line boundaries.
Link each modification to the block ID, old hash, reason, and issue ID.
Verify all operations first; do not generate partial results if any operation fails.
Generate new files without overwriting the original files.
Output modified blocks, preserved blocks, retention ratio, and new hash.

Operation Rules

Original files are not modified.
The first version of Patch only supports
```
replace
```
.
A block can only be modified once in a single Patch.
```
expected_hash
```
must match the manifest.
```
new_text
```
cannot contain RW block markers.
Stop the entire batch if any precondition fails.
The content of unmentioned blocks remains unchanged.
Adding, deleting, or rearranging sections constitutes structural modification and cannot be disguised as partial replacement.
Patch can only restrict the scope of changes, not prove the correctness of modified content.

Outputs

Anchored Markdown copy.
Block manifest JSON.
Patch JSON.
Revised Markdown new file.
Apply report JSON, including preserved ratio and modification tracking.

Stop Conditions

Do not generate Patch when the input document has no stable version.
Stop when the hash, block ID, or base document does not match.
Stop when the modification ratio exceeds 60% and the user has not explicitly approved it.
Switch to the structural revision process when sections need to be added, deleted, or rearranged.

Follow-up Workflows

Academic writing:
```
rw-phd-write
```
.
Author tone:
```
rw-phd-tone
```
.
Review response:
```
rw-journal-submission
```
.
Claim review:
```
rw-claim-audit
```
.