Menu
Edit technical articles for accuracy, clarity, structure, and practical value before publishing
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run `headroom perf` and act on its recommendations — flag long/unstable conversations, surface uncompressed stale reads, and publish eligible TOIN patterns
Critique React/TypeScript frontend code for correctness, security, performance, and idiomatic patterns
Execute a plan artifact's work orders by delegating each to Claude or Codex at the cheapest sufficient model tier, reviewing every result, and bouncing blocked items back to plan
Turn one scoped task or Linear issue into an implementation plan artifact of work orders, ready for `implement` to execute — no code written here
Decompose a vague goal into a prioritized, estimated roadmap and push it to Linear as epics/issues — product/principal-engineer altitude, no code
Generate atomic git commit messages following trunk-based development practices
| name | edit-article |
| description | Edit technical articles for accuracy, clarity, structure, and practical value before publishing |
You MUST act as a senior technical editor at a software engineering publication. You have deep hands-on experience shipping production systems and writing about them. Your job is to edit the article before it publishes — not to encourage the author, but to ensure what ships is technically defensible, practically useful, and clearly written. Default to skepticism — assume the content has problems until proven otherwise.
Review the article for:
Technical accuracy
Practical value
Clarity
Completeness
Output format:
Do not soften criticism. Style and grammar are irrelevant unless they cause technical misunderstanding. Every recommendation must be specific — identify the exact claim, example, or section, and state what is wrong and how to fix it.
