Help us improve
Share bugs, ideas, or general feedback.
From blog-plugin
Generates Markdown blog posts about recent work using git history, project detection, and type-specific templates (quick-update, project-update, retrospective, tutorial, deep-dive) with guided prompts.
npx claudepluginhub laurigates/claude-plugins --plugin blog-pluginHow this skill is triggered — by the user, by Claude, or both
Slash command
/blog-plugin:blog-postThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create a blog post about your work with minimal friction. Gathers context automatically and provides structured templates to reduce blank-page anxiety.
Provides style guide and Markdown templates for consistent, scannable blog posts on technical projects, from quick updates to tutorials and retrospectives.
Generates Markdown blog post drafts from recent git commits, ctx status, learnings, decisions, and journals. Use for documenting project progress and sharing development experiences.
Accepts PRs, git refs, marketing briefs, or freeform text as input and generates a structured, SEO-optimized blog post with discovery, research, and outline phases.
Share bugs, ideas, or general feedback.
Create a blog post about your work with minimal friction. Gathers context automatically and provides structured templates to reduce blank-page anxiety.
| 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 |
find . -maxdepth 1 -type d \( -name blog -o -name posts -o -name _posts \) -print -quitgit remote -vgit rev-list --count --since="7 days ago" HEADgit branch --show-currentParse $ARGUMENTS for:
type: Post type (quick-update, project-update, retrospective, tutorial, deep-dive)
--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)Execute this blog post creation workflow:
Detect project name and recent git history:
git log to get recent commitsIf type argument not provided, ask user to select from five options:
For each type, ask 1-2 focused questions:
YYYY-MM-DD-<slugified-title>.mddate: Todayproject: Detected or specifiedtype: Selected typestatus: draftAsk what user would like to do:
| Context | Command |
|---|---|
| Get project name | git remote get-url origin 2>/dev/null | sed 's/.*\///' | sed 's/\.git$//' |
| Recent commits | git log --since="7 days ago" --format="%h %s" 2>/dev/null | head -10 |
| Find blog directory | ls -d blog/ posts/ content/blog/ content/posts/ _posts/ 2>/dev/null | head -1 |
| Current date | date +%Y-%m-%d |
| Get today's commits | git log --since="1 day ago" --format="- %s" 2>/dev/null |
| Post Type | Time | Use Case |
|---|---|---|
| Quick Update | 5-15 min | Small wins, log entries |
| Project Update | 20-45 min | Milestone, feature complete |
| Retrospective | 45-90 min | Reflection on period/project |
| Tutorial | 1-3 hours | Teach how to do something |
| Deep Dive | 2-5 hours | Explain complex concepts |