vzhukovs

close

Close out a merged issue: harvest what was learned, clean up worktrees.

exec

Implement the plan, one task per worker, each producing a receipt.

plan-review

Adversarial review of a plan, before any code is written.

plan

Plan an issue: scout the code, resolve the open choices, and produce a plan with executable done-criteria.

pr-sync

Process review feedback: triage threads, fix, reply, resolve.

pr

Create branches and pull requests. The only command that writes to GitHub.

preflight

Run the deterministic gates and report pass or fail.

reset

Start one issue over: forget its plan, research and artefacts so the next cycle runs from nothing. Touches no other issue, and nothing upstream.

resume

Come back to an issue after a break: drift analysis, rebase, plan amendment.

review-pr

Review someone else's pull request along four parallel axes.

slice

Turn one change set into a verified graph of atomic pull requests.

triage

Triage an upstream podman-desktop issue: dedup, classify, draft requirements, and pick a route. Without an issue number, shortlist what is worth taking.

validate

Drive the built application, collect evidence, and propose an e2e test.

audit

Audit the diff against the plan in fresh context.

quickfix

Small fix without the planning ceremony.

doctor

Check the pdkit environment: required tools, optional MCP servers, hook wiring, and gate self-test.

knowledge

Revise the shipped knowledge base against what recent work actually showed.

package-map

Explains which podman-desktop package owns a piece of functionality and which layer is responsible. Use when asked where something lives, which package to change, or what a layer is for.

pr-status

Dashboard across all open pull requests: CI, review threads, staleness.

upstream-rules

The non-negotiable rules of the podman-desktop repository: SPDX headers, conventional commits with a package scope, Signed-off-by, schema regeneration, squashing without interactive rebase.