blog

Convert development session logs and diff stories into structured technical blog posts.

3|2|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/joyehuang/skills --skill blog-joyehuang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blog
Source: https://github.com/joyehuang/skills/tree/main/blog
Command: npx skills add https://github.com/joyehuang/skills --skill blog-joyehuang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the friction of converting raw, fragmented development notes and session logs into structured, professional-grade technical blog posts.

Core Features & Use Cases

  • Multi-Format Generation: Supports diverse styles including source code analysis, bug fix documentation, solution comparisons, and project retrospectives.
  • Context-Aware Writing: Automatically pulls technical details, code snippets, and file paths directly from your project's session history.
  • Platform Optimization: Tailors the tone and structure for specific platforms like Medium, Dev.to, or Chinese-language platforms like Juejin.

Quick Start

Use the blog skill to generate a technical article based on the most recent diff story in the current project.

Frequently Asked Questions about blog

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

FAQPage Schema
How do I turn development session logs into a technical blog post?

To turn development session logs into a technical blog post, you analyze project-specific session files and diff stories to extract technical details, code snippets, and file paths, generating structured markdown articles. This ensures technical accuracy and code snippet validity.

Can I generate platform-specific technical writing from raw codebase history?

Yes, you can generate platform-specific technical writing from raw codebase history by tailoring the tone and structure for specific platforms like Medium, Dev.to, or Juejin. It automatically pulls context-aware technical details directly from local session history.

What is the best way to document a bug fix from a diff story?

The best way to document a bug fix from a diff story is transforming fragmented development notes into structured formats like bug fix documentation. By analyzing session history, it validates code snippets and file paths to produce professional-grade technical posts.

Do I need local session history to generate developer experience content?

Yes, you need local session history and codebase access to generate developer experience content. Accessing local session files is required to ensure technical accuracy and validate code snippets when converting raw diff stories into publishable articles.

What formats does session log to article conversion support?

Session log to article conversion supports diverse formats including source code analysis, bug fix documentation, solution comparisons, and project retrospectives. It structures raw diff stories into polished markdown tailored for various platforms.