| name | blog-post |
| description | Create a blog post via guided prompts with git context auto-populated. Use when writing a quick update, retrospective, tutorial, deep dive, or devlog entry. |
| args | [type] [--project <name>] [--title <title>] |
| allowed-tools | Read, Write, Edit, Grep, Glob, Bash(hugo *), Bash(date *), TodoWrite, AskUserQuestion |
| argument-hint | quick-update | project-update | retrospective | tutorial | deep-dive |
| disable-model-invocation | true |
| created | "2026-01-10T00:00:00.000Z" |
| modified | "2026-05-09T00:00:00.000Z" |
| reviewed | "2026-02-14T00:00:00.000Z" |
/blog:post
Create a blog post about your work with minimal friction. Gathers context automatically and provides structured templates to reduce blank-page anxiety.
When to Use This Skill
| Use this skill when... | Use alternative when... |
|---|
| Capturing work quickly into a blog post | Need detailed documentation -> Project wiki/docs |
| Want templates to reduce blank-page anxiety | Writing a technical tutorial -> /blog:post tutorial |
| Need git context auto-populated | Creating portfolio summary -> Different workflow |
Context
- Blog directory: !
find . -maxdepth 1 -type d \( -name blog -o -name posts -o -name _posts \) -print -quit
- Git remotes: !
git remote -v
- Recent commits: !
git rev-list --count --since="7 days ago" HEAD
- Current branch: !
git branch --show-current
Parameters
Parse $ARGUMENTS for:
type: Post type (quick-update, project-update, retrospective, tutorial, deep-dive)
- If not provided, ask user to select
--project <name>: Specify project name (default: detected from git)--title <title>: Specify post title (default: ask user)--edit: Open in editor after creation (default: show filepath)
Execution
Execute this blog post creation workflow:
Step 1: Gather context
Detect project name and recent git history:
- Use
git log to get recent commits
- Extract project name from git remote or directory
- If blog directory doesn't exist, ask where to save posts
Step 2: Determine post type
If type argument not provided, ask user to select from five options:
- Quick Update (5-15 min)
- Project Update (20-45 min)
- Retrospective (45-90 min)
- Tutorial (1-3 hours)
- Deep Dive (2-5 hours)
Step 3: Ask targeted questions based on post type
For each type, ask 1-2 focused questions:
- Quick Update: "What did you just do?"
- Project Update: "Main accomplishment?" and "What was interesting?"
