Distillation

Date: Sep 8, 2026

• 🟡 (20:15) Public skill files are symlinked to the canonical package sources: apps/cli-docs/public/.well-known/skills/sentry-cli/SKILL.md → ../../../../../../packages/cli/plugins/sentry-cli/skills/sentry-cli/SKILL.md, and apps/cli-docs/public/.well-known/skills/sentry-cli/references → ../../../../../../packages/cli/plugins/sentry-cli/skills/sentry-cli/references.
• 🟡 (20:15) packages/cli/plugins/README.md states that packages/cli/plugins/sentry-cli/skills/sentry-cli/SKILL.md is auto-generated from CLI command definitions, must not be edited manually, is regenerated with pnpm run generate:docs, and is auto-committed by CI when stale.
• 🟡 (20:16) Regression tests in packages/cli/test/script/generate-skill-markdown.test.ts cover: extractCommandPathFromHeading() extracting command paths while ignoring descriptive headings; matchExampleToCommand() preserving optional organization syntax for agent-conversation headings; keeping organization and conversation ID in one positional; associating project-create examples; mapping bare command-group examples to a default subcommand; preferring longer command paths over shorter prefixes; and retaining valid generated project-create examples.
• 🔴 (20:16) User established that the platform in sentry project create arguments must always be attached with : and must never use a space-separated form. Valid examples include web:javascript api:python-django worker:node and my-new-app:javascript-nextjs; invalid forms include my-new-app javascript-nextjs and my-org/my-new-app javascript-nextjs.
• 🟡 (20:17) Type-checking reported src/commands/agent-conversation/list.ts(101,5): error TS2353: customUsage is not a known property of the current docs type, which only accepts { readonly brief: string; readonly fullDescription?: string | undefined; }.
• 🟡 (20:17) Type-checking also reported src/index.ts(26,34) and src/index.ts(34,32): error TS2307, because ./sdk.generated.js or its corresponding type declarations could not be found.
• 🔴 (20:17) User established that conversation IDs never contain /; [<org>/]<conversation-id> therefore has at most one slash, with text before it representing the organization and text after it representing the conversation ID, while a slashless value is the conversation ID with organization auto-detection.
• 🟡 (20:17) Historical commit 7cf6483be5ee458c66d3ab2c40362b63b0f5ed8f (feat: add sentry conversation command group for inspecting AI agent transcripts (#1020)) introduced sentry conversation list and sentry conversation view [<org>/]<conversation-id>. It chose shared buildListCommand/buildCommand, cursor-stack pagination, resolveOrg, markdown/plain rendering, and --json/--fields machinery for consistency; chose a single gh-style [<org>/]<conversation-id> positional; and used apiRequestToRegion with local Zod schemas because /ai-conversations/ was absent from @sentry/api 0.253.0, with a plan to replace local schemas once generated SDK types became available.
• 🟡 (20:17) Historical commit 7cf6483be5ee458c66d3ab2c40362b63b0f5ed8f intended transcript reconstruction from raw gen_ai.* span attributes to match sentry-mcp’s get-ai-conversation-details, structured JSON envelopes for agent consumption, and narrow-terminal behavior that drops low-priority list columns instead of truncating useful columns.
• 🟡 (20:17) The original docs added by commit 7cf6483be5ee458c66d3ab2c40362b63b0f5ed8f incorrectly showed space-separated view examples such as sentry conversation view my-org conv-123, despite the implementation’s declared single-positional [<org>/]<conversation-id> design; PR #1558 corrects this historical mismatch.
• 🔴 (20:18) User established the repository-wide migration directive: “replace bun run with tsx/pnpm across scripts and CI (#999),” corresponding to commit 2a62159fe.