Dashboard › cli › Distillation
34f6a55b-6a06-49e8-957e-63aef7139dd0["lore_tm_v1_V_ofmrKTibhpqX9v3airu1-ApCHZNM_w77b7cFFouJM","lore_tm_v1_wwO_A-C0Yy93MdK2JjFhWQLEIPwjuccL1Bfqi-NLUBI","lore_tm_v1_qO0pPOkJ2QVqLHF5jSXZSr20MwNdqfXieNG3rgAvnIs","lore_tm_v1_qm9vi3eBRl96Hbu22f9zeyy7qh9kB-GNHPBcYGg0jFU","lore_tm_v1_CnPZUxbkANubBycHnUs-IuZ3j8YgI_ZQXmnfxo8c7tQ","lore_tm_v1_Dy5YdmYTaanupdgsI21XPgkeROGWUr6UUNqyGvBwtiU"]
packages/cli/plugins/sentry-cli/skills/sentry-cli/references/build.md has front matter name: sentry-cli-build, version: 0.45.0-dev.0, description Manage mobile build artifacts, bins: ["sentry"], and auth: true; it documents sentry build upload <path...> as “Upload builds to a project.”sentry build upload <path...> documentation lists flags including --build-configuration <value>, --release-notes <value>, repeatable --install-group <value>..., --head-sha <value>, --base-sha <value>, --vcs-provider <value>, --head-repo-name <value>, --base-repo-name <value>, --head-ref <value>, --base-ref <value>, --pr-number <value>, and boolean --force-git-metadata, which conflicts with --no-git-metadata.cb6c33e0c2b313d0ce0aebcaf94db06daaa2afb0cea7b0f8b3aa3b657b3a1102.packages/cli/test/script/generate-skill-markdown.test.ts was revised so the agent-conversation documentation test builds metadata directly from listCommand, viewCommand, and buildCommandInfo, and imports formatCommandExamples, rather than reading references/agent-conversation.md for those assertions.listCommand.__primaryUsage is undefined, list positional syntax is [<org>], and list examples include # Explicit organization\nsentry agent-conversation list my-org.[<org>/]<conversation-id> and exact examples in order: 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) is expected to render one **Examples:** section containing a fenced bash block, with the 3 agent-conversation view examples separated by blank lines.sentry project create syntax must always be attached to the project name with : and must never use a space-separated form.sentry project create my-new-app javascript-nextjs and sentry project create my-org/my-new-app javascript-nextjs, while requiring sentry project create web:javascript api:python-django worker:node and sentry project create my-new-app:javascript-nextjs.validationError was found only once by search, at packages/cli/src/lib/errors.ts:540.field must always be passed when constructing a validation error because unfielded validation errors collapse into one Sentry fingerprint.packages/cli/src/lib/errors.ts defines buildValidationMessage(headline: string, examples: string[], note?: string): string; it renders the headline, an optional blank line plus Try: section with each example indented by 2 spaces, and an optional blank line plus Note: ${note}.packages/cli/src/lib/errors.ts currently defines validationError(headline: string, examples: string[], field?: string, note?: string): ValidationError, passing buildValidationMessage(headline, examples, note) and field into new ValidationError(...); both the wrapper’s field parameter and ValidationError constructor’s field parameter are typed optional despite the stated requirement to always pass field.ValidationError extends CliError, calls super(message, EXIT.VALIDATION), sets this.name = "ValidationError", and stores readonly field?: string.sentry agent-conversation view probes showed "id", " org/id ", "org/ id", and "\tid\n" proceeded to API requests and threw ApiError: API request failed: 403 Forbidden; surrounding whitespace was therefore not uniformly rejected or trimmed before request handling."org /id" proceeded to an API request and exited 30 with a 404 Not Found error for endpoint /organizations/org /agents/conversations/id/, preserving the space in the organization segment."/id" and "org/" exited 21 with Error: Conversation target must include both an organization and conversation ID when using '/'. followed by a Try: suggestion; the captured suggestion was truncated as sentry agent-conversation view [<org>/]<conversation-id."org//id" and "org/id/x" exited 21 with Error: Conversation target must contain at most one '/'. and the recovery command sentry agent-conversation view [<org>/]<conversation-id>.