huashu-article-edit skill

Overview

This skill standardizes article editing to ensure change scope is clear, progress is trackable, and edits are recorded. It prevents lost work from conversation interruptions and gives the user full control over what is changed. The workflow emphasizes confirmation, incremental saves, and transparent change logs.

How this skill works

On request, the skill first reads the full article to understand structure and tone. It then lists all proposed edits with locations and types, waits for user confirmation, and applies edits in small batches. After each batch the file is saved and a concise progress report is presented. When finished, a summarized changelog with reasons (and sources for external facts) is produced.

When to use it

• User asks to edit, modify, or optimize an existing article.
• Multiple edits are required across paragraphs or sections.
• You need deletions, rewrites, tone adjustments, or structural reorganization.
• Work must be resilient against chat interruption or accidental data loss.

Best practices

• Always confirm the full list of changes with the user before editing.
• Group related edits and save after each batch to avoid data loss.
• Report progress after every 3–5 items with completed and pending lists.
• Provide a final changelog listing each change and the reason behind it.
• Preserve the original author’s style unless the user requests a style shift.

Example use cases

• User says “edit this article” and you extract and confirm an itemized change list before editing.
• Turn a long draft into a concise version by listing sections to shorten and getting approval.
• Adjust article tone from formal to casual by identifying affected paragraphs and confirming scope.
• Remove outdated claims and supply updated references, saving after each group of edits.
• Restructure a scattered article into a logical flow by proposing section moves and applying them incrementally.

FAQ