technical-writing

Convert code changes into technical blog posts with frontmatter and WordPress drafts.

69|11|Updated Dec 30, 2025

Search Tags:#writing #publishing #codebase #blog #technical #style-guide

Ready to run

npx skills add https://github.com/richtabor/agent-skills --skill technical-writing-richtabor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: technical-writing
Source: https://github.com/richtabor/agent-skills/tree/main/skills/technical-writing
Command: npx skills add https://github.com/richtabor/agent-skills --skill technical-writing-richtabor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, markdown2, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Writes technical blog posts about features being built. This skill analyzes your codebase to understand implementations, then structures clear, engaging content that balances technical detail with readability while avoiding AI-sounding language.

Core Features & Use Cases

Loads Writing anti-patterns and style guides to shape tone and avoid AI patterns
Analyzes Git history and code changes to describe implementation decisions
Generates frontmatter (title, url, category, tags) and Gutenberg-friendly content
Saves drafts to a configurable path and optionally publishes to WordPress

Quick Start

Ask the tool to draft a technical blog post about a feature by analyzing your codebase and applying your writing guides.

Frequently Asked Questions about technical-writing

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

FAQPage Schema

How do I turn code changes into technical blog posts automatically?▼

To turn code changes into technical blog posts, this skill analyzes your codebase and Git history to extract implementation details, then applies a style guide to generate reader-friendly content with frontmatter. It structures feature announcements and architectural explainers while avoiding AI-sounding language.

What is the best way to write release notes from a codebase?▼

Writing release notes from a codebase is best handled by analyzing Git history to identify key implementation decisions, then mapping those changes to an anti-pattern and style guide framework. This ensures technical accuracy and readability while generating Gutenberg-compatible content with appropriate tags and metadata.

Can I draft technical blog posts directly in WordPress from Git history?▼

Yes, you can draft technical blog posts in WordPress from Git history. This skill generates Gutenberg-compatible content and frontmatter, saves drafts to a configurable path, and provides an optional workflow to publish directly to WordPress using the requests and markdown2 dependencies.

How do I avoid AI-sounding language in technical writing?▼

To avoid AI-sounding language in technical writing, this skill loads specific writing anti-patterns and style guides that shape tone and filter out generic phrasing. It analyzes your codebase to ground content in actual implementation details rather than relying on templated generation.

Does this technical writing skill work for architectural explainers and feature announcements?▼

Yes, this technical writing skill works for architectural explainers and feature announcements. It tailors content to your specified audience by extracting key implementation details from code changes and applying a structured style guide to balance technical depth with readability.

What format does the generated technical blog content use for frontmatter and publishing?▼

The generated technical blog content uses standard frontmatter including title, URL, category, and tags, formatted as Gutenberg-friendly content. This ensures compatibility with WordPress publishing workflows and allows drafts to be saved to a configurable path before optional publication.