Dashboard › cli › Distillation
704024a2-3af3-4031-92fb-ed958b6d5223["lore_tm_v1_90oyRDpMD7mXL57WK5UdZKf24AGXpp0pg-P_ntG0YSo"]
extractFlags() always returns one FlagInfo per input entry; packages/cli/test/lib/introspect.property.test.ts verifies the output length equals Object.keys(flags).length, preserves every flag name, and defaults boolean flags with unspecified optional to optional: true.getPositionalString() for tuple positionals always produces angle-bracket placeholders. Updated property coverage generates both placeholder and optional; each entry must render as <${placeholder}> when required or [<${placeholder}>] when optional, using arg${index} when no placeholder is supplied.getPositionalString() for array positionals always includes an ellipsis (...).resolveCommandPath(routeMap, []) always returns null; property coverage also requires any resolved command path to start with sentry .packages/cli/test/lib/introspect.test.ts adds exact optional-tuple rendering coverage: required { placeholder: "required" } plus optional { placeholder: "optional", optional: true } must produce <required> [<optional>].packages/cli/test/lib/command.test.ts adds coverage that buildCommand() retains structured docs.examples on the command’s introspection metadata as __examples; the fixture preserves { description: "Select an organization explicitly", command: "sentry thing list my-org" }.buildCommandInfo() prefers structured command metadata in __examples over legacy document examples. The test passes a stale legacy example sentry thing list stale-org but expects, in order: 1. # Use automatic organization detection\nsentry thing list; 2. # Select an organization explicitly\nsentry thing list my-org.packages/cli/test/script/generate-skill-markdown.test.ts adds integration coverage showing agent-conversation documentation is derived from command metadata via buildCommandInfo(): listCommand.__primaryUsage is undefined, list positional syntax is generated as [<org>], and list examples include # Explicit organization\nsentry agent-conversation list my-org.[<org>/]<conversation-id> and exactly these ordered examples: 1. # View full transcript (organization auto-detected)\nsentry agent-conversation view conv-123; 2. # Explicit organization\nsentry agent-conversation view my-org/conv-123; 3. # JSON output\nsentry agent-conversation view my-org/conv-123 --json.formatCommandExamples(view.examples) must render one **Examples:** section followed by a fenced bash block containing the 3 view examples in metadata order, with blank lines separating each comment-and-command pair.: and must not use a space-separated form. Generated plugins/sentry-cli/skills/sentry-cli/references/project.md must retain heading ### \sentry project create [<org>/]<name>:<platform>...`, exclude sentry project create my-new-app javascript-nextjsandsentry project create my-org/my-new-app javascript-nextjs, and include sentry project create web:javascript api:python-django worker:nodeplussentry project create my-new-app:javascript-nextjs`.sentry project create "My New App":.