manpage-sync

Synchronize ytnova manpage and usage docs from etc/ytnova.1.md via make docs.

12|1|Updated Oct 31, 2025
One-click install
npx skills add https://github.com/robkam/ytreenova --skill manpage-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manpage-sync
Source: https://github.com/robkam/ytreenova/tree/main/.ai/skills/manpage-sync
Command: npx skills add https://github.com/robkam/ytreenova --skill manpage-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps the ytnova manpage and usage documentation aligned with the canonical source by centralizing edits in etc/ytnova.1.md and regenerating derived outputs.

Core Features & Use Cases

  • Edit etc/ytnova.1.md as the single source of truth for the manpage and usage docs.
  • Regenerate derived outputs with the build step (make docs) to ensure docs/USAGE.md and other artifacts reflect current behavior.
  • Validate that generated outputs are consistent with implemented behavior and UI.

Quick Start

Edit etc/ytnova.1.md to update the source, then run make docs to regenerate the usage documentation.

Frequently Asked Questions about manpage-sync

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

FAQPage Schema
How do I keep generated manpage documentation in sync with source files?

To keep generated manpage documentation in sync, edit the canonical source file and run a build command to regenerate derived outputs. This ensures all usage docs reflect the latest changes made to the source.

What is documentation drift and when do I need to regenerate manpage outputs?

Documentation drift occurs when derived outputs become outdated after editing source files. You need to regenerate manpage outputs whenever edits cause a mismatch between the canonical source and the generated usage docs.

How do I regenerate usage docs from a markdown manpage source?

To regenerate usage docs from a markdown manpage source, edit the canonical markdown file and execute the build step. This processes the source file and produces updated usage documentation artifacts.

Do I need to edit generated usage docs directly when updating manpages?

No, you should not edit generated usage docs directly. You must edit the canonical manpage source file as the single source of truth, then run the build step to regenerate all derived documentation outputs.

Why does my generated manpage not match current application behavior?

Your generated manpage may not match current behavior due to documentation drift. You need to update the canonical source file, regenerate the outputs using the build command, and validate that the docs reflect current behavior.