pitchdocs

Plugin pitchdocs from marketplace lba-plugins in littlebearapps/lba-plugins. Commands read from the repo's manifest — 11 days ago.

Skills (16)

• api-reference

  Guidance for setting up API reference documentation generators — TypeDoc, Sphinx, godoc, and rustdoc. Detects project language, recommends the right tool, and provides configuration templates. Use when a project needs automated API documentation from source code comments.

• changelog

  Generates user-friendly changelogs from git history using conventional commits. Writes entries in benefit language ("You can now..." not "Refactored internal..."). Follows Keep a Changelog format. Use when creating or updating CHANGELOG.md.

• doc-refresh

  Orchestrates documentation updates after version bumps, feature additions, or periodic maintenance. Analyses git history since the last release, identifies which docs are affected, and delegates to existing skills (changelog, feature-benefits, docs-verify, llms-txt, user-guides) for selective refres

• docs-verify

  Validates documentation quality and freshness — checks for broken links, stale content, llms.txt sync, image issues, heading hierarchy, and badge URLs. Runs locally or in CI. Use to catch documentation decay before it reaches users.

• feature-benefits

  Systematic codebase scanning for features and evidence-based feature-to-benefit translation. Extracts what a project does from its code and translates it into what users gain — generates features and benefits sections, "Why [Project]?" content, and feature audit reports. Use when writing a features

• geo-optimisation

  Generative Engine Optimisation (GEO) patterns for documentation that surfaces correctly in AI-generated answers — citation capsules, crisp definitions, atomic sections, comparison tables, statistics, and semantic scaffolding. Load when optimising docs for AI citation (ChatGPT, Perplexity, Google AI

• launch-artifacts

  Transforms README and CHANGELOG into platform-specific launch content — Dev.to articles, Hacker News posts, Reddit posts, Twitter/X threads, and awesome list submission PRs. Keeps promotion tethered to code artifacts, not generic marketing. Use when launching or announcing a project release.

• llms-txt

  Generates llms.txt and llms-full.txt files following the llmstxt.org specification. Provides LLM-friendly content curation for AI coding assistants (Cursor, Windsurf, Claude Code) and AI search engines. Use when generating or updating llms.txt for a repository.

• package-registry

  Documentation guidance for projects published to npm and PyPI package registries. Covers metadata fields that affect registry pages, README cross-renderer compatibility, trusted publishing, provenance badges, and audit checks. Use when a project has package.json or pyproject.toml and is published pu

• pitchdocs-suite

  One-command generation and audit of the full public repository documentation set — README, CHANGELOG, ROADMAP, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, issue templates, PR template, and discussion templates. Use when setting up a new repo or auditing an existing one.

• platform-profiles

  Platform-specific equivalents for GitLab and Bitbucket when generating repository documentation. Lookup tables for file paths, badges, Markdown rendering, CI/CD, and CLI tools. Load this skill when working on non-GitHub repos or generating cross-platform docs.

• public-readme

  Generates READMEs with the Daytona/Banesullivan marketing framework — hero section, benefit-driven features, quickstart, comparison tables, and compelling CTAs. Produces docs that sell as well as they inform. Use when creating or overhauling a project README.

• roadmap

  Generates ROADMAP.md from project milestones, issues, and boards (GitHub, GitLab, or Bitbucket). Structures content with mission statement, current milestone progress, upcoming milestones, and community involvement section. Use when creating or updating a project roadmap.

• user-guides

  Generates task-oriented user guides and how-to documentation for a repository. Creates docs/guides/ with step-by-step instructions for common workflows, integrations, and advanced usage. Links guides into README.md and CONTRIBUTING.md. Use when a project needs user-facing how-to documentation beyond

• visual-standards

  Visual formatting standards for repository documentation — emoji heading prefixes, horizontal rules, TOC anchors, callouts, screenshots (device dimensions, HTML patterns, captions, shadows), and image optimisation. Load when generating READMEs with visual elements or working with screenshots.

• pitchdocs

  Generate marketing-quality repository documentation from codebase analysis. Scans 10 signal categories, extracts features with file-level evidence, and produces README, CHANGELOG, ROADMAP, and 15+ more docs. Zero runtime dependencies. For AI context file management, see ContextDocs.

Slash commands (16)

• /pitchdocs:activate

  Install, uninstall, or check status of PitchDocs per-project features: $ARGUMENTS

• /pitchdocs:ai-context

  AI context file management has moved to ContextDocs: $ARGUMENTS

• /pitchdocs:changelog

  Generate or update CHANGELOG.md from git history: $ARGUMENTS

• /pitchdocs:context-guard

  Context Guard hooks have moved to ContextDocs: $ARGUMENTS

• /pitchdocs:doc-refresh

  Refresh documentation after version bumps, feature additions, or periodic maintenance: $ARGUMENTS

• /pitchdocs:docs-audit

  Audit repository documentation completeness and quality: $ARGUMENTS

• /pitchdocs:docs-verify

  Verify documentation quality, links, freshness, and consistency: $ARGUMENTS

• /pitchdocs:features

  Extract features and benefits from a codebase: $ARGUMENTS

• /pitchdocs:geo

  Load GEO optimisation patterns for AI citation: $ARGUMENTS

• /pitchdocs:launch

  Generate platform-specific launch and promotion artifacts from README/CHANGELOG: $ARGUMENTS

• /pitchdocs:llms-txt

  Generate llms.txt and llms-full.txt for LLM-friendly content curation: $ARGUMENTS

• /pitchdocs:platform

  Detect hosting platform and report PitchDocs feature support: $ARGUMENTS

• /pitchdocs:readme

  Generate or update a marketing-friendly README.md: $ARGUMENTS

• /pitchdocs:roadmap

  Generate or update ROADMAP.md from GitHub milestones and issues: $ARGUMENTS

• /pitchdocs:user-guide

  Generate user guide documentation for the repository: $ARGUMENTS

• /pitchdocs:visual-standards

  Load visual formatting standards for screenshots, emoji headings, and image specs: $ARGUMENTS

Subagents (1)

• docs-freshness

  Checks documentation freshness and suggests PitchDocs commands to fix staleness. Launch when docs-awareness rule detects documentation moments, after version bumps, or before releases. Does NOT modify docs — only reports and suggests.

Similar plugins