post-review

Review Jekyll blog posts for prose errors and validate source links.

1|Updated Aug 1, 2020
One-click install
npx skills add https://github.com/JohannesKonings/JohannesKonings.github.io --skill post-review-johanneskonings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post-review
Source: https://github.com/JohannesKonings/JohannesKonings.github.io/tree/main/.github/skills/post-review
Command: npx skills add https://github.com/JohannesKonings/JohannesKonings.github.io --skill post-review-johanneskonings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Technical bloggers and content creators often spend hours manually proofreading blog posts for typos, grammar errors, broken links, and mismatched link context, while also needing to compile a clean list of sources without altering code examples or post structure.

Core Features & Use Cases

  • Prose Cleanup: Fixes spelling, grammar, and clarity issues in narrative text while leaving all code blocks, inline code, and CLI commands completely unchanged.
  • Link Validation: Checks all outbound URLs for functionality, verifies that surrounding text accurately describes the linked content, and flags mismatches for approval before making changes.
  • Source Hygiene: Automatically adds a deduplicated "Sources and links" section at the end of the post listing every URL mentioned in the content.
  • Use Case: A developer publishing a post about AWS CDK can use this skill to quickly fix typos, confirm all linked AWS documentation is valid and correctly described, and generate a sources list without modifying any code snippets or post layout.

Quick Start

Use the post-review skill to review and lightly edit the blog post file _posts/2024-05-20-aws-cdk-best-practices.md for prose quality and source hygiene.

Frequently Asked Questions about post-review

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

FAQPage Schema
How do I validate links and fix prose in Jekyll blog posts?

You can review Jekyll blog posts stored in the _posts/ directory by applying automated prose editing and source link validation, which fixes typos and checks outbound URL health without altering structural elements or code examples.

Can I automatically generate a deduplicated sources list for my technical blog post?

Yes, source hygiene automation can scan your technical blog post and automatically add a deduplicated 'Sources and links' section at the end, listing every URL mentioned in the content while preserving your original layout and inline code.

Does prose editing for Jekyll posts modify code examples and CLI commands?

Prose editing for Jekyll posts leaves all code blocks, inline code, and CLI commands completely unchanged, ensuring that spelling, grammar, and clarity fixes only apply to the narrative text surrounding your technical examples.

How do I check if link context matches the linked documentation in my blog post?

Link validation checks all outbound URLs for functionality and verifies that the surrounding text accurately describes the linked content, flagging any link context mismatches for your approval before making any changes.

What is the best way to verify outbound URL health in technical blog content?

Verifying outbound URL health in technical blog content involves checking all linked documentation for functionality, confirming descriptive accuracy, and generating a clean list of sources without manually proofreading each hyperlink.