release-manual

You can automate manual release for technical PDF documentation by verifying content completeness, auditing CHANGELOG updates, and generating Git commit and tag commands. This Skill checks PDF page counts and outlines to prevent silent content drops during publication.

The best way to verify PDF completeness before a technical documentation release is to check for page count, outline, and key sections. This Skill automates these PDF verification checks to ensure quality and consistency in manual publication workflows.

To manage CHANGELOG updates and Git handoff, you audit the CHANGELOG, update the deliverables README, and execute suggested Git commands for committing and tagging. This Skill automates the audit and generates the necessary Git handoff commands.

No, the release-manual Skill does not automatically execute Git commands for tagging a release. It suggests Git commands for committing changes and tagging the release, requiring manual verification and manual Git command execution to complete the handoff process.

This Skill specifically automates the release of Parallax Propeller 2 manuals by verifying PDFs and managing CHANGELOG updates. It applies to technical documentation release workflows involving manual publication and audit processes, though it is tailored for P2 manual publication.