Skip to content

πŸ“ Document Scan Analyze, Delete, and Fix the View Verb Name#88

Open
gilday wants to merge 2 commits into
mainfrom
worktree-iss-7254+fix-pixee-scan-skill
Open

πŸ“ Document Scan Analyze, Delete, and Fix the View Verb Name#88
gilday wants to merge 2 commits into
mainfrom
worktree-iss-7254+fix-pixee-scan-skill

Conversation

@gilday
Copy link
Copy Markdown
Contributor

@gilday gilday commented May 15, 2026

The pixee CLI 0.13.0 release added pixee scan analyze <id> and pixee scan delete <id> alongside the existing list, and 0.15.0 (ISS-7255) replaced the positional pixee scan <scan-id> view-by-id form with an explicit pixee scan view <scan-id> subcommand. The audit-skills workflow caught two skill problems: the published pixee-scan skill called the view verb pixee scan get (which the binary rejects with "unknown command"), and it documented neither analyze nor delete.

This PR brings the skill in line with the 0.15.0 binary. The ## pixee scan get heading is replaced with ## pixee scan view, the body describes a normal subcommand (no more "positional shortcut" framing), and the text-mode output description matches the new sectioned Key: value block (Id, Detector, Branch, Sha, Imported at, Expires at) instead of the prior tab-separated row. ## pixee scan analyze documents the new subcommand, including --finding for scoping the analysis to specific findings, --watch for chaining the start call into the same poll-and-narrate behavior provided by pixee analysis view --watch, the --interval cadence default, the Started analysis <id> on scan <id> stdout contract, and the 422 non-analyzable error path. ## pixee scan delete matches the destructive-verb voice already used in pixee-workflow and pixee-repo: UUID positional, no flags, no client-side confirmation prompt.

The cross-reference to pixee-analysis is added to the PREREQUISITES blockquote so agents can follow the start-then-watch handoff. Four new runnable examples cover the bread-and-butter calls β€” analyze --watch on a whole scan, scoped --finding re-analysis with a longer --interval, the capture-the-id-and-watch-separately pattern, and scan delete β€” and the existing JSON view examples now use pixee scan view <id>. Two best-practices bullets capture analyze --watch versus hand-rolled polling and when to scope with --finding.

The picker description is rewritten verb-first to "List, view, analyze, and delete Pixee scans with filters for repository, branch, detector tool, and analysis state." (115 chars, no picker-breaking punctuation). The README bullet is refreshed to match.

/close ISS-7254

gilday added 2 commits May 20, 2026 15:24
The pixee CLI 0.13.0 release added `pixee scan analyze <id>` and
`pixee scan delete <id>` and surfaces a single-scan view as a positional
argument on the top-level subcommand (`pixee scan <scan-id>`) rather
than a `get` verb. The pixee-scan skill on `origin/main` documented
`list` plus a non-existent `## pixee scan get` section β€” so the
audit-skills workflow caught both missing verbs and a doc bug that
would have an agent type a command the binary rejects with
"unknown command".

This corrects the existing section and adds the two new ones.
`## pixee scan get` is replaced with `## pixee scan <scan-id>`,
explicitly calling out that the view-by-id form is the positional
argument on the top-level command β€” no `get` subcommand exists.
`## pixee scan analyze` documents the new subcommand, including
`--finding` for scoping to specific findings, `--watch` for chaining
the start call into the same poll-and-narrate behavior provided by
`pixee analysis view --watch`, `--interval` cadence, the
`Started analysis <id> on scan <id>` stdout contract, and the 422
non-analyzable error path. `## pixee scan delete` matches the
destructive-verb voice already in `pixee-workflow` and `pixee-repo`:
UUID positional, no flags, no client-side confirmation prompt.

The cross-reference to `pixee-analysis` is added to the PREREQUISITES
blockquote so agents can follow the start-then-watch handoff. Four new
runnable examples cover the bread-and-butter calls β€” `analyze --watch`
on the whole scan, scoped `--finding` re-analysis with a longer
`--interval`, the capture-the-id-and-watch-separately pattern, and
`scan delete` β€” and the existing JSON view examples are corrected to
use the positional form. Two best-practices bullets capture
`analyze --watch` versus hand-rolled polling and when to scope with
`--finding`.

The picker description is rewritten to verb-first
"List, view, analyze, and delete Pixee scans with filters for
repository, branch, detector tool, and analysis state." (115 chars,
picker-safe). The README bullet is refreshed to match.

/close ISS-7254
The pixee CLI 0.15.0 release replaced the positional view-by-id form
(`pixee scan <scan-id>`) with an explicit `pixee scan view <scan-id>`
subcommand. The audit-skills follow-up on this skill was drafted
against 0.13.0 where the positional shortcut still existed and called
out its quirk explicitly; this brings the section in line with the
0.15.0 reality.

The `## pixee scan <scan-id>` H2 is renamed to `## pixee scan view`,
and the body drops the "positional argument on the top-level command"
framing in favor of describing a normal subcommand. The text-mode
output description is updated to the new sectioned `Key: value` block
(`Id`, `Detector`, `Branch`, `Sha`, `Imported at`, `Expires at` β€”
colon-separated, one field per line) instead of the prior tab-separated
row; `Branch` is omitted for branch-less detectors. JSON output is
unchanged. Examples that used `pixee scan <id> --json` (the
fetch-one-scan example and the HAL walk) become `pixee scan view <id>
--json`, and the two best-practices bullets that referenced the
positional form are rewritten to use `view` as well.

The picker description doesn't change β€” "view" was already in the
verb list. The README bullet collapses `pixee scan <id> (view)` to
just `view` to match.

/close ISS-7254
@gilday gilday force-pushed the worktree-iss-7254+fix-pixee-scan-skill branch from 7f90aaa to c588711 Compare May 20, 2026 19:25
@sonarqubecloud
Copy link
Copy Markdown

@gilday gilday marked this pull request as ready for review May 20, 2026 19:26
@gilday gilday requested a review from dhafley May 20, 2026 19:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant