Developer Docs Editing Review
Use this skill to improve developer documentation after a draft exists. It treats editing as validation and refactoring: check whether the doc is accurate, complete, structured, clear, brief, and reviewable.
This skill is derived from Docs for Developers: An Engineer's Field Guide to Technical Writing, especially Chapter 4, "Editing documentation." It is expanded with paraphrased guidance from Christopher Gales and the Splunk Documentation Team's The Product Is Docs: Writing Technical Documentation in a Product Development Group, especially Chapter 15, "Technical Editing," and Chapter 16, "Technical Verification." Do not copy book prose into user outputs. Source: https://link.springer.com/book/10.1007/978-1-4842-7217-6
Quick Start
- Load
guidelines.md to choose the smallest useful reference set.
- Identify doc type, audience, source of truth, and release risk.
- Use separate passes for technical accuracy, completeness, structure, clarity, and brevity.
- Use
workflows/verify-technical-doc.md when procedures, migrations, security, data, or production changes need formal verification.
- Use
workflows/edit-developer-doc.md for a full edit.
- Return findings first when the user asks for a review; return revised text when the user asks for an edit.
Default Output
When reviewing documentation, return:
- Findings - ordered by reader risk, with file/section references when available.
- Missing validation - commands, examples, screenshots, API facts, or source claims not checked.
- Verification route - self-test, SME review, QA test, or release blocker.
- Recommended edits - exact changes or rewrites.
- Review routing - who should validate technical details.
- Residual risk - assumptions that remain after the edit.
When editing directly, return the revised doc plus a brief change summary and unresolved questions.
Contents
| Need |
Start Here |
| Understand editing passes |
references/core/knowledge.md |
| Apply review rules |
references/core/knowledge.md |
| See examples of edits and feedback |
references/core/knowledge.md |
| Run a full edit |
workflows/edit-developer-doc.md |
| Verify risky technical docs |
workflows/verify-technical-doc.md |
| Route by task |
guidelines.md |
Core Posture
- Separate writing from editing; do not polish around an unverified flaw.
- Prioritize reader-impacting errors over style preferences.
- Ask for specific reviews from the right technical owners.
- Treat high-risk procedures as release-blocking until verified or explicitly accepted.
- Integrate feedback by user need, not by reviewer rank or comment volume.
1---2name: developer-docs-editing-review3description: Edit and review developer documentation for technical accuracy, completeness, structure, clarity, brevity, peer feedback, technical review, technical verification, QA procedure testing, and feedback integration. Use when reviewing, editing, refactoring, or preparing developer docs for release, especially docs with procedures, examples, prerequisites, or high-risk technical claims.4license: MIT5---67# Developer Docs Editing Review89Use this skill to improve developer documentation after a draft exists. It treats editing as validation and refactoring: check whether the doc is accurate, complete, structured, clear, brief, and reviewable.1011This skill is derived from *Docs for Developers: An Engineer's Field Guide to Technical Writing*, especially Chapter 4, "Editing documentation." It is expanded with paraphrased guidance from Christopher Gales and the Splunk Documentation Team's *The Product Is Docs: Writing Technical Documentation in a Product Development Group*, especially Chapter 15, "Technical Editing," and Chapter 16, "Technical Verification." Do not copy book prose into user outputs. Source: https://link.springer.com/book/10.1007/978-1-4842-7217-61213## Quick Start14151. Load `guidelines.md` to choose the smallest useful reference set.162. Identify doc type, audience, source of truth, and release risk.173. Use separate passes for technical accuracy, completeness, structure, clarity, and brevity.184. Use `workflows/verify-technical-doc.md` when procedures, migrations, security, data, or production changes need formal verification.195. Use `workflows/edit-developer-doc.md` for a full edit.206. Return findings first when the user asks for a review; return revised text when the user asks for an edit.2122## Default Output2324When reviewing documentation, return:25261. **Findings** - ordered by reader risk, with file/section references when available.272. **Missing validation** - commands, examples, screenshots, API facts, or source claims not checked.283. **Verification route** - self-test, SME review, QA test, or release blocker.294. **Recommended edits** - exact changes or rewrites.305. **Review routing** - who should validate technical details.316. **Residual risk** - assumptions that remain after the edit.3233When editing directly, return the revised doc plus a brief change summary and unresolved questions.3435## Contents3637| Need | Start Here |38|------|------------|39| Understand editing passes | `references/core/knowledge.md` |40| Apply review rules | `references/core/knowledge.md` |41| See examples of edits and feedback | `references/core/knowledge.md` |42| Run a full edit | `workflows/edit-developer-doc.md` |43| Verify risky technical docs | `workflows/verify-technical-doc.md` |44| Route by task | `guidelines.md` |4546## Core Posture4748- Separate writing from editing; do not polish around an unverified flaw.49- Prioritize reader-impacting errors over style preferences.50- Ask for specific reviews from the right technical owners.51- Treat high-risk procedures as release-blocking until verified or explicitly accepted.52- Integrate feedback by user need, not by reviewer rank or comment volume.
LVTD-LLC