docs: add integrations directory with framework tracker

[jdx]

Summary

• Adds integrations/README.md with a prioritized checklist of 30+ CLI frameworks across 16+ languages
• Organized into high/medium/lower priority tiers based on ecosystem popularity (GitHub stars)
• Includes a "How Integrations Work" section explaining the spec generation approach
• References clap_usage as the existing reference implementation

Highlights

High priority (>15k stars): Cobra (Go), Commander.js (Node), urfave/cli (Go), Typer/Click (Python), argparse (Python)

Medium priority (4-12k stars): yargs, Spectre.Console (.NET), Symfony Console (PHP), oclif, picocli (Java), Thor (Ruby), swift-argument-parser, and more

Lower priority (<3k stars): Kong, Clikt, argh, zig-clap, optparse-applicative, and others

Test plan

• No code changes, docs only

🤖 Generated with Claude Code

---

Note

Low Risk
Docs-only change that adds planning/overview material without modifying runtime code paths.

Overview
Adds a new integrations/README.md that tracks planned/implemented CLI-framework integrations via a prioritized checklist and links to the existing clap_usage reference implementation.

Documents the intended integration flow: extracting framework CLI definitions into the KDL usage spec to drive completions, docs, man pages, and --help output.

^{Written by Cursor Bugbot for commit 6859f09. This will update automatically on new commits. Configure here.}

[gemini-code-assist]

Summary of Changes

Hello @jdx, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces comprehensive documentation outlining the strategy for integrating with various CLI frameworks. It establishes a prioritized list of frameworks to target for generating usage specifications, which will enable features like shell completions, documentation, and man pages from a single source. The new README.md clarifies the integration process and provides a roadmap for future development in this area.

Highlights

• New Integrations Directory: A new integrations/README.md file has been added, featuring a prioritized checklist of over 30 CLI frameworks across more than 16 languages.
• Priority Tiers: Frameworks are organized into high, medium, and lower priority tiers, determined by their ecosystem popularity (GitHub stars).
• Integration Mechanism Explained: The document includes a section detailing "How Integrations Work," which explains the process of generating usage specs from CLI framework definitions.
• Reference Implementation: The clap_usage project is referenced as an existing implementation example for these integrations.

Changelog

• integrations/README.md
  • Added a new documentation file detailing CLI framework integrations.

Activity

• The pull request introduces documentation only, with no code changes.
• The content was generated with the assistance of Claude Code.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds a new documentation file, integrations/README.md, which serves as a tracker for planned integrations with various CLI frameworks. The document is well-organized, categorizing frameworks by priority based on popularity. My review focuses on enhancing the completeness of the information provided. I've suggested adding direct links to the documentation for standard library modules, which will improve the usability of this tracker for developers. Overall, this is a great addition for project planning and transparency.

[gemini-code-assist]

For consistency and to help readers, it would be great to add a link to the official documentation for argparse, similar to how other libraries have links to their repositories. This will make the list more useful.

Suggested change

	- [ ] **argparse** (Python) - stdlib
	- [ ] **argparse** (Python) - [stdlib](https://docs.python.org/3/library/argparse.html)

[gemini-code-assist]

To improve this documentation, please add links to the official documentation for these standard library modules. This will make it easier for developers to look them up.

Suggested change

	- [ ] **Getopt::Long** (Perl) - stdlib
	- [ ] **OptionParser** (Elixir) - stdlib
	- [ ] **OptionParser** (Ruby) - stdlib
	- [ ] **getopt** (C) - POSIX stdlib
	- [ ] **Getopt::Long** (Perl) - [stdlib](https://perldoc.perl.org/Getopt::Long)
	- [ ] **OptionParser** (Elixir) - [stdlib](https://hexdocs.pm/elixir/OptionParser.html)
	- [ ] **OptionParser** (Ruby) - [stdlib](https://docs.ruby-lang.org/en/master/OptionParser.html)
	- [ ] **getopt** (C) - [POSIX stdlib](https://man7.org/linux/man-pages/man3/getopt.3.html)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.81%. Comparing base (1a9a880) to head (6859f09).
⚠️ Report is 8 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #497      +/-   ##
==========================================
+ Coverage   70.71%   77.81%   +7.10%     
==========================================
  Files          47       47              
  Lines        6716     6595     -121     
  Branches     6716     6595     -121     
==========================================
+ Hits         4749     5132     +383     
+ Misses       1277     1105     -172     
+ Partials      690      358     -332     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Pull request overview

This PR adds a comprehensive documentation file tracking CLI framework integration priorities for the Usage project. The document serves as a roadmap for creating usage spec generators across 30+ popular CLI frameworks spanning 16+ languages, organized by implementation priority based on ecosystem popularity (GitHub stars).

Changes:

• Adds integrations/README.md with categorized checklist of CLI frameworks
• Includes explanatory "How Integrations Work" section describing the spec generation approach
• References the existing clap_usage implementation as a working example

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The "Lower Priority" section header implies frameworks with fewer than 3k stars, but Kong is listed with ~3k stars (exactly at the boundary). Consider either updating the section description to "≤3k stars" or moving Kong to the Medium Priority section if you want to maintain strict boundaries.

Suggested change

	### Lower Priority
	### Lower Priority (≤3k stars)