technical-writing

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.

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.

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.

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.

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.

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.