create-tldr-page

To create a tldr page, you provide a command name and an authoritative documentation URL. It extracts common usage patterns and formats them into concise, example-driven CLI references with an upstream link.

The best way to summarize command line documentation is to extract representative examples and validate source credibility. This approach converts scattered CLI help output into prioritized, example-driven tldr formatting.

Yes, you can use help output to generate tldr formatting. The tool accepts help output, context files, or documentation URLs to extract common command examples and apply placeholder conventions.

Yes, an authoritative URL is required to extract command examples for a tldr page. If a URL is missing or points to non-authoritative documentation, the tool prompts for clarification.

A tldr page should include 5 to 8 representative examples when summarizing documentation. It prioritizes the most common and useful command usage patterns extracted from the provided source.

When multiple candidate URLs are provided for tldr page validation, the tool prompts for clarification. It validates that the source URL points to authoritative documentation before extracting examples.