sansi-erhouxing

Enforces reading the full document skeleton before editing any existing document.

76|3|Updated Aug 7, 2026
One-click install
npx skills add https://github.com/Job-Yang/jobbyang-ai-skills --skill sansi-erhouxing-job-yang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sansi-erhouxing
Source: https://github.com/Job-Yang/jobbyang-ai-skills/tree/main/skills/sansi-erhouxing
Command: npx skills add https://github.com/Job-Yang/jobbyang-ai-skills --skill sansi-erhouxing-job-yang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When editing an existing document, agents and writers tend to fix only the flagged paragraph, append new sections at the end, or re-add content that a previous review deliberately removed. This Skill inserts a mandatory pre-edit checkpoint: read the whole document skeleton, map the impact area, and pass three gate questions before changing a single word. ## Core Features & Use Cases - Three-Step Hard Constraint: Read the whole piece, list the impact area (what you will touch plus related existing logic), then answer three gate questions about history, risk, and skeleton integrity. - Skeleton-First Rule: For new or heavily revised documents, establish the outline (one opinion sentence per section) before filling content, and re-scan the skeleton after any section change. - Pre-Edit Report Template: Produces a structured report covering what was read, the impact list, the three gate answers, and a final decision of edit, do-not-edit, or redesign at the skeleton level. - Use Case: A reviewer flags one paragraph in your design document. Instead of patching that paragraph, you first read the full skeleton, discover the paragraph's argument is actually supported in a later section, and decide to move evidence rather than rewrite. ## Quick Start Ask the agent to revise a section of an existing document and require it to run the pre-edit reading report before making any changes.

Frequently Asked Questions about sansi-erhouxing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I edit a document without breaking its overall structure?

Read the full document skeleton first, where each section is summarized as one opinion sentence. Then list the impact area of your planned change and check whether it breaks transitions between adjacent sections before editing.

What should I check before applying review feedback to a document?

Check three things: whether this point was changed before in document or review history, whether the fix is riskier than the original problem, and whether the change breaks the document skeleton. If any check fails, do not force a patch.

Does this workflow apply to code changes?

No. It only covers document-type artifacts such as essays, research notes, plans, and skill documentation. Code and engineering changes are explicitly out of scope and should go through dedicated verification workflows.

When can I skip the pre-edit reading step?

You can skip it for one-off disposable drafts, single-sentence answers, and trivial fixes like typos or formatting. Even for light edits, you should mentally confirm the change is truly only a typo before skipping.

Why does editing one paragraph cause inconsistencies elsewhere?

Documents have a skeleton where each section carries one job and evidence sits in specific places. Editing locally without reading the whole piece causes repeated content, broken transitions, and re-added material that prior reviews removed.