publishing-checklist

Validate Jekyll site changes for publishing regressions before release.

3|Updated Dec 13, 2019
One-click install
npx skills add https://github.com/Christos-Hadjinikolis/Christos-Hadjinikolis.github.io --skill publishing-checklist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publishing-checklist
Source: https://github.com/Christos-Hadjinikolis/Christos-Hadjinikolis.github.io/tree/main/.codex/skills/publishing-checklist
Command: npx skills add https://github.com/Christos-Hadjinikolis/Christos-Hadjinikolis.github.io --skill publishing-checklist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents website and blog publishing mistakes by providing a final, practical QA pass that reduces the chance of broken navigation, incorrect metadata, leaked internal content, or accidental exposure.

Core Features & Use Cases

  • Pre-publish repository QA: Verify changed files are in expected locations and that internal-only docs do not render or leak into published output.
  • Metadata and social preview validation: Review front matter and ensure correct description, canonical behavior, and explicit social images (including correct og:image and twitter:image values).
  • Build output verification: Confirm the generated _site/ output does not contain accidental repo docs or unexpected pages, using make build and make audit where possible.

Quick Start

Use this skill to run a final publish-readiness review of your current changes before deploying the site and sharing the updated post.

Frequently Asked Questions about publishing-checklist

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

FAQPage Schema
How do I prevent broken links and leaked content when publishing Jekyll blog posts?

Prevent Jekyll publishing regressions by running a pre-merge release checklist that verifies the generated _site/ output, confirms correct front matter, and validates social preview metadata to stop broken navigation before merging.

How do I validate social sharing metadata like og:image for a Jekyll website release?

Validate social sharing metadata for Jekyll releases by reviewing page front matter to ensure correct description tags, canonical behavior, and explicit social images including proper og:image and twitter:image values during your pre-publish review.

What is the best way to check a Jekyll build for accidental internal documentation exposure?

Check Jekyll builds for internal documentation exposure by running make build and make audit, then inspecting the generated _site/ directory to confirm internal-only docs do not render or leak into the published output.

Do I need make build and make audit to review Jekyll site changes before merging?

You need make build and make audit to execute the checklist-driven verification workflow, which generates the _site/ output required for targeted inspection of page metadata and validation of content release readiness.

Why does my Jekyll site release checklist need to verify canonical behavior and analytics tags?

Your Jekyll release checklist verifies canonical behavior and analytics tags to prevent incorrect metadata from causing SEO regressions, duplicate content issues, or tracking failures after your website or blog post is deployed.

Can I use this pre-merge content QA process for both Jekyll blog posts and site page updates?

You can use this pre-merge content QA process for both Jekyll blog posts and site page updates, as the checklist-driven workflow validates changed files, navigation integrity, and metadata across all content release reviews.