publish-post

Publish a wro.cpp blog post with verification, permalinks, and pull request preparation.

1|Updated Sep 1, 2024
One-click install
npx skills add https://github.com/wrocpp/wrocpp.github.io --skill publish-post
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish-post
Source: https://github.com/wrocpp/wrocpp.github.io/tree/main/.claude/skills/publish-post
Command: npx skills add https://github.com/wrocpp/wrocpp.github.io --skill publish-post

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the end-to-end process of publishing a wro.cpp blog post by turning a draft into a verified, linked, reviewed, and ready-to-merge change.

Core Features & Use Cases

  • Post Verification: Confirms the related C++26 examples compile locally and in Compiler Explorer before publication.
  • Content Wiring: Replaces placeholder embeds with real permalinks, updates cross-references, and adds the discussion thread link.
  • Release Workflow: Flips the draft flag, creates the branch and commits, pushes the PR, and schedules publication safeguards.

Quick Start

Use the publish-post skill to ship the post identified by its slug or series number.

Frequently Asked Questions about publish-post

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

FAQPage Schema
How do I automate blog publishing from markdown draft to GitHub pull request?

Automating blog publishing from markdown draft to GitHub pull request requires verifying code examples, generating Compiler Explorer permalinks, updating cross-references, and preparing the branch commit. This skill handles that entire workflow end-to-end for the wro.cpp C++26 reflection series.

What is the process for generating Compiler Explorer permalinks before publishing a C++ blog post?

Generating Compiler Explorer permalinks before publishing a C++ blog post involves validating that local examples compile successfully, then replacing placeholder embeds with real permalinks. This skill automates that verification and permalink generation as part of the draft-to-PR workflow.

Do I need a clean git state and GitHub CLI access to automate markdown blog publishing?

Yes, a clean git state and GitHub CLI access are required to automate markdown blog publishing. You also need a working local build and verification environment to ensure the C++ examples compile correctly before the skill creates the pull request.

How to wire cross-references and discussion threads when preparing a blog post pull request?

Wiring cross-references and discussion threads when preparing a blog post pull request involves updating internal links and adding the discussion thread URL to the post. This skill automates the content wiring alongside flipping the draft flag and pushing the PR.

What's the best way to verify C++26 reflection examples compile locally before opening a PR?

Verifying C++26 reflection examples compile locally before opening a PR requires a working local build environment to test compilation. This skill integrates that local verification step with Compiler Explorer checks before flipping the draft flag and pushing the pull request.