writing-prose

Edits prose drafts by cutting filler, hedges, and machine-writing tells.

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/m-de-graaff/skills --skill writing-prose-m-de-graaff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-prose
Source: https://github.com/m-de-graaff/skills/tree/main/skills/writing-prose
Command: npx skills add https://github.com/m-de-graaff/skills --skill writing-prose-m-de-graaff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Drafts of commit messages, PR descriptions, tickets, READMEs, and changelogs often read as machine-written: padded, hedged, and symmetrical where reality is not. This Skill provides a concrete editing method that cuts filler and puts the claim first so human readers get the point immediately. ## Core Features & Use Cases - Claim-first structure: Enforces a three-part shape — the claim in the first sentence, the evidence, then any real caveat — so readers never carry setup without knowing the point. - Substitution table: Maps common AI-writing tells ("It's worth noting that", "delve", "leverage", triads of three) to plain replacements, drawn from Wikipedia's Signs of AI writing. - Register guide: Adapts the same shape to commits, PR descriptions, tickets, changelogs, READMEs, code comments, and design docs. - Use Case: You drafted a PR description that a reviewer called generic. Run the six-step editing pass — delete the first sentence, cut the closing summary, check every list of three, remove hedges and degree adverbs — and the draft commits to its actual claim. ## Quick Start Edit this PR description draft to remove machine-writing tells and lead with the claim.

Frequently Asked Questions about writing-prose

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

FAQPage Schema
How do I make AI-generated text sound less robotic?▼

Cut the tells: delete preamble openers like "It's worth noting that", replace stock words like "delve" and "leverage" with plain verbs, and break up uniform sentence rhythm. Lead with the claim in the first sentence and commit to it instead of hedging.

How do I write a good PR description?▼

Open with what changed and why in one sentence, then give the reviewer what they need: risk areas, what to look at, and how it was tested. Delete any closing summary paragraph — the last point is the ending.

What are the signs of AI writing to avoid?▼

Common tells include "It's worth noting", "In today's fast-paced world", words like "delve" and "seamless", forced lists of three, degree adverbs without numbers, and a summary paragraph at the end. The inventory comes from Wikipedia's Signs of AI writing.

Does this skill decide what content to write?▼

No. It only shapes how prose is written, not what it says. Commit and PR conventions belong to git-workflow, ticket fields to jira-workflow, and it does not apply inside code, tests, or config files.

How should a changelog entry be written?▼

Write from the reader's side: state what they can now do or must now change, not what the repo did. "Sessions now survive a server restart" belongs; "refactored the auth module" does not.