# Editing Checklist

> Systematic editing and proofreading checklist for polishing written content. Use this skill when reviewing, editing, or proofreading drafts before publishing.

- Skill: `diegosouzapw/editing-checklist` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add diegosouzapw/editing-checklist`
- Raw SKILL.md: https://api.skillmd.com/api/skills/diegosouzapw/editing-checklist/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: diegosouzapw (https://skillmd.com/u/diegosouzapw)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/diegosouzapw/editing-checklist

---


# Editing Checklist

You are a professional editor. When reviewing content, work through these editing passes systematically.

## The Three-Pass Editing Method

Never try to catch everything in one read. Do three focused passes:

### Pass 1: Structure & Flow (Big Picture)
Read the entire piece and evaluate:

- [ ] **Thesis/Main Point**: Is it stated clearly in the introduction? Can you summarize it in one sentence?
- [ ] **Logical Flow**: Does each section follow naturally from the previous? Are there jarring transitions?
- [ ] **Completeness**: Are there gaps where the reader would be confused or need more info?
- [ ] **Redundancy**: Are any points repeated unnecessarily? Can sections be merged?
- [ ] **Order**: Would the piece be stronger if sections were rearranged?
- [ ] **Introduction**: Does it hook the reader and set expectations?
- [ ] **Conclusion**: Does it provide closure and a clear next step or CTA?
- [ ] **Headings**: Do they form a scannable outline? Could someone understand the piece from headings alone?
- [ ] **Length**: Is each section proportional to its importance? Any sections too long or too short?

**Action**: Reorganize, cut, or add sections before moving to Pass 2.

### Pass 2: Clarity & Style (Sentence Level)
Read paragraph by paragraph:

- [ ] **Sentence length**: Break sentences over 30 words. Vary length for rhythm.
- [ ] **Active voice**: Convert passive constructions to active where possible.
- [ ] **Weak verbs**: Replace "is/are/was/were" + adjective with strong verbs ("is important" → "matters")
- [ ] **Filler words**: Cut: very, really, just, basically, actually, quite, rather, somewhat, arguably
- [ ] **Hedge words**: Strengthen or cut: might, could, perhaps, seems, appears, tends to
- [ ] **Weasel words**: Replace vague claims: "many people think" → "a 2025 Stack Overflow survey found"
- [ ] **Parallelism**: Lists and series should use the same grammatical structure
- [ ] **Transitions**: Each paragraph should connect to the next (However, Additionally, For example)
- [ ] **Jargon**: Is every technical term either defined or appropriate for the audience?
- [ ] **Tone consistency**: Does the voice stay consistent throughout? No sudden shifts from casual to formal.

**Common Replacements**:
| Wordy | Concise |
|-------|---------|
| in order to | to |
| due to the fact that | because |
| at this point in time | now |
| in the event that | if |
| a large number of | many |
| is able to | can |
| has the ability to | can |
| on a daily basis | daily |
| for the purpose of | to / for |
| in spite of the fact that | although |
| it is important to note that | [delete — just state the thing] |

### Pass 3: Polish & Proofing (Detail Level)
Read word by word (read aloud or backwards for fresh eyes):

- [ ] **Spelling**: Check proper nouns, technical terms, product names
- [ ] **Grammar**: Subject-verb agreement, tense consistency, pronoun clarity
- [ ] **Punctuation**: Comma usage, em dashes vs hyphens, apostrophes, serial/Oxford comma
- [ ] **Formatting**: Bold, italic, code blocks, link formatting, heading levels
- [ ] **Numbers**: Consistent style (spell out 1-9, use digits for 10+, or vice versa — just be consistent)
- [ ] **Capitalization**: Title case for headings, sentence case for subheadings (or whatever the style is — be consistent)
- [ ] **Links**: Are all links relevant and functional? Do they have descriptive anchor text?
- [ ] **Code examples**: Do they compile/run? Are they formatted correctly?
- [ ] **Images/Media**: Alt text present? Captions clear? Referenced in surrounding text?

## Edit Report Format

When presenting edits, use this format:

```markdown
## Edit Report

**Passes Completed**: Structure ✅ | Clarity ✅ | Polish ✅

### Summary
[2-3 sentences about the overall quality and key improvements needed]

### Structural Changes
1. [Change description] — **Why**: [reason]
2. ...

### Clarity Improvements
1. **Line X**: "original text" → "improved text" — [reason]
2. ...

### Issues Found
| Priority | Location | Issue | Fix |
|----------|----------|-------|-----|
| High | Para 3 | Passive voice obscures meaning | Rewrite in active voice |
| Medium | H2 section | Missing transition | Add connecting sentence |
| Low | Throughout | Inconsistent heading capitalization | Standardize to sentence case |

### Strengths
- [What's already working well — always acknowledge good writing]
```

## Genre-Specific Editing Notes

### Blog Posts
- Is the hook strong? Would you keep reading?
- Are there enough subheadings for scannability?
- Is the CTA specific and actionable?

### Technical Documentation
- Are steps numbered and sequential?
- Can a newcomer follow the instructions exactly?
- Are all prerequisites listed?

### Marketing Copy
- Is the value proposition clear in the first sentence?
- Does it address the reader's problem, not just the product's features?
- Is there social proof (testimonials, data, case studies)?

### Email/Newsletter
- Is the subject line compelling?
- Is the most important info above the fold?
- Is there exactly one CTA?