eos-devlog-publish

To convert private vault devlog sessions into draft posts, this skill reads session logs and writes them as publish-ready posts with publish: false. It preserves frontmatter and triggers a local site rebuild so drafts appear for review.

Yes, eos-devlog-publish preserves the original session frontmatter when writing draft posts. It sets type: post and publish: false by default to ensure your devlog drafts remain safe for review before going live.

You trigger a local site rebuild after publishing devlog drafts by using the integrated Publish API. The skill automatically initiates this rebuild once it finishes writing the draft posts to the site source directory.

Devlog drafts are set to publish: false by default to separate the wrapup workflow from public visibility. You can override this default behavior and publish directly by using the --publish flag during the devlog publish process.

The default publish state for devlog posts generated from vault logs is publish: false. This ensures that converted session logs remain as unpublished drafts under the site devlog directory until you explicitly review and approve them.