pixee-workflow
List, create, update, run, and delete Pixee workflows on a repository with partial-update semantics across event kinds.
pixee · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add pixee/pixee-cli --skill pixee-workflow技能说明
name: pixee-workflow description: "List, create, update, run, and delete Pixee workflows on a repository with partial-update semantics across event kinds." license: Apache-2.0 compatibility: Requires the pixee CLI binary on PATH metadata: version: 1.1.0 openclaw: category: "developer-tools" requires: bins: - pixee cliHelp: "pixee workflow --help"
pixee workflow
PREREQUISITES: Read
../pixee-shared/SKILL.mdfor global flags, exit codes, and error handling,../pixee-auth/SKILL.mdif authentication needs to be configured, and../pixee-repo/SKILL.mdfor the--reporesolution protocol.
pixee workflow manages Pixee workflows for a single repository: list, view, create, update, run,
and delete.
pixee workflow list
pixee workflow list --repo <name-or-uuid>
--repois required.- Text output is tab-separated with columns
id,name,event,action,tool. - Pagination is transparent — every workflow on the repo is emitted in one call. There is no
--paginateflag here;--paginateonly lives onpixee api.
pixee workflow view
pixee workflow view <workflow-id>
Fetch a single workflow by UUID. <workflow-id> is the value shown in the id column of
pixee workflow list.
Default text mode prints a sectioned Key: value block of the workflow's headline fields — the
same ones list surfaces (id, name, event, action, tool) plus the event-specific
configuration (cadence/branch/start for schedule, branch for new-scan,
target-branch/source-branch for pull-request-scan) — colon-separated, one field per line.
Use --output json (or --json) for the full HAL body, which adds the _links envelope and any
fields the text view omits. No flags beyond the global ones.
A non-existent UUID returns the standard not-found error and exits 3.
pixee workflow create
pixee workflow create does not take an --event flag. Event kind is selected via a subcommand:
pixee workflow create schedule— cadence-based.pixee workflow create new-scan— triggered when a new scan is uploaded on a branch.pixee workflow create pull-request-scan— triggered on pull-request scans.
All three share the shared create flags below; event-specific flags differ:
schedule — --cadence <daily|weekly> (required), --start <iso8601> (optional start time
with timezone, e.g. 2026-05-01T00:00:00Z), --branch <name> (exact branch name; defaults to
the repo's default branch).
new-scan — --branch <pattern> (optional; supports a * suffix, e.g. release/*; defaults
to the repo's default branch).
pull-request-scan — --target-branch <pattern>, --source-branch <pattern> (each optional;
supports feature/* style patterns).
Shared create flags
Every create subcommand accepts:
--repo <name-or-uuid>— required. Target repository.--tool <tool>— required. Scanner tool (sonar,semgrep,codeql, etc.).--action <kind>— required.create-patchornone.--severity-labels <csv>,--min-severity-score <int>,--max-severity-score <int>,--min-fix-confidence <high|medium|low|no-rating>,--finding-limit <int|none>— optional severity filters. All require--action create-patch; they have no meaning for--action none.
--severity-labels and --min/max-severity-score are mutually exclusive: pick either
label-based or score-based filtering. The CLI rejects mixed usage at parse time (exit code 1)
before any network call.
pixee workflow update
pixee workflow update is a partial update: only the flags you pass are changed; everything
else is left as-is on the server. Like create, the event kind is selected via subcommand, and
the workflow ID is a positional argument:
pixee workflow update schedule <workflow-id>— for cadence-based workflows.pixee workflow update new-scan <workflow-id>— for new-scan workflows.pixee workflow update pull-request-scan <workflow-id>— for PR-scan workflows.
The subcommand must match the workflow's existing event kind; you cannot retype a schedule
workflow into a new-scan via update. There is no --repo flag — the workflow UUID
disambiguates by itself.
Event-specific flags mirror create:
- schedule —
--cadence,--branch,--start. - new-scan —
--branch. - pull-request-scan —
--target-branch,--source-branch.
Shared update flags
Every update subcommand also accepts:
-
--name <name>— rename the workflow. -
--enabled/--disabled— toggle the workflow on or off. Mutually exclusive; pass at most one. -
--action <kind>,--severity-labels,--min-severity-score,--max-severity-score,--min-fix-confidence,--finding-limit— same semantics and same--action create-patchrequirement as oncreate. The--severity-labelsvs--min/max-severity-scoremutual exclusion still applies. -
--unset <field>— repeatable. Clears a nullable field back tonullinstead of setting it; use this to drop a filter rather than change it. Per-subcommand fields:- schedule:
start,severity-labels,min-severity-score,max-severity-score,min-fix-confidence,finding-limit. - new-scan:
severity-labels,min-severity-score,max-severity-score,min-fix-confidence,finding-limit. - pull-request-scan:
target-branch,source-branch,severity-labels,min-severity-score,max-severity-score,min-fix-confidence,finding-limit.
Action-scoped fields (
severity-labels,min/max-severity-score,min-fix-confidence,finding-limit) require--action create-patchon the same call, even when only unsetting. - schedule:
pixee workflow run
pixee workflow run <workflow-id>
Trigger a scheduled workflow on demand. <workflow-id> is the UUID shown in the id column of
pixee workflow list.
run targets schedule workflows specifically —