Track Every Edit: A Standard Workflow for Article Agents

Where this fits

You ask your agent to "tweak the intro and tighten the conclusion" of a 2,000-word draft. It starts rewriting, you get interrupted, and an hour later the session truncates—losing half the edits. This skill solves that exact failure mode by forcing a structured edit workflow: confirm scope before touching the file, save in small batches, and report progress after every few changes. It turns an unstructured "edit my article" request into a trackable, resumable process.

Why agents benefit

• Scope confirmation prevents runaway rewrites — the agent lists each planned change (location, type, content) and waits for approval, so it never silently rewrites sections you wanted untouched.
• Incremental saves protect against context loss — by saving after every related group of edits, a truncated conversation only loses the last few changes, not the entire session's work.
• Progress reports keep you in control — after every 3–5 edits, the agent shows a checklist (completed vs. pending), so you can redirect mid-task without waiting for a final dump.
• Change summaries build trust — at the end, the agent explains why each edit was made, including sources for any external facts, making the review process faster and more accountable.
• Style rules are enforced — the skill references SHARED-RULES.md to keep the output consistent with the author's voice, useful when editing for a specific brand or person.

Practical scenarios

Revising a blog post with multiple stakeholder comments

You have a draft with notes from three reviewers. Instead of pasting each comment, you say "apply these changes." The agent reads the full article, groups the comments into a numbered edit list, confirms the order with you, then executes and saves each group—so you can approve the first batch while it works on the rest.

Restructuring a long technical guide

You need to move three sections, rewrite two headings, and delete a redundant FAQ. The agent lists every move and rewrite as discrete items, you approve the plan, and it executes with a visible checklist. If the session dies mid-way, you resume from the last saved point and the progress report tells you exactly what remains.

Reducing AI-flavored language without losing meaning

The user wants the article to sound more human. After editing, the agent triggers a separate review pass (the complementary "AI味审校" skill) to catch remaining robotic phrasing. The edit skill focuses on what to change; the review skill focuses on how natural it sounds—two cleanly separated concerns.

Add it to your agent workflow

Install the skill and invoke it when a user asks to edit or modify an existing article:

npx skills add alchaincyf/huashu-skills --skill huashu-article-edit

Then trigger it with a natural command like: "Edit my draft in post.md — shorten the intro, cut the third paragraph, and add a comparison table." The agent will follow the four-step flow: read → list changes → wait for confirmation → edit and save incrementally. For more details on this skill and similar ones, see its page on OpenAgentSkill.

Compare before adopting

Before committing, evaluate: (1) Quality signals — does the skill enforce a confirmation gate and incremental saves, or just promise them? (2) Maintenance freshness — check the GitHub repo for recent commits and issue responses; a stale skill may break with newer model contexts. (3) Alternatives — some agents have built-in file-change tracking; this skill adds a human-in-the-loop confirmation step that may be overkill for trivial edits. (4) Workflow fit — if your editing tasks are always single-shot and short, the overhead of listing and confirming every change might slow you down.

Why it is worth tracking

With 1,441 stars and an active author (alchaincyf, the maker behind the popular "花叔" AI newsletter), this skill shows real community traction. Its focus on edit process—not just output—addresses a pain point every agent developer hits: losing work to context limits. Keep an eye on it if you build agents that handle long-form content or multi-step revisions; the pattern of confirming scope and saving incrementally is a reusable template you can adapt even if you don't adopt the skill verbatim.