sddflow 2.7.0__tar.gz → 2.7.1__tar.gz

{sddflow-2.7.0 → sddflow-2.7.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: sddflow
-Version: 2.7.0
+Version: 2.7.1
 Summary: SDD Framework CLI — initialize and upgrade Spec-Driven Development packs
 Project-URL: Homepage, https://github.com/sunil1983us/universalguide
 Project-URL: Repository, https://github.com/sunil1983us/universalguide

{sddflow-2.7.0 → sddflow-2.7.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "sddflow"
-version = "2.7.0"
+version = "2.7.1"
 description = "SDD Framework CLI — initialize and upgrade Spec-Driven Development packs"
 readme = "README.md"
 requires-python = ">=3.9"
@@ -51,6 +51,17 @@ packages = ["sdd"]
 artifacts = ["sdd/packs/**"]
 
 [tool.hatch.build.targets.sdist]
+# artifacts here (not just on the wheel target) is required: `uv build` (and
+# any other build-frontend that builds the wheel FROM the sdist rather than
+# directly from source) inherits whatever the sdist has. Without this, the
+# sdist silently drops the gitignored sdd/packs/ directory — hatchling's
+# default file selection follows VCS/gitignore rules — and the wheel built
+# from that sdist has no packs either, even though the wheel target's own
+# artifacts line looks like it should cover it. `python -m build --wheel`
+# doesn't hit this because it builds the wheel directly from source, bypassing
+# the sdist step entirely — which is why that command alone can't catch this
+# class of bug; verify with `uv build` (or `python -m build`, sdist+wheel).
+artifacts = ["sdd/packs/**"]
 include = [
     "sdd/",
     "README.md",

sddflow-2.7.1/sdd/__init__.py

@@ -0,0 +1 @@
+__version__ = "2.7.1"

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/address-review.md

@@ -0,0 +1,121 @@
+# /address-review
+
+Read all unresolved human review comments on the current PR, present them as a
+checklist, apply the developer's chosen fixes, reply to each thread, and
+request re-review. Works on GitHub, GitLab, Bitbucket, and Azure DevOps — the
+`sdd pr` commands below auto-detect which host this repo is on.
+
+Repeatable — run once per review round until the PR is approved.
+
+## Usage
+
+```
+/address-review           # infer PR number from current branch
+/address-review 42        # explicit PR number
+```
+
+## Step 1 — Fetch unresolved review comments
+
+```bash
+sdd pr comments [--pr-id {number}]
+```
+
+This prints a numbered checklist directly — grouped implicitly by file:line,
+with each comment's author, text, and the `comment_id` needed for later steps.
+
+If it fails (missing host credentials, or a host with no automated listing),
+the error message names exactly what's missing (e.g. `GITLAB_TOKEN`,
+`BITBUCKET_USERNAME`/`BITBUCKET_APP_PASSWORD`). Tell the user, then offer to
+continue manually: read the comments from the host's web UI and proceed from
+Step 3 using whatever ids that UI shows.
+
+If no unresolved comments:
+> No open review comments on PR #{number}. PR is ready to approve.
+Stop here.
+
+## Step 2 — Present checklist
+
+Relay the checklist `sdd pr comments` printed, e.g.:
+
+```
+  ─────────────────────────────────────────────────────────
+  Review Comments — PR #{number}   (GitHub)
+  ─────────────────────────────────────────────────────────
+  [1] src/auth/login.ts:42  —  @jane  (comment_id=123)
+      "This still needs a null check before accessing profile"
+
+  [2] src/auth/login.ts:89  —  @jane  (comment_id=124)
+      "Dead variable retryCount is still present"
+
+  [3] General comment  —  @jane  (comment_id=125)
+      "Missing unit test for the error path"
+  ─────────────────────────────────────────────────────────
+  3 comment(s)
+
+  Which should I fix? Enter numbers (e.g. 1,3), 'all', or 'none':
+```
+
+## Step 3 — Apply selected fixes
+
+Wait for developer input. Accept:
+- `all`  → fix every comment
+- `none` → acknowledge all, fix nothing
+- `1,3`  → fix items 1 and 3; acknowledge the rest
+
+For each selected item:
+- Read the referenced file at the referenced line
+- Apply the fix the reviewer requested
+- No per-fix confirmation needed
+
+Commit all fixes together:
+```bash
+git add <changed files>
+git commit -m "fix(review): address PR #{number} review comments"
+```
+
+Push to the same branch (PR updates automatically):
+```bash
+git push
+```
+
+## Step 4 — Reply to comment threads
+
+For each **fixed** item (using its `comment_id` from Step 1):
+```bash
+sdd pr reply --comment-id {comment_id} \
+  --body "Fixed in $(git rev-parse --short HEAD) — {one-line description of the change}"
+```
+
+For each **acknowledged** (not fixed) item:
+```bash
+sdd pr reply --comment-id {comment_id} \
+  --body "Acknowledged — will address in a follow-up."
+```
+
+## Step 5 — Resolve threads
+
+For each fixed item:
+```bash
+sdd pr resolve --comment-id {comment_id}
+```
+
+Bitbucket has no API-level thread resolution today — the command prints a
+warning and the reviewer resolves it manually after seeing the reply. Treat
+that warning as expected, not a failure to retry.
+
+## Step 6 — Request re-review
+
+```bash
+sdd pr request-review --reviewer {reviewer_login}
+```
+
+If the reviewer's login isn't known, use the comment author field from Step 1.
+
+Print:
+```
+  ✓  Fixes committed and pushed.
+     Replied to {N} thread(s).
+     Re-review requested from @{reviewer}.
+
+  Run /address-review again after they respond.
+```

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/analyze.md

@@ -0,0 +1,7 @@
+---
+description: ANALYZE — Risks, complexity, and traceability analysis
+---
+
+Read and follow ALL instructions in `.github/prompts/analyze.prompt.md` exactly as written, then execute them now.
+
+$ARGUMENTS

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/ava.md

@@ -0,0 +1,5 @@
+---
+description: Ava — Principal Software Architect · /analyze · /plan-design · /specify-doc
+---
+
+Read and follow ALL instructions in `.github/prompts/ava.prompt.md` exactly as written, then execute them now.

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/bug-assess.md

@@ -0,0 +1,7 @@
+---
+description: BUG-ASSESS — Structured bug assessment: reproduce, root cause, impact, fix estimate
+---
+
+Read and follow ALL instructions in `.github/prompts/bug-assess.prompt.md` exactly as written, then execute them now.
+
+$ARGUMENTS

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/bug-fix.md

@@ -0,0 +1,7 @@
+---
+description: BUG-FIX — Implement a bug fix from a BUG-NNN assessment with regression test
+---
+
+Read and follow ALL instructions in `.github/prompts/bug-fix.prompt.md` exactly as written, then execute them now.
+
+$ARGUMENTS

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/change.md

@@ -0,0 +1,7 @@
+---
+description: CHANGE — Raise a change request at any stage. Reads existing documents one by one, classifies each as SKIP/ANNOTATE/UPDATE/RERUN/INCORPORATE, shows targeted diffs, waits for quality check before proceeding. Works for any CR type: Business, Technical, Security, Data, UX, Performance, Operational, or Defect.
+---
+
+Read and follow ALL instructions in `.github/prompts/change.prompt.md` exactly as written, then execute them now.
+
+$ARGUMENTS

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/check-review.md

@@ -0,0 +1,62 @@
+# /check-review
+
+Check the review status of a document and act on the outcome.
+
+## Usage
+
+```
+/check-review           # checks the most recently submitted document
+/check-review brd       # explicit document key
+/check-review hld
+```
+
+## Agent instructions
+
+Run:
+```bash
+sdd review check --doc {doc_key}
+```
+
+Then act based on the exit code:
+
+### Exit 0 — APPROVED
+
+The document is approved. Tell the user clearly:
+
+> ✓ {DOC} approved. Proceeding to {next step}.
+
+Then continue to the next step in the SDD sequence:
+- After BRD → submit SRD for review (`/submit-review srd`)
+- After SRD → submit Arch for review (`/submit-review arch`)
+- After Arch → submit HLD for review (`/submit-review hld`)
+- After HLD → proceed to `/plan-lld` (or next phase)
+- After LLD → submit ADR for review (`/submit-review adr`)
+- After ADR → proceed to `/task`
+- After tasks → proceed to implementation
+
+### Exit 1 — NEEDS REVISION
+
+Review comments were found. Do the following:
+
+1. Read each comment carefully
+2. Edit the document file (`.specify/features/{feature}/{doc}.md`) to address each comment
+3. Run: `sdd review apply --doc {doc_key}` — this re-pushes to Confluence and notifies the reviewer
+4. Tell the user:
+
+> {DOC} updated per review comments. The reviewer ({role}) has been notified to re-review.
+> Run /check-review again after they respond.
+
+### Exit 2 — PENDING
+
+No reviewer response yet. Tell the user:
+
+> ⏳ {DOC} is waiting for {reviewer_role} to respond in Jira.
+> Run /check-review again after they have reviewed.
+
+Stop — do not proceed to the next document.
+
+### Exit 3 — NOT SUBMITTED
+
+The document has not been submitted yet. Tell the user:
+
+> Run /submit-review {doc} first.

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/checklist.md

@@ -0,0 +1,8 @@
+---
+description: CHECKLIST — Spec-quality validation (run after /specify, before /validate)
+argument-hint: optional feature name override
+---
+
+Read and follow ALL instructions in `.github/prompts/checklist.prompt.md` exactly as written, then execute them now.
+
+$ARGUMENTS

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/clarify.md

@@ -0,0 +1,7 @@
+---
+description: CLARIFY — Resolve open questions before planning
+---
+
+Read and follow ALL instructions in `.github/prompts/clarify.prompt.md` exactly as written, then execute them now.
+
+$ARGUMENTS

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/create-context.md

@@ -0,0 +1,7 @@
+---
+description: CREATE-CONTEXT — Turn informal notes into a structured context.md (optional, before /specify)
+---
+
+Read and follow ALL instructions in `.github/prompts/create-context.prompt.md` exactly as written, then execute them now.
+
+$ARGUMENTS

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/implement.md

@@ -0,0 +1,8 @@
+---
+description: IMPLEMENT — Execute one task with PR rules enforced
+argument-hint: TASK-NNN
+---
+
+Read and follow ALL instructions in `.github/prompts/implement.prompt.md` exactly as written, then execute them now.
+
+$ARGUMENTS

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/jira-push.md

@@ -0,0 +1,7 @@
+---
+description: JIRA-PUSH — Push SDD artifacts to Jira via REST API (Epic after BRD, Stories after SRD/UC, Tasks after /task)
+---
+
+Read and follow ALL instructions in `.github/prompts/jira-push.prompt.md` exactly as written, then execute them now.
+
+$ARGUMENTS

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/kai.md

@@ -0,0 +1,5 @@
+---
+description: Kai — Engineering Manager · /task · /taskstoissues
+---
+
+Read and follow ALL instructions in `.github/prompts/kai.prompt.md` exactly as written, then execute them now.

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/leo.md

@@ -0,0 +1,5 @@
+---
+description: Leo — Lead Developer · /plan-lld · /implement · /pre-review · /address-review · /bug-assess · /bug-fix
+---
+
+Read and follow ALL instructions in `.github/prompts/leo.prompt.md` exactly as written, then execute them now.

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/maya.md

@@ -0,0 +1,5 @@
+---
+description: Maya — Senior Business Analyst · /specify-brd · /specify-uc · /validate · /create-context · /change
+---
+
+Read and follow ALL instructions in `.github/prompts/maya.prompt.md` exactly as written, then execute them now.

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/morgan.md

@@ -0,0 +1,5 @@
+---
+description: Morgan — Delivery Manager · /orchestrate
+---
+
+Read and follow ALL instructions in `.github/prompts/morgan.prompt.md` exactly as written, then execute them now.

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/orchestrate.md

@@ -0,0 +1,8 @@
+---
+description: ORCHESTRATE — Drive the full SDLC pipeline as a sequenced multi-agent workflow. Pauses at every human gate. Supports CLI (single-session) and SDK (multi-agent) modes. Use --list to view pipeline status, --from STEP to resume, --to STEP to stop early.
+argument-hint: [--from STEP] [--to STEP] [--list] [--mode multi-agent]
+---
+
+Read and follow ALL instructions in `.github/prompts/orchestrate.prompt.md` exactly as written, then execute them now.
+
+$ARGUMENTS

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/plan-adr.md

@@ -0,0 +1,5 @@
+---
+description: PLAN-ADR — Architecture Decision Records (separate mode, Step 3 of 3, mvp+ only)
+---
+
+Read and follow ALL instructions in `.github/prompts/plan-adr.prompt.md` exactly as written, then execute them now.

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/plan-arch.md

@@ -0,0 +1,5 @@
+---
+description: PLAN-ARCH — Architecture document (separate mode, Step 1 of 3)
+---
+
+Read and follow ALL instructions in `.github/prompts/plan-arch.prompt.md` exactly as written, then execute them now.

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/plan-design.md

@@ -0,0 +1,5 @@
+---
+description: PLAN-DESIGN — Architecture, Diagrams, API Design, and ADRs in one document
+---
+
+Read and follow ALL instructions in `.github/prompts/plan-design.prompt.md` exactly as written, then execute them now.

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/plan-hld.md

@@ -0,0 +1,5 @@
+---
+description: PLAN-HLD — High-level design diagrams (separate mode, Step 2 of 3)
+---
+
+Read and follow ALL instructions in `.github/prompts/plan-hld.prompt.md` exactly as written, then execute them now.

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/plan-lld.md

@@ -0,0 +1,7 @@
+---
+description: PLAN-LLD — Low-level design (mvp+ only)
+---
+
+Read and follow ALL instructions in `.github/prompts/plan-lld.prompt.md` exactly as written, then execute them now.
+
+$ARGUMENTS

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/pre-review.md

@@ -0,0 +1,150 @@
+# /pre-review
+
+Run a one-time code pre-review on the current task's implementation, present a
+checklist of findings, apply the developer's chosen fixes, then create the PR.
+
+Runs ONCE per task — do not re-run after fixes are applied.
+
+## Usage
+
+```
+/pre-review              # infer task from branch name
+/pre-review TASK-001     # explicit task ID
+```
+
+## Step 0 — Check config
+
+Read `.specify/integrations.yml`:
+
+- If `code_review.enabled: false` **or** `code_review.pre_review: false`:
+  > Pre-review is disabled (`code_review.pre_review: false`).
+  > Running `sdd pr create` directly.
+
+  Run `sdd pr create --task {task}` and stop.
+
+## Step 1 — Identify the task
+
+If no task ID was given, extract from the current branch name:
+```bash
+git branch --show-current
+```
+Pattern: `feature/{task-id}-{slug}` → task ID is the segment before the first `-`
+after `feature/` up to and including the issue number (e.g. `task-001` → `TASK-001`).
+
+If still unclear, ask: "Which task is this for? (e.g. TASK-001)"
+
+## Step 2 — Get the diff
+
+```bash
+git diff $(git merge-base HEAD origin/main)...HEAD
+git diff HEAD
+```
+
+For any file with more than 3 changed hunks, read the full file — partial
+context misses bugs in unchanged lines adjacent to the diff.
+
+## Step 3 — Analyse (6 angles, ≤ 10 findings total)
+
+### A — Correctness  [HIGH]
+Off-by-one, null/undefined deref before check, inverted condition, missing
+`await`, wrong variable in copy-paste, error swallowed in catch, falsy-zero
+treated as "not set".
+
+### B — Removed behaviour  [HIGH]
+For every deleted or replaced line: name the invariant it enforced, then
+check whether the new code re-establishes it. Deleted guard = candidate.
+
+### C — Security  [HIGH]
+Hardcoded secrets or tokens, SQL/command/path injection, unvalidated external
+input used in a query or shell call, auth check removed or bypassed, sensitive
+data written to logs.
+
+### D — Cross-file impact  [MEDIUM]
+For changed function signatures, grep callers. Does any call site break?
+New precondition not satisfied? Changed return type not handled upstream?
+
+### E — Quality  [LOW]
+Copy-paste with slight variation, dead code left behind, deeply nested logic
+that could be flattened, state that is derivable rather than stored.
+
+### F — Performance  [LOW]
+N+1 query inside a loop, redundant computation per call, blocking I/O on a
+hot path, large closure that captures the full enclosing scope.
+
+Drop any finding without a concrete failure scenario.
+
+## Step 4 — Present checklist
+
+If no findings:
+> No issues found. Proceeding to PR creation.
+Skip to Step 7.
+
+Otherwise print:
+
+```
+  ─────────────────────────────────────────────────────
+  Pre-Review — {TASK-ID}
+  ─────────────────────────────────────────────────────
+  [1] HIGH  bug       src/auth/login.ts:42
+      Null deref: user.profile accessed before null check
+      Fix: add  if (!user.profile) return res.status(400)...
+
+  [2] HIGH  security  src/auth/login.ts:67
+      SQL injection: query built with string concat
+      Fix: use parameterised query  db.query('...', [input])
+
+  [3] MED   quality   src/auth/login.ts:89
+      Dead variable: retryCount set but never read
+      Fix: remove the variable
+
+  [4] LOW   perf      src/users/list.ts:23
+      N+1 query: findUser() called inside a loop
+      Fix: batch with  findUsers([ids])
+  ─────────────────────────────────────────────────────
+  4 finding(s) — 2 high · 1 medium · 1 low
+
+  Which should I fix? Enter numbers (e.g. 1,3), 'all', or 'none':
+```
+
+## Step 5 — Apply selected fixes
+
+Wait for developer input. Accept:
+- `all`   → fix every finding
+- `none`  → acknowledge all, fix nothing
+- `1,3`   → fix items 1 and 3; acknowledge the rest
+
+Apply all selected fixes at once — no per-fix confirmation needed.
+
+Commit:
+```bash
+git add <changed files>
+git commit -m "fix(pre-review): address pre-review findings for {TASK-ID}"
+```
+
+## Step 6 — Save pre-review summary
+
+Read feature name from `.specify/manifest.yml` → `project.feature`.
+Write to `.specify/features/{feature}/.pre-review-{task-id-lowercase}.md`:
+
+```markdown
+## Pre-Review Summary — {TASK-ID}
+
+Fixed:
+- [1] HIGH bug: null deref on user.profile (login.ts:42)
+- [2] HIGH security: SQL injection via string concat (login.ts:67)
+
+Acknowledged (not fixed):
+- [3] MED quality: dead variable `retryCount` (login.ts:89)
+- [4] LOW perf: N+1 query in user list (list.ts:23)
+```
+
+If developer chose `none`: list all under "Acknowledged (not fixed)".
+If no findings: write `No issues found in pre-review.`
+
+## Step 7 — Create the PR
+
+```bash
+sdd pr create --task {TASK-ID}
+```
+
+The CLI reads the summary file and includes it in the PR body automatically.

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/quinn.md

@@ -0,0 +1,5 @@
+---
+description: Quinn — QA Lead · /checklist
+---
+
+Read and follow ALL instructions in `.github/prompts/quinn.prompt.md` exactly as written, then execute them now.

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/release.md

@@ -0,0 +1,7 @@
+---
+description: RELEASE — UAT + deployment plan + go-live gate
+---
+
+Read and follow ALL instructions in `.github/prompts/release.prompt.md` exactly as written, then execute them now.
+
+$ARGUMENTS

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/rex.md

@@ -0,0 +1,5 @@
+---
+description: Rex — Senior Requirements Engineer · /specify-srd · /clarify
+---
+
+Read and follow ALL instructions in `.github/prompts/rex.prompt.md` exactly as written, then execute them now.

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/riley.md

@@ -0,0 +1,5 @@
+---
+description: Riley — Release Manager · /release
+---
+
+Read and follow ALL instructions in `.github/prompts/riley.prompt.md` exactly as written, then execute them now.

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/specify-brd.md

@@ -0,0 +1,5 @@
+---
+description: SPECIFY-BRD — Generate Business Requirements Document (gate: GATE-1 passed)
+---
+
+Read and follow ALL instructions in `.github/prompts/specify-brd.prompt.md` exactly as written, then execute them now.

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/specify-doc.md

@@ -0,0 +1,7 @@
+---
+description: SPECIFY-DOC — Generate any extended spec document: security, api-spec, data-model, etc.
+---
+
+Read and follow ALL instructions in `.github/prompts/specify-doc.prompt.md` exactly as written, then execute them now.
+
+$ARGUMENTS

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/specify-srd.md

@@ -0,0 +1,5 @@
+---
+description: SPECIFY-SRD — Generate Software Requirements Document (gate: BRD approved)
+---
+
+Read and follow ALL instructions in `.github/prompts/specify-srd.prompt.md` exactly as written, then execute them now.

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/specify-uc.md

@@ -0,0 +1,7 @@
+---
+description: SPECIFY-UC — Generate Use Case Specification (Actors + MP/AP/EP)
+---
+
+$ARGUMENTS
+
+Follow the instructions in `.github/prompts/specify-uc.prompt.md`.

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/specify.md

@@ -0,0 +1,7 @@
+---
+description: SPECIFY — Constitution Part 2 (DRAFT) + spec documents for this scope
+---
+
+Read and follow ALL instructions in `.github/prompts/specify.prompt.md` exactly as written, then execute them now.
+
+$ARGUMENTS

sddflow-2.7.1/sdd/packs/sdd-backend-service/.claude/commands/start.md

@@ -0,0 +1,24 @@
+---
+description: Startup — read framework files and confirm project state (Step 0)
+---
+
+<!-- shared:start-command-body:start -->
+Read and follow the "Startup (every session)" steps in `CLAUDE.md`:
+- `.specify/manifest.yml`
+- `.specify/memory/constitution.md`
+- `.specify/memory/summary-rules.md`
+- `.specify/memory/change-rules.md`
+- `.specify/memory/roles.yml`
+- `.github/instructions/*.instructions.md` (apply each file's `applyTo` glob — AI-7)
+
+Then confirm:
+- Project name, scope (pilot/mvp/full), feature, context file
+- Constitution Part 2: generated? finalized (GATE-1)?
+- Commands available for this scope
+- PR rules (max lines/files per PR)
+
+State which command is ready to run next. If Part 2 is generated but not
+finalized, remind the user to complete GATE-1 before `/validate`.
+<!-- shared:start-command-body:end -->
+
+$ARGUMENTS