skills.rest
whinchman
whinchmanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

blogger

Generates technical blog posts and changelogs from a project's codebase and workflow files.

Updated May 2, 2026
Search Tags:#changelog#documentation#markdown#technical writing#release notes#codebase analysis#blog generation
One-click install
npx skills add https://github.com/whinchman/midi-man-mk3 --skill blogger-whinchman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: blogger
Source: https://github.com/whinchman/midi-man-mk3/tree/main/.claude/skills/blogger
Command: npx skills add https://github.com/whinchman/midi-man-mk3 --skill blogger-whinchman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing project announcements, release notes, and technical blog posts requires re-reading the codebase and git history, which is time-consuming. This Skill automates that by reading the project source, completed-feature logs, and backlog, then producing a structured markdown article. ## Core Features & Use Cases - Codebase-Driven Writing: Reads agent.yaml, README.md, DONE.md, BACKLOG.md, git history, and key source files to ground the article in what was actually built. - Configurable Tone: Uses the blogger.mood setting (e.g., technical deep-dive, casual, marketing-forward, tutorial) to control voice, structure, and code-snippet depth. - Dated Output Files: Writes the article to a configurable output directory as blog-<project>-<YYYY-MM-DD>.md. - Use Case: After shipping a feature in a Rust MIDI sequencer project, run the Skill to produce a developer blog post covering the architecture, shipped work, and roadmap without writing it manually. ## Quick Start Ask the agent to read this project and write a blog post about the recently completed features using the blogger skill.

Frequently Asked Questions about blogger

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

FAQPage Schema
How do I generate a blog post from my codebase automatically?▼

Run the blogger agent in the project root. It reads agent.yaml, README.md, DONE.md, BACKLOG.md, recent git history, and key source files, then writes a markdown article to the configured output directory.

How do I control the tone of an AI-generated technical blog post?▼

Set the blogger.mood field in agent.yaml. Supported styles include technical deep-dive, casual and approachable, marketing-forward, and tutorial; if omitted, a neutral technical tone is used.

What files does the blogger agent need to write an article?▼

It requires agent.yaml for project name and description. It optionally reads README.md, .workflow/DONE.md, .workflow/BACKLOG.md, and git log output, skipping any files that do not exist.

Where does the generated blog article get saved?▼

The article is written to <blogger.output_dir>/blog-<project.name>-<YYYY-MM-DD>.md if output_dir is set in agent.yaml, otherwise to .workflow/blog-<project.name>-<YYYY-MM-DD>.md.

Does the blogger agent modify my project source code?▼

No. The agent is read-only with respect to project source. It does not create branches, open PRs, or edit project files; it only reads context and writes the article output file.

Related Skills

Explore More Content & Communication Skills→
jayhjenkinsjayhjenkins
1

roadmap-updating

Sequence PRDs by timeline and status into Now/Next/Later roadmap sections.

Community
Basic
Dante-danDante-dan

dan-publish-all

Publish markdown articles across multiple content platforms with generated visual assets.

Community
Advanced
tau-rstau-rs

critic

Flag unsourced claims in written drafts against a reference style guide.

Official
Basic
allanninalallanninal
1

changelog-generator

Convert git commits into changelogs following Keep a Changelog and Conventional Commits.

Community
Intermediate