From 98d3bc1ac94fb9106917d7a0e10c70330246c5da Mon Sep 17 00:00:00 2001 From: jawwad-ali Date: Tue, 14 Jul 2026 23:15:15 +0500 Subject: [PATCH 1/2] docs(integrations): document the 'integration list --catalog' flag 'specify integration list' accepts a --catalog flag (integrations/_query_commands.py: typer.Option(False, "--catalog", ...)) that browses the full built-in + community catalog, but the Integrations reference documented no options for the list command. Add an option table for it, matching the style used by the sibling 'integration search' and 'integration catalog add' sections. Co-Authored-By: Claude Opus 4.8 (1M context) --- docs/reference/integrations.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/reference/integrations.md b/docs/reference/integrations.md index 72044ec684..c441954bb6 100644 --- a/docs/reference/integrations.md +++ b/docs/reference/integrations.md @@ -48,6 +48,10 @@ The Specify CLI supports a wide range of AI coding agents. When you run `specify specify integration list ``` +| Option | Description | +| ----------- | ------------------------------------------------------------------------------------------- | +| `--catalog` | Browse the full catalog (built-in + community) instead of only the built-in/installed set | + Shows all available integrations, which one is currently installed, and whether each requires a CLI tool or is IDE-based. When multiple integrations are installed, the list marks the default integration separately from the other installed integrations. The list also shows whether each built-in integration is declared multi-install safe. From f32d10aa8ffb4bb2f5e5cada1ff1f891c074ffab Mon Sep 17 00:00:00 2001 From: jawwad-ali Date: Fri, 17 Jul 2026 15:17:21 +0500 Subject: [PATCH 2/2] docs(integrations): clarify that default 'integration list' shows only built-ins The --catalog row implied the default list already includes the full installed set; in fact 'integration list' iterates INTEGRATION_REGISTRY (built-ins) and marks installed status, so a community integration that is not built in only appears with --catalog. Reword the option and the intro sentence to say the default shows the built-in integrations and --catalog adds community ones. Co-Authored-By: Claude Opus 4.8 (1M context) --- docs/reference/integrations.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/reference/integrations.md b/docs/reference/integrations.md index c441954bb6..8b03b5c6c4 100644 --- a/docs/reference/integrations.md +++ b/docs/reference/integrations.md @@ -48,11 +48,11 @@ The Specify CLI supports a wide range of AI coding agents. When you run `specify specify integration list ``` -| Option | Description | -| ----------- | ------------------------------------------------------------------------------------------- | -| `--catalog` | Browse the full catalog (built-in + community) instead of only the built-in/installed set | +| Option | Description | +| ----------- | ----------------------------------------------------------------------------------------------------------------------- | +| `--catalog` | Also browse the catalog (built-in **and** community). Community integrations that are not built in are only shown here. | -Shows all available integrations, which one is currently installed, and whether each requires a CLI tool or is IDE-based. +Shows the built-in integrations, which one is currently installed, and whether each requires a CLI tool or is IDE-based. When multiple integrations are installed, the list marks the default integration separately from the other installed integrations. The list also shows whether each built-in integration is declared multi-install safe.