tui-cli

To sync CLI and TUI changes with project documentation, run the tui-cli skill after modifying TypeScript code. It parses command and screen changes, automatically updating Markdown files like CLAUDE.md and README.md to reflect the latest interface updates.

Keeping Markdown documentation consistent when updating CLI commands requires parsing TypeScript code for changes. This skill automatically updates docs/cli/ directories and generates a parity checklist, ensuring your command references match the actual codebase.

A parity checklist for CLI and TUI documentation is a generated list that guides manual verification of interface consistency. It ensures changes parsed from TypeScript code are accurately reflected across all updated Markdown files and prompts you to run tests.

Yes, this documentation sync tool works with TypeScript projects on feature branches and main. It parses TypeScript code for command and screen changes, then updates Markdown files across both branch types to maintain documentation parity.

The best way to automate TUI and CLI documentation updates is parsing TypeScript code for command and screen changes. This approach automatically updates Markdown files including CLAUDE.md and README.md, eliminating manual synchronization effort across feature branches.

Project documentation shows outdated CLI commands after code changes because Markdown files are not automatically synchronized. Running this skill parses TypeScript code changes and updates docs/cli/, docs/tui/, and README.md files to match your current interface.