GitHub
Publish to your own blog repo instead of someone else’s platform. OpenWriter writes the post as markdown and commits it to the repo that already powers your site.
Authentication
The plugin uses your local GitHub CLI. Run gh auth login once and OpenWriter publishes as you. There is no OAuth connection to set up.
Register a site
add_blog_site registers a blog repo once. After that, every post is a single tool call.
- Points at a GitHub repo you own
- Stores the conventions OpenWriter needs to publish into it
Publish a post
post_to_blogwrites the post as a markdown file and commits it to the repo- Before anything is committed, the frontmatter is checked against your site’s content schema (since 0.34.0). If a field doesn’t fit, the publish stops and tells you what to fix
- Your Git history becomes the publishing log
- Featured images and frontmatter are written in the format your site expects
- Once a post is live, the Publish button becomes Republish, which updates the same post in place
Tools
| Tool | What it does |
|---|---|
inspect_blog_repo | Reads a repo and previews its framework, content directory, image directory, and frontmatter |
add_blog_site | Registers a blog repo |
list_blog_sites | Lists your registered sites |
edit_blog_site | Changes a registered site’s settings |
remove_blog_site | Removes a registered site |
post_to_blog | Commits the post to the repo |
Knows your stack
inspect_blog_reporeads the repo’s conventions — frontmatter shape, content directory, image paths- Posts land in the structure your static site generator already expects (e.g. an Astro content collection)
- No reformatting step on your end
Why repo-native
Your content is plain markdown in version control, served from your own domain. Move it, version it, or leave OpenWriter entirely — the posts stay.
Related
- Blog-Writer is the skill that drafts the post this plugin commits
- Connections covers the X, LinkedIn, and newsletter accounts