원클릭으로 Manus에서 모든 스킬 실행

revise-chapter

스타1

포크0

업데이트2026년 7월 16일 01:16

Guided revision pass on a draft chapter -- macro-to-micro, with a measurable cut target and a read-aloud check. Use when Sagar says "revise this chapter", "tighten this", "edit pass", or wants a draft made publishable.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

Sagargupta16

Sagargupta16/sagas

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Revise a chapter

Run the revision ladder on ONE unpublished chapter (status: draft or revising). His prose stays his: propose edits as a findings list or, if he says "apply", as minimal diffs.

Preparation

Read references/revision.md and references/prose-style.md from the writing-craft library. Add references/pov-tense.md when filter words show up, references/dialogue.md when tags need work.

The ladder (never skip levels, never start at the bottom)

Story pass: does the chapter still do its outline job (goal, progress signpost, hook)? If the story is broken, stop here and report; line edits on a broken scene are wasted.
Scene pass: MRU order (motivation before reaction), scene/sequel balance, paragraphs that repeat a beat already landed.
Line pass, with the measurable King target -- 2nd draft = 1st draft - 10%:
- Count words before and after; report both numbers.
- Cut order: filler phrases, redundant beats, throat-clearing openings, -ly adverbs on tags, thought verbs, filter words (saw/felt/heard/noticed/realized) unless the distance is deliberate (Harnby).
- R.U.E.: Resist the Urge to Explain -- delete the sentence that explains the emotion the previous sentence already showed (Browne & King).
Read-aloud pass: flag rhythm faults -- runs of same-length sentences, accidental rhymes, tongue-twisters (Le Guin: the test of a sentence is, does it sound right).
Copyedit: typos, dialogue punctuation per US convention, -- never em/en-dash characters, one error type at a time.

Status transitions

After a full ladder run: suggest draft -> revising or revising -> final.
Publishing (publishedOn) is the publish-chapter skill's job, never this one's -- its gates (continuity, fanfic checks, mechanical sweep) must not be bypassed by an edit pass.

Rules

Published chapters (with publishedOn) only get typo/punctuation fixes; anything larger is a new-chapter problem or an author's-note, not a silent rewrite.
Never cut content just to hit -10% if the chapter is already lean; report the honest number and say why the target doesn't apply.
Preserve his darlings unless they serve the author instead of the story (Quiller-Couch's actual rule); when proposing such a cut, quote the passage and say exactly that.

이 저장소의 다른 Skills

같은 저장소

frontend-quality

Sagargupta16/sagas

Pre-ship UI quality gate for the sagas reading site -- accessibility (WCAG, keyboard, contrast), performance (fast static delivery, fonts, motion cost), and SEO (per-page metadata, canonical, OG/Twitter, sitemap, JSON-LD, RSS). Mobile-first, since the product is long-form reading on phones at night. Audits and fixes against this repo's design tokens and dash/motion house rules.

2026-07-161

outline-book

Sagargupta16/sagas

Turn a book idea into a structural outline with promises, arcs, and a chapter plan. Use when Sagar says "outline this book", "plan the plot", "structure this story", or has a new book idea that needs shape before drafting.

2026-07-161

critique-chapter

Sagargupta16/sagas

Run a full craft critique of a chapter draft -- structure, POV, prose, dialogue, pacing, exposition, hooks -- with findings cited to craft rules. Use when Sagar says "critique this chapter", "review my chapter", "is this chapter good", or pastes prose asking what's wrong with it.

2026-07-111

fanfic-check

Sagargupta16/sagas

Canon, characterization, and convention check for fan fiction chapters -- OOC detection, canon-compliance audit, tagging and disclaimer hygiene. Use when Sagar works on any fanfic-shelf book and says "canon check", "is this in character", "check my fanfic", or before publishing a fanfic chapter.

2026-07-111

name-forge

Sagargupta16/sagas

Generate and vet names -- characters, places, magic terms, book titles, chapter titles -- consistent with each book's naming rules. Use when Sagar says "name this", "title for this chapter", "what should I call", or needs any proper noun for a book.

2026-07-111

new-chapter

Sagargupta16/sagas

Add a chapter to an existing book, with correct ordering and a consistency pass. Use when Sagar says "new chapter", "add chapter", or pastes chapter prose for a book. For releasing a finished chapter, use publish-chapter instead.

2026-07-111

name	revise-chapter
description	Guided revision pass on a draft chapter -- macro-to-micro, with a measurable cut target and a read-aloud check. Use when Sagar says "revise this chapter", "tighten this", "edit pass", or wants a draft made publishable.

Revise a chapter

Run the revision ladder on ONE unpublished chapter (status: draft or revising). His prose stays his: propose edits as a findings list or, if he says "apply", as minimal diffs.

Preparation

Read references/revision.md and references/prose-style.md from the writing-craft library. Add references/pov-tense.md when filter words show up, references/dialogue.md when tags need work.

The ladder (never skip levels, never start at the bottom)

Story pass: does the chapter still do its outline job (goal, progress signpost, hook)? If the story is broken, stop here and report; line edits on a broken scene are wasted.
Scene pass: MRU order (motivation before reaction), scene/sequel balance, paragraphs that repeat a beat already landed.
Line pass, with the measurable King target -- 2nd draft = 1st draft - 10%:
- Count words before and after; report both numbers.
- Cut order: filler phrases, redundant beats, throat-clearing openings, -ly adverbs on tags, thought verbs, filter words (saw/felt/heard/noticed/realized) unless the distance is deliberate (Harnby).
- R.U.E.: Resist the Urge to Explain -- delete the sentence that explains the emotion the previous sentence already showed (Browne & King).
Read-aloud pass: flag rhythm faults -- runs of same-length sentences, accidental rhymes, tongue-twisters (Le Guin: the test of a sentence is, does it sound right).
Copyedit: typos, dialogue punctuation per US convention, -- never em/en-dash characters, one error type at a time.

Status transitions

After a full ladder run: suggest draft -> revising or revising -> final.
Publishing (publishedOn) is the publish-chapter skill's job, never this one's -- its gates (continuity, fanfic checks, mechanical sweep) must not be bypassed by an edit pass.

Rules

Published chapters (with publishedOn) only get typo/punctuation fixes; anything larger is a new-chapter problem or an author's-note, not a silent rewrite.
Never cut content just to hit -10% if the chapter is already lean; report the honest number and say why the target doesn't apply.
Preserve his darlings unless they serve the author instead of the story (Quiller-Couch's actual rule); when proposing such a cut, quote the passage and say exactly that.