gald3r Commands — Full Reference

Complete usage, arguments, syntax, and behavioral notes for every gald3r command, extracted from each command file in project_template/.claude/commands/. Invoke commands with the @g- prefix (Cursor) or /g- prefix (Claude Code). For the grouped one-line index, see Commands.

Total commands: 182

---

@g-agent-hire

Adds a new gald3r agent through a four-phase research-gated workflow so

Usage:

@g-agent-hire "<role description>"
@g-agent-hire "<role description>" --reference <repo-or-url>          # optional: prime research with a specific reference
@g-agent-hire "<role description>" --skill <existing-skill-id>        # optional: pre-declare an owned skill
@g-agent-hire status                                                  # show the current draft state if a hire is in progress
@g-agent-hire cancel                                                  # abort an in-progress hire and discard the draft

Notes:

• @g-skl-agent-creator is not a precondition for this command —

the skill name appears in T1017's spec but no such skill currently ships with gald3r. @g-agent-hire itself IS the workflow; future refactor may extract reusable phases into a g-skl-agent-creator skill, in which case this command will delegate. For now: this command is self-contained.

• Platform parity is intentional: an agent that exists only in

.cursor/ is effectively unhired for users on Claude Code, Codex, OpenCode, etc. The default target set is "every platform that supports the agents/ primitive" as declared in .gald3r_sys/_platform_capabilities.json.

• Estimated context-impact band should be conservative — medium

unless you can demonstrate the agent is reliably low. Over-declaring causes mild dispatch conservatism; under-declaring causes context exhaustion (same contract as token_budget: in SKILL.md).

Related:

• T1017 — original task spec .
• T1172a — token_budget: ordinal bands (re-used here for the

agent's "Estimated context impact").

• custom_scripts/platform_parity_sync.ps1 — controller parity machinery

invoked in Phase 4.

• AGENTS.md "Agents" roster table — canonical source-of-truth for the

active agent set.

_Source: g-agent-hire.md_

---

@g-bug-add

Report a new bug. Activates g-skl-bugs → REPORT BUG operation.

Usage:

@g-bug-add "Description of the bug"
@g-bug-add "Description" --severity high --file path/to/file.py --line 42

_Source: g-bug-add.md_

---

@g-bug-archive

Archive terminal bug history into .gald3r/archive/ while keeping BUGS.md as an active quality index.

Usage:

@g-bug-archive --dry-run
@g-bug-archive --apply
@g-bug-archive --dry-run --include-recent

What This Command Does:

Delegates to g-skl-bugs -> ARCHIVE BUGS.

The command moves resolved/closed bug history out of the active index and into count-based archive buckets:

• Index files: .gald3r/archive/archive_bugs_0000_0999.md, .gald3r/archive/archive_bugs_1000_1999.md, ...
• Bug files: .gald3r/archive/bugs/bugs_0000_0999/, .gald3r/archive/bugs/bugs_1000_1999/, ...

Buckets hold at most 1000 archive entries/files and are assigned by archive entry ordinal, not by BUG-NNN.

_Source: g-bug-archive.md_

---

@g-bug-del

Close/archive a bug record. Activates g-skl-bugs → CLOSE BUG operation.

Usage:

@g-bug-del BUG-NNN --reason "Won't fix — by design"
@g-bug-del BUG-NNN --resolved "Fixed in TASK-NNN"

_Source: g-bug-del.md_

---

@g-bug-fix

Fix a bug. Activates g-bugs → FIX BUG operation.

Usage:

@g-bug-fix

_Source: g-bug-fix.md_

---

@g-bug-report

Report a bug. Activates g-skl-bugs → REPORT BUG operation.

Usage:

@g-bug-report

_Source: g-bug-report.md_

---

@g-bug-upd

Update a bug record. Activates g-skl-bugs → UPDATE BUG operation.

Usage:

@g-bug-upd BUG-NNN status resolved
@g-bug-upd BUG-NNN severity critical
@g-bug-upd BUG-NNN add-note "Found root cause: null guard missing"

_Source: g-bug-upd.md_

---

@g-cleanup

Deprecated — use g-medic instead.

Usage:

@g-cleanup

_Source: g-cleanup.md_

---

@g-cli-claude

Claude Code CLI quick reference — headless flags, session continuation, MCP config, permissions, overnight use.

Usage:

@g-cli-claude

_Source: g-cli-claude.md_

---

@g-cli-codex

OpenAI Codex CLI quick reference — approval modes, sandbox config, provider/model flags, session management, CI/overnight use.

Usage:

@g-cli-codex

_Source: g-cli-codex.md_

---

@g-cli-copilot

Activate g-skl-cli-copilot for GitHub Copilot CLI operations.

Usage:

@g-cli-copilot

_Source: g-cli-copilot.md_

---

@g-cli-cursor

Cursor CLI quick reference — Agent/Plan/Ask/Debug modes, Cloud Agent handoff, session management.

Usage:

@g-cli-cursor

_Source: g-cli-cursor.md_

---

@g-cli-gemini

Gemini CLI quick reference — auth, checkpointing, config, extensions, cross-agent use.

Usage:

@g-cli-gemini

_Source: g-cli-gemini.md_

---

@g-code-review

Activate the g-skl-code-review skill.

Usage:

@g-code-review

_Source: g-code-review.md_

---

@g-codeowners-gen

Generate .github/CODEOWNERS from subsystem owners

Usage:

@g-codeowners-gen [arguments]

Flags:

Flag	Effect
--dry-run	Print the would-be CODEOWNERS to stdout without writing the file

Behavior:

Runs the helper .claude/skills/g-skl-github-pr/scripts/codeowners_gen.py:

1. Read every .gald3r/subsystems/**/*.md spec (skipping SUBSYSTEM* index/graph artifacts).
2. For each spec with a non-empty owners: list, emit one CODEOWNERS line per

locations.code: path → owners (usernames get a leading @; @org/team slugs pass through).

1. Write .github/CODEOWNERS with the header

# Auto-generated by g-codeowners-gen — do not hand-edit above the marker.

1. Preserve anything below the # CUSTOM ENTRIES BELOW marker on regeneration.
2. UTF-8 without BOM.

uv run python .claude/skills/g-skl-github-pr/scripts/codeowners_gen.py -DryRun
uv run python .claude/skills/g-skl-github-pr/scripts/codeowners_gen.py

Notes:

• Idempotent and safe to re-run; the auto block is rewritten, custom entries kept.
• Populate a subsystem's owners: via g-skl-subsystems (T1298).
• Pairs with the "Require review from Code Owners" branch-protection rule

(.gald3r/config/branch_protection.md, T1295).

_Source: g-codeowners-gen.md_

---

@g-command-new

Creates a new command for your own project. You choose where it lives - your AI platform folder

Usage:

@g-command-new <verb-noun>
@g-command-new "deploy-staging"

_Source: g-command-new.md_

---

@g-compliance-gate

Activate the g-skl-compliance skill and run a GATE operation

Usage:

# Pre-push compliance check
python .claude/skills/g-skl-compliance/scripts/run_compliance_scan.py -Scanner auto
if [ "$?" -eq 2 ]; then
    echo "COMPLIANCE FAIL — push blocked. Run @g-compliance-report for details." >&2
    exit 1
fi

Behavior:

• If no report exists: runs SCAN first, then evaluates verdict
• If COMPLIANCE_GATE_STRICT=1 env var is set: exit 1 (WARN) also blocks
• Prints blocking packages to stderr on FAIL

What This Command Does:

Returns a machine-readable compliance verdict suitable for pre-push hooks and CI/CD pipelines. Reads the most recent .gald3r/reports/compliance_*.md report.

Related Commands:

• @g-compliance-scan — run a fresh scan
• @g-compliance-report — display full report with findings

_Source: g-compliance-gate.md_

---

@g-compliance-report

Activate the g-skl-compliance skill and run a REPORT operation

Usage:

@g-compliance-report [arguments]

What This Command Does:

Displays the most recent compliance scan report from .gald3r/reports/compliance_*.md.

Related Commands:

• @g-compliance-scan — run a new scan
• @g-compliance-gate — machine-readable verdict for hooks

_Source: g-compliance-report.md_

---

@g-compliance-scan

Activate the g-skl-compliance skill and run a SCAN operation

Usage:

@g-compliance-scan [arguments]

Options:

Option	Description
--scanner <name>	Override auto-detection (ort\	fossa\	snyk\	pmd\	fallback)
--path <dir>	Scan a specific directory instead of cwd

What This Command Does:

Runs a dependency/license scan against the current repository and writes a structured compliance report to .gald3r/reports/compliance_YYYYMMDD.md.

_Source: g-compliance-scan.md_

---

@g-compress-memory

Compress the non-gald3r sections of memory files (AGENTS.md/CLAUDE.md/memory.md) to cut

Usage:

@g-compress-memory                 # SCAN (dry-run) AGENTS.md + CLAUDE.md
@g-compress-memory AGENTS.md       # scan a specific file
@g-compress-memory AGENTS.md --apply   # compress + apply (shows diff, asks confirmation first)

What It Does:

1. SCAN (default, no writes): runs gald3r_compress_memory.py to report protected vs

compressible token budgets and the ≥30% target.

1. COMPRESS: the agent rewrites only the compressible region (terse facts, drop redundant

examples, dedup) — never the gald3r SECTION range, code blocks, or URLs.

1. APPLY: writes the new file only after showing a diff and getting explicit confirmation;

the helper refuses unless the protected gald3r range is byte-identical.

In the gald3r source repo the whole memory file is gald3r-managed, so SCAN reports skip.

Helper: .claude/skills/g-skl-compress-memory/scripts/gald3r_compress_memory.py

_Source: g-compress-memory.md_

---

@g-constraint-add

Add a new architectural constraint to .gald3r/CONSTRAINTS.md.

Usage:

@g-constraint-add

_Source: g-constraint-add.md_

---

@g-constraint-check

Validate the current task or implementation against all active constraints in .gald3r/CONSTRAINTS.md.

Usage:

@g-constraint-check

_Source: g-constraint-check.md_

---

@g-constraint-del

Deprecate a constraint. Activates g-skl-constraints → DEPRECATE operation.

Usage:

@g-constraint-del C-NNN
@g-constraint-del C-NNN --reason "Superseded by C-NNN"

_Source: g-constraint-del.md_

---

@g-constraint-upd

Update an existing constraint. Activates g-skl-constraints → UPDATE operation.

Usage:

@g-constraint-upd C-NNN
@g-constraint-upd C-NNN --field enforcement --value "Enforced by g-go-code AC gate step b2"

_Source: g-constraint-upd.md_

---

@g-crash-stats

Show CRASH activation stats (Commands / Rules / Agents / Skills / Hooks)

Usage:

uv run python -c "from gald3r import crash; crash.record_activation('skill','g-skl-tasks',trigger_source='@g-status',force=True)"

What This Command Does:

Displays the CRASH activation tracking report (T433) — datetime invocation statistics for the five gald3r extension-point types: Commands, Rules, Agents, Skills, Hooks. It answers: what is actually being invoked, what is never called, and what should be called (declares intent) but isn't.

The data lives in .gald3r/logs/crash_activations.jsonl — one JSON line per activation: {component_type, component_name, activated_at, session_id, trigger_source, elapsed_ms}.

_Source: g-crash-stats.md_

---

@g-create-hook

Scaffold a new gald3r hook script + companion hook.md self-description in one step.

Usage:

@g-hook-create <hook-name> <event>

What It Does:

<2-3 sentence description of the hook's job — what it inspects, what it decides>

Related:

• Task: T1171 (OpenClaw hook.md self-description pattern → gald3r hooks)
• Source: V18 OpenClaw Hooks Crash Course harvest (Bdr7afGhh4I, 2026-05-13)
• Skill: hook-create (generic Cursor hook authoring)
• Skill: g-skl-platform-cursor, g-skl-platform-claude (hook.md companion pattern documentation)

_Source: g-create-hook.md_

---

@g-crr

Clean-room rewrite pipeline — harvest a repo, write all findings to IDEA_BOARD, create tasks for top candidates, and produce a gald3r-native implementation spec. Calls separate agents per phase.

Usage:

@g-crr https://github.com/owner/repo
@g-crr https://github.com/owner/repo --target-subsystem 3d-pipeline
@g-crr https://github.com/owner/repo --ideas-only
@g-crr https://github.com/owner/repo --no-spec
@g-crr https://github.com/owner/repo --mode fast
@g-crr STATUS owner__repo
@g-crr RESUME owner__repo

Flags:

Flag	Effect
--target-subsystem <name>	Name of the gald3r subsystem the rewrite targets (read from SUBSYSTEMS.md)
--ideas-only	Stop after Phase 2 — no tasks, no spec
--no-spec	Run Phases 1–3, skip Phase 4 spec task
--mode fast	Route Phase 1/3/4 subagents to haiku-class models
STATUS <slug>	Show recon report status for a previously analyzed slug
RESUME <slug>	Resume from last completed phase (idempotent)

See Also:

• @g-recon-repo — Lightweight capture only
• @g-res-deep — Deep 5-pass analysis (Phase 1 of this pipeline)
• @g-res-review — Review existing recon reports
• @g-res-apply — Apply approved features to .gald3r/

_Source: g-crr.md_

---

@g-curator

Activate the g-skl-curator skill — autonomous skill library audit.

Usage:

@g-curator

_Source: g-curator.md_

---

@g-dependency-graph

Activate g-skl-dependency-graph to generate or refresh dependency graphs for tasks and/or subsystems.

Usage:

@g-dependency-graph

_Source: g-dependency-graph.md_

---

@g-doctor

Validate the complete gald3r environment: Docker MCP health, .gald3r/ structure, vault configuration,

Usage:

@g-doctor                # Full health report (read-only)
@g-doctor --fix          # Apply safe auto-fixes (narrow scope — see below)
@g-doctor identity       # Identity & Config checks only
@g-doctor tasks          # Task sync checks only
@g-doctor mcp            # MCP / Docker checks only
@g-doctor vault          # Vault checks only
@g-doctor platform       # Platform IDE parity checks only

Related Commands:

• @g-setup — Initialize or repair a gald3r project
• @g-medic — Deep .gald3r/ structural health and intervention
• @g-status — Project task/bug/phase status overview
• @g-vault-lint — Vault integrity check and index regeneration

_Source: g-doctor.md_

---

@g-feat-add

Stage a new feature. Activates g-skl-features → STAGE operation.

Usage:

@g-feat-add "Feature Name"
@g-feat-add "Feature Name" --goal G-01
@g-feat-add "Feature Name" --tier full
@g-feat-add "Feature Name" --from-harvest research/harvests/repo_slug/
@g-feat-add "Feature Name" --skip-match

_Source: g-feat-add.md_

---

@g-feat-del

Archive a feature staging doc. Activates g-skl-features → ARCHIVE FEATURE operation.

Usage:

@g-feat-del feat-NNN
@g-feat-del feat-NNN --reason "Superseded by feat-MMM"

_Source: g-feat-del.md_

---

@g-feat-new

Stage a new feature in the feature backlog. Activates g-skl-features → STAGE operation.

Usage:

@g-feat-new

_Source: g-feat-new.md_

---

@g-feat-promote

Promote a specced feature to committed — triggers interactive task creation. Activates g-skl-features → PROMOTE operation.

Usage:

@g-feat-promote

_Source: g-feat-promote.md_

---

@g-feat-rename

Rename a feature slug and title. Activates g-skl-features → RENAME operation.

Usage:

@g-feat-rename

_Source: g-feat-rename.md_

---

@g-feat-upd

Update a staging feature doc. Activates g-skl-features → UPDATE FEATURE operation.

Usage:

@g-feat-upd feat-NNN status specced
@g-feat-upd feat-NNN min-tier full
@g-feat-upd feat-NNN goal G-02
@g-feat-upd feat-NNN add-subsystem voice-speech-system

_Source: g-feat-upd.md_

---

@g-git-commit

Create a git commit

Usage:

@g-git-commit

What This Command Does:

Creates a well-structured git commit integrated with the gald3r task management system.

_Source: g-git-commit.md_

---

@g-git-push

Run gald3r push-gate before git push to distinguish routine pushes from release pushes. Complements @g-git-sanity / g-hk-pre-commit.py and shared .claude/skills

Usage:

❌ COMPLIANCE GATE BLOCKED
Scanner: ORT
Packages with FAIL-level violations: 3
Report: .gald3r/reports/compliance_scan_2026-05-09.json
Review with: @g-compliance-report

Violations must be resolved or explicitly approved before pushing.
Run @g-compliance-scan for details, or set GALD3R_PUSH_GATE_OVERRIDE=1 to override.

_Source: g-git-push.md_

---

@g-git-sanity

Run a quick sanity check on staged changes before committing. Covers secrets detection, large files, gald3r sync drift, and Workspace-Control repo boundaries.

Usage:

@g-git-sanity          # Check all staged changes
@g-git-sanity secrets  # Secrets check only
@g-git-sanity size     # Large file check only
@g-git-sanity sync     # gald3r task sync check only

_Source: g-git-sanity.md_

---

@g-go-bugs-swarm

Parallel bug-fix swarm — coordinate multiple bug fixes simultaneously

Usage:

@g-go-bugs-swarm                    # all open bugs in parallel, critical→high→medium→low
@g-go-bugs-swarm severity:critical  # only critical bugs, max parallelism
@g-go-bugs-swarm severity:critical,high  # critical + high
@g-go-bugs-swarm bug:BUG-042,BUG-043    # specific bugs in parallel
@g-go-bugs-swarm --dry-run          # preview fix queue and bucket plan

Examples:

@g-go-bugs-swarm                    # all open bugs in parallel
@g-go-bugs-swarm severity:critical  # only critical bugs
@g-go-bugs-swarm bug:BUG-042,BUG-043,BUG-044  # specific bug batch

See @g-go-bugs for sequential (single-agent-per-bug) variant.

Let's swarm those bugs.

_Source: g-go-bugs-swarm.md_

---

@g-go-bugs

Dedicated bug-fix pipeline — reproduce → fix → regression test → adversarial review

Usage:

@g-go-bugs                          # fix all open bugs, critical→high→medium→low
@g-go-bugs severity:critical,high   # only critical + high
@g-go-bugs severity:medium,low      # only medium + low
@g-go-bugs bug:BUG-042              # specific bug
@g-go-bugs bug:BUG-042,BUG-043      # specific bugs (comma-separated)
@g-go-bugs --dry-run                # report what would be fixed, no changes

Examples:

@g-go-bugs                          # fix all open bugs
@g-go-bugs severity:critical,high   # blitz critical + high only
@g-go-bugs bug:BUG-042              # fix one specific bug
@g-go-bugs --dry-run                # preview fix queue

For parallel execution (faster on large bug queues):

@g-go-bugs-swarm
@g-go-bugs-swarm severity:critical

Let's fix some bugs.

_Source: g-go-bugs.md_

---

@g-go-code-swarm

Alias for @g-go-code --swarm

Usage:

@g-go-code-swarm
@g-go-code-swarm tasks 7, 9, 10, 11, 12
@g-go-code-swarm bugs-only

_Source: g-go-code-swarm.md_

---

@g-go-code

Implementation-only backlog execution

Usage:

@g-go-code
@g-go-code tasks 14, 15
@g-go-code bugs BUG-001, BUG-002
@g-go-code subsystem cross-project
@g-go-code bugs-only
@g-go-code --swarm
@g-go-code --swarm tasks 7, 9, 10, 11, 12
@g-go-code --swarm bugs-only
@g-go-code --mode fast tasks 14, 15
@g-go-code --mode standard tasks 14, 15
@g-go-code --mode cheap bugs BUG-001
@g-go-code --swarm --mode fast
@g-go-code --max-iterations 3 tasks 14, 15, 16, 17, 18
@g-go-code --timeout-minutes 15 bugs-only
@g-go-code --max-iterations 10 --timeout-minutes 60 --swarm
@g-go-code --max-iterations 1 tasks 14
@g-go-code --skip-post-lint docs-only

Behavior:

When $ARGUMENTS contains --resume T{id}:

1. Locate the worktree for T{id} via gald3r worktree resume -TaskId {id} -Role code -Owner {owner}. The helper reads .gald3r-worktree.json (last_checkpoint_sha, continuity_artifact_path) and the worktree's continuity_artifact.md.
2. Print the resume banner (verbatim format):

   Resuming from checkpoint {sha} — {N} ACs complete, {M} remaining

{N}/{M} are the checked (- [x]) / unchecked (- [ ]) AC counts read from the artifact.

1. Inject the artifact as a context prefix — the artifact body (returned as context_prefix under -Json) is prepended to the implementation context so the resumed session re-grounds on the goal, the ACs already done, and the next planned action before claiming new tool work.
2. Continue the b/c/d/e/f loop from the pending ACs. The worktree, branch, and last_checkpoint_sha are reused — no new worktree is created for the resumed task.

_Source: [g-go-code.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-go-code.md)_

---

## `@g-go-go`

Maximal workspace swarm autopilot — rolling implement/review until a hard stop

**Usage:**

@g-go-go @g-go-go --budget 5 @g-go-go --heartbeat 15m @g-go-go --controller-only @g-go-go --controller-only --budget 3 @g-go-go tasks 220, 222, 223 @g-go-go bugs-only @g-go-go subsystem multiple-ide-platform-parity @g-go-go --target-branch main # default: PASS items merge to main (feature-branches-only model) @g-go-go --no-auto-merge # disable auto-merge; reviewer leaves [MERGE-BLOCKED] for human @g-go-go --target-branch staging # merge to a custom branch instead of main @g-go-go --repos example_agent --budget 3 # scope autopilot to example_agent tasks only @g-go-go --repos example_agent,example_desktop # scope autopilot to two specific member repos @g-go-go --reset-every 3 # [--legacy only] Rolling Amnesia cadence (deprecated; inert under the default conductor) @g-go-go --reset-every 6 # less frequent context resets (longer-lived coordinator sessions) @g-go-go --no-reset # disable Rolling Amnesia; use the legacy iteration-count throttle @g-go-go --resume .gald3r/logs/ggo_run_state.json # resume after a scheduled reset (normally issued by the hook) @g-go-go # DEFAULT: T630 stateless conductor (gald3r autopilot loop), fresh coordinator per iteration @g-go-go --stateless --budget 8 # stateless run, 8-iteration budget @g-go-go --legacy # force the DEPRECATED single-session loop (was the old default) @g-go-go --subsystem MEMORY_AND_KNOWLEDGE # T632: scope this coordinator to one subsystem (Pro+) @g-go-go --subsystem UI_AND_OUTPUT # a second, disjoint-scope coordinator may run in parallel @g-go-go --no-context-aware # disable context-aware throttle (full N at all context levels) @g-go-go --no-context-aware --budget 3 # short burst: max parallelism, no throttle @g-go-go --no-code-swarm # Phase 1 sequential coding (1 task at a time); Phase 2 review swarm unchanged @g-go-go --no-code-swarm --budget 3 # safe debugging mode: sequential coding, parallel review

_Source: [g-go-go.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-go-go.md)_

---

## `@g-go-review-swarm`

Alias for @g-go-review --swarm

**Usage:**

@g-go-review-swarm @g-go-review-swarm tasks 14 15 16 17 18 @g-go-review-swarm bugs BUG-013 BUG-014 @g-go-review-swarm tasks 14 15 bugs BUG-013

_Source: [g-go-review-swarm.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-go-review-swarm.md)_

---

## `@g-go-review`

Verification-only backlog review

**Usage:**

@g-go-review @g-go-review tasks 14 15 16 @g-go-review tasks 14 @g-go-review --swarm @g-go-review --swarm tasks 14 15 16 17 18

_Source: [g-go-review.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-go-review.md)_

---

## `@g-go-status`

Show whether an active g-go-go run is ALIVE, IDLE-WAIT, or STALLED

**Usage:**

@g-go-status # status of the run rooted at the nearest .gald3r @g-go-status --json # machine-readable (for scripts / CI gates / dashboards)

**Notes:**

- The reader depends on the marker being refreshed per-iteration (reliable after the
  BUG-181/182 conductor fixes). If the marker is stale but commits are recent, the commit
  signal keeps the verdict honest.
- PID liveness is best-effort: it uses a recorded `conductor_pid`/`pid` if present, otherwise
  reports `in-session` (when the marker mode indicates an in-session coordinator) or `unknown`.
  It never fails the verdict on a missing PID.

_Source: [g-go-status.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-go-status.md)_

---

## `@g-go-swarm`

Alias for @g-go --swarm

**Usage:**

@g-go-swarm @g-go-swarm tasks 7, 9, 10, 11, 12 @g-go-swarm bugs-only @g-go-swarm --workspace @g-go-swarm --workspace tasks 220, 221, 222

_Source: [g-go-swarm.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-go-swarm.md)_

---

## `@g-go-xreview`

Cross-vendor verification review (A7 / T495)

**Usage:**

@g-go-xreview @g-go-xreview tasks 14 15 16 @g-go-xreview tasks 14 @g-go-xreview --swarm @g-go-xreview --swarm tasks 14 15 16 17 18

**Related:**

- Skill: `g-skl-cross-review` (implementation; delegates to `src/review/`)
- Base review machinery: `@g-go-review`, `@g-go-review-swarm`
- Orchestrator: `gald3r_agent/src/review/` — `CrossVendorReview`, `build_review_bundle`, `select_reviewer_harness`
- Design spec: `.gald3r/specifications_collection/SPEC-A7-cross-vendor-review.md` (T495, EPIC T488)

Ready to review.

_Source: [g-go-xreview.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-go-xreview.md)_

---

## `@g-go`

Pipeline orchestrator — implement then auto-review

**Usage:**

@g-go @g-go tasks 7, 9, 12 @g-go bugs BUG-003, BUG-007 @g-go subsystem vault-hooks-automation @g-go bugs-only @g-go --swarm @g-go --swarm tasks 7, 9, 10, 11, 12 @g-go --swarm bugs-only @g-go --workspace @g-go --workspace tasks 220, 221 @g-go --swarm --workspace @g-go --swarm --workspace tasks 220, 221, 222 @g-go --mode fast tasks 7, 9 @g-go --mode standard tasks 7, 9 @g-go --swarm --mode fast tasks 7, 9, 10, 11 @g-go --swarm --mode cheap bugs-only @g-go --max-iterations 3 tasks 7, 9, 10, 11, 12 @g-go --timeout-minutes 15 bugs-only @g-go --max-iterations 10 --timeout-minutes 60 --swarm @g-go --swarm --workspace --max-iterations 8 --timeout-minutes 45

_Source: [g-go.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-go.md)_

---

## `@g-goal-update`

Update project goals. Activates g-project → UPDATE PROJECT.MD (Goals section).

**Usage:**

@g-goal-update

_Source: [g-goal-update.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-goal-update.md)_

---

## `@g-goal`

Set, view, or clear a persistent session goal that locks the agent on target across iterations

**Usage:**

@g-goal [arguments]

**What It Does:**

`@g-goal` writes a session-persistent goal to `.gald3r/config/ACTIVE_GOAL.md` (YAML frontmatter). Once set:

- `g-go`, `g-go-code`, and `g-go-go` read the goal at session start and inject it as `CURRENT GOAL: <description>` into working context.
- After every AC-gate iteration, the implementing agent self-checks: "Does this action advance the goal?" — drift triggers a re-anchor pass.
- The goal survives context compression and session restarts (file-backed persistence).
- A `turn_budget` (default 50) tracks consumed turns; when exhausted, the loop surfaces a budget notice and pauses for user direction.

This locks the agent on target: the goal is re-checked each turn, drift is self-corrected, and the loop exits gracefully when the turn budget is exhausted.

**Related:**

- Spec: `.gald3r/tasks/task965_g_go_persistent_goal_ralph_loop.md`
- Pattern: persistent session goal with turn-budget exit
- Integrates with: `g-go`, `g-go-code`, `g-go-go`
- Config file: `.gald3r/config/ACTIVE_GOAL.md`

Let's go.

_Source: [g-goal.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-goal.md)_

---

## `@g-grooming`

Deprecated — use g-medic instead.

**Usage:**

@g-grooming

_Source: [g-grooming.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-grooming.md)_

---

## `@g-hotfix-open`

Open an urgent hotfix branch + task from the latest release tag

**Usage:**

@g-hotfix-open [arguments]

**Flags:**

| Flag | Effect |
|---|---|
| `--from-tag <tag>` | Override the base tag (default: latest `git describe`) |
| `--no-pr` | Skip the auto Draft-PR open even when integration is enabled |
| `--description <text>` | Task description / objective |

**Behavior:**

1. **Resolve base tag**: `git describe --tags --abbrev=0` (or `--from-tag <tag>`).
2. **Create branch**: `hotfix/{tag}-{slug}` cut from that tag (not from `main`).
3. **Scaffold task** via `g-skl-tasks` CREATE TASK:
   - `type: hotfix`, `priority: high` (or `critical` if stated).
   - `target_branches: [main]` (add `develop` when a `develop` branch exists — Gitflow).
   - `--description <text>` populates the objective.
4. **Allocate worktree**: `gald3r worktree create` on the hotfix branch (records
   `worktree_branch`, `worktree_owner`, etc. in the task frontmatter).
5. **Optional Draft PR**: if `github_integration: enabled` and not `--no-pr`, invoke
   `g-pr-open --task <id>` (base = `main`).
6. **Cherry-pick guidance**: print the post-merge step — after the hotfix merges to `main`,
   cherry-pick the fix commit(s) onto `develop` (if Gitflow) so the fix isn't lost on the next
   release: `git checkout develop && git cherry-pick <sha>...`.

**Notes:**

- `hotfix/*` branches are exempt from the "require branches up to date" rule in
  `.gald3r/config/branch_protection.md` (T1295) for speed; they still require PR + checks.
- Cherry-pick to `develop` is **guidance only** — the command never force-pushes or
  cherry-picks automatically (Autonomous Push Gate, g-rl-33).
- Helper logic lives in `g-skl-github-pr` (HOTFIX scaffolding).

_Source: [g-hotfix-open.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-hotfix-open.md)_

---

## `@g-idea-capture`

Capture an idea to IDEA_BOARD.md. Activates g-ideas → CAPTURE operation.

**Usage:**

@g-idea-capture

_Source: [g-idea-capture.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-idea-capture.md)_

---

## `@g-idea-farm`

Scan codebase for improvement ideas. Activates g-ideas → FARM operation.

**Usage:**

@g-idea-farm

_Source: [g-idea-farm.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-idea-farm.md)_

---

## `@g-idea-review`

Review IDEA_BOARD. Activates g-ideas → REVIEW operation.

**Usage:**

@g-idea-review

_Source: [g-idea-review.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-idea-review.md)_

---

## `@g-install-agent`

Install the Gald3r Agent CLI from the latest public GitHub Release

**Usage:**

@g-install-agent [arguments]

**What This Command Does:**

Wraps the engine install verb to download the precompiled, signed **Gald3r Agent** binary
from the public `Gald3r-Labs/gald3r_agent` releases, verify it (SHA-256 sidecar), and place
it in the gald3r home `bin/` directory. This does NOT reimplement install logic — it invokes
the `gald3r install agent` engine verb (T1615) when an engine is reachable, and falls back
to a zero-engine bootstrap when none is (installs ship NO engine source — T1645).

**Notes:**

- `--release vX.Y.Z` pins a specific release; default is latest.
- `--from-source` falls back to the legacy `uv sync` source build — dev checkouts only
  (installs do not carry engine source; T1645).
- `--require-verification` fails closed if the `.sha256` checksum is missing or mismatched (BUG-198).
- On network failure / 404 / missing asset the engine degrades gracefully — surface the
  message, do not retry blindly.

_Source: [g-install-agent.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-install-agent.md)_

---

## `@g-install-throne`

Install the Gald3r Throne desktop app from the latest public GitHub Release

**Usage:**

@g-install-throne [arguments]

**What This Command Does:**

Wraps the engine install verb to download the precompiled, signed **Gald3r Throne** installer
from the public `Gald3r-Labs/gald3r_throne` releases, verify it (minisign `.sig`), and launch
the platform installer. This does NOT reimplement install logic — it invokes the
`gald3r install throne` engine verb (T1615). Installs ship NO engine source (T1645), so the
verb needs the compiled agent binary first.

**Notes:**

- `--release vX.Y.Z` pins a specific release; default is latest.
- `--require-verification` fails closed if the minisign `.sig` is missing or invalid (BUG-198).
- Throne ships an OS installer (MSI / EXE / AppImage / deb), not a bare binary — the command
  launches it.
- On network failure / 404 / missing asset the engine degrades gracefully — surface the
  message, do not retry blindly.

_Source: [g-install-throne.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-install-throne.md)_

---

## `@g-issue-sync`

Two-way sync between gald3r tasks and GitHub Issues

**Usage:**

@g-issue-sync [arguments]

**Flags:**

| Flag | Effect |
|---|---|
| `--dry-run` | Show the sync plan without writing either side |
| `--repo <owner/name>` | Override `github_repo` |
| `--label-filter <label>` | Only sync issues carrying this label |
| `--no-create` | Update only; never create new tasks/issues |

**Notes:**

- New WPAC/issue-derived tasks follow normal `g-skl-tasks` CREATE rules; populate
  `issue_ref`, `integration_scope: github`, and `last_synced_at`.
- Edge cases to handle: issue closed externally while task is `[🔄]`; task cancelled
  while issue still open; issue reopened. Surface, don't silently diverge.
- See `g-skl-github-pr` for the issue-link operation contract.

_Source: [g-issue-sync.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-issue-sync.md)_

---

## `@g-juggernaut`

Alias for @g-mission. Unstoppable autonomous loop until a verifiable condition is met

**Usage:**

@g-juggernaut <condition> @g-juggernaut <condition> --budget <N> @g-juggernaut status @g-juggernaut clear @g-juggernaut <condition> --until-empty @g-juggernaut --from-task T{id}

_Source: [g-juggernaut.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-juggernaut.md)_

---

## `@g-kamikaze`

Alias for @g-mission. All-in autonomous loop until a verifiable condition is met

**Usage:**

@g-kamikaze <condition> @g-kamikaze <condition> --budget <N> @g-kamikaze status @g-kamikaze clear @g-kamikaze <condition> --until-empty @g-kamikaze --from-task T{id}

_Source: [g-kamikaze.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-kamikaze.md)_

---

## `@g-keep-it-simple`

Toggle terse mode on or off

**Usage:**

@g-keep-it-simple # turn terse mode ON @g-keep-it-simple off # turn terse mode OFF @g-keep-it-simple status # show current terse-mode state /g-keep-it-simple # alias for @-form

**See Also:**

- Skill: `g-skl-keep-it-simple` (`.claude/skills/g-skl-keep-it-simple/SKILL.md`)
- Related: `@g-pers-pick`, `@g-pers-list`

_Source: [g-keep-it-simple.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-keep-it-simple.md)_

---

## `@g-learn-wrap-up`

Manually flush session learning artifacts before ending a conversation — or any time you want to save without waiting for the automatic stop-event trigger.

**Usage:**

@g-learn-wrap-up @g-learn-wrap-up --no-memory # skip MCP memory capture (offline/fast) @g-learn-wrap-up --chat-only # only save the chat log @g-learn-wrap-up --facts-only # only run learned-facts extraction

**What It Does:**

1. **Chat log** — runs `g-hk-cursor-chat-logger.py` against the current session transcript
2. **Learned facts extraction** — runs `gald3r_nightly_learn.py` (force mode, bypasses the 5-stop counter)
3. **Vocab checkpoint** — confirms `.gald3r/vocab.md` is up to date
4. **Memory capture** — offers `memory_capture_session` summary via example_app MCP (optional, requires Docker)

**Notes:**

- The `g-learn-*` prefix groups all session-memory and knowledge commands together for visual discoverability (CRASH convention)
- This command is safe to run mid-session — it does not end the conversation
- The 5-stop counter in `g-hk-nightly-learn.py` is bypassed; the counter is NOT reset by this command

_Source: [g-learn-wrap-up.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-learn-wrap-up.md)_

---

## `@g-learn`

Capture session learning — write insights to .gald3r/learned-facts.md and optionally to the global vault memory note. No JSONL scanning. Safe for all session modes.

**Usage:**

@g-learn

_Source: [g-learn.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-learn.md)_

---

## `@g-marketing-audit`

Run a full marketing audit of the current project.

**Usage:**

@g-marketing-audit @g-marketing-audit --quick # 5-minute quick scan (positioning + top 3 actions) @g-marketing-audit --deep # Full audit including GEO, SEO, messaging, channels

**What It Does:**

1. Reads PROJECT.md and PLAN.md for product context
2. Evaluates: positioning clarity, channel fit, GEO readiness, content gaps
3. Produces a prioritized audit report in `.gald3r/reports/marketing/`
4. Offers to create tasks for top action items

_Source: [g-marketing-audit.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-marketing-audit.md)_

---

## `@g-marketing-content`

Generate content that compounds over time — blog posts, tutorials, comparisons.

**Usage:**

@g-marketing-content # Generate content ideas based on product @g-marketing-content --type tutorial # Write a tutorial post @g-marketing-content --type comparison # Write a competitor comparison post @g-marketing-content --type casestudy # Write a case study format @g-marketing-content --type faq # Generate FAQ page (good for GEO) @g-marketing-content --calendar # Build a 30-day content calendar @g-marketing-content --repurpose <url> # Repurpose an existing post into social

**What It Does:**

1. Reads PROJECT.md to understand product and target audience
2. Generates SEO-optimized content that targets search intent
3. All posts include: title, meta description, H2 structure, CTAs
4. Writes to `.gald3r/reports/marketing/YYYY-MM-DD_content.md`

_Source: [g-marketing-content.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-marketing-content.md)_

---

## `@g-marketing-geo`

Generative Engine Optimization — get your product discovered inside AI tools

**Usage:**

@g-marketing-geo # Full GEO audit and recommendations @g-marketing-geo --audit # Score current GEO readiness (0-10) @g-marketing-geo --faq # Generate FAQ content for AI discoverability @g-marketing-geo --schema # Generate JSON-LD structured data markup

**What It Does:**

1. Audits your product's discoverability in AI-generated answers
2. Scores GEO readiness across 7 dimensions
3. Generates specific content fixes (FAQ, comparison, definition pages)
4. Produces JSON-LD structured data templates
5. Writes to `.gald3r/reports/marketing/YYYY-MM-DD_geo.md`

_Source: [g-marketing-geo.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-marketing-geo.md)_

---

## `@g-marketing-hn`

Write a proper Hacker News Show HN post — title, framing, story, technical depth.

**Usage:**

@g-marketing-hn # Generate Show HN post (full) @g-marketing-hn --title # Generate 5 title options (most important element) @g-marketing-hn --tellhn # Write a "Tell HN" insight post instead @g-marketing-hn --timing # Get optimal posting time advice

**What It Does:**

1. Reads PROJECT.md for product context and technical details
2. Generates 3-5 title options (title is the make-or-break element)
3. Writes the post body: problem → existing failures → your solution → technical decisions
4. Includes advice on comment engagement strategy for launch day
5. Writes to `.gald3r/reports/marketing/YYYY-MM-DD_hn_draft.md`

_Source: [g-marketing-hn.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-marketing-hn.md)_

---

## `@g-marketing-launch`

Orchestrate a full product launch across channels.

**Usage:**

@g-marketing-launch # Generate full launch plan @g-marketing-launch --channel hn # HN-specific launch post @g-marketing-launch --channel reddit # Reddit launch post @g-marketing-launch --channel ph # Product Hunt submission copy @g-marketing-launch --channel social # Social announcement thread @g-marketing-launch --sequence # Full 2-week launch sequence

**What It Does:**

1. Reads PROJECT.md for product context
2. Generates launch artifacts for each requested channel
3. Creates a 2-week launch timeline with daily actions
4. Writes outputs to `.gald3r/reports/marketing/YYYY-MM-DD_launch.md`
5. Creates tasks for each launch day action item

_Source: [g-marketing-launch.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-marketing-launch.md)_

---

## `@g-marketing-reddit`

Find authentic Reddit conversations to participate in + draft genuine replies.

**Usage:**

@g-marketing-reddit # Find subreddits + keywords to monitor @g-marketing-reddit --keywords # Generate keyword monitoring list @g-marketing-reddit --post # Write a r/SideProject or r/IndieHackers launch post @g-marketing-reddit --reply "<thread text>" # Draft an authentic reply to a specific thread

**What It Does:**

1. Reads PROJECT.md to understand product and target audience
2. Identifies top subreddits where target users gather
3. Generates keyword monitoring list for ongoing tracking
4. Writes launch posts in "builder story" format (not sales copy)
5. Drafts authentic replies that help first, mention product only if directly relevant
6. Writes to `.gald3r/reports/marketing/YYYY-MM-DD_reddit.md`

_Source: [g-marketing-reddit.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-marketing-reddit.md)_

---

## `@g-marketing-social`

Generate X/Twitter (and LinkedIn) content in your brand voice.

**Usage:**

@g-marketing-social # Generate a week of content @g-marketing-social --platform x # X/Twitter only @g-marketing-social --platform linkedin # LinkedIn only @g-marketing-social --thread # Write a full thread @g-marketing-social --batch 10 # Generate 10 standalone posts @g-marketing-social --repurpose <blog-url> # Turn a blog post into 10 social posts @g-marketing-social --milestone "<text>" # Celebrate a milestone in your voice

**What It Does:**

1. Reads PROJECT.md to establish brand voice and product context
2. Generates content in a consistent, authentic-sounding voice (not generic AI)
3. Includes hashtag recommendations
4. Writes to `.gald3r/reports/marketing/YYYY-MM-DD_social.md`

_Source: [g-marketing-social.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-marketing-social.md)_

---

## `@g-marketing-status`

Show current marketing activity status — what's running, what's pending, recent wins.

**Usage:**

@g-marketing-status # Full growth dashboard @g-marketing-status --quick # One-line summary of active channels

**What It Does:**

1. Lists all marketing reports generated (`.gald3r/reports/marketing/`)
2. Shows open marketing tasks from TASKS.md
3. Summarizes active channels and their status
4. Lists recent wins (any tasks marked complete with marketing tag)
5. Recommends next best action

_Source: [g-marketing-status.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-marketing-status.md)_

---

## `@g-mcp-new`

Scaffold a new gald3r MCP plugin from the _template/ directory and stage a

**Usage:**

@g-mcp-new <plugin_name> [--category <cat>] [--credential-source <src>]

**Arguments:**

- `<plugin_name>` — snake_case name. Must be unique across `docker/gald3r/tools/plugins/`.
- `--category <cat>` — one of: `storage | memory | search | integration | ai | database | research | ingest | monitor | video | admin | util`. Default: `util`.
- `--credential-source <src>` — one of: `none | env | per_call | vault_secret | docker_env`. Default: `none`.

**What It Does:**

1. Validates `<plugin_name>` is unique under `docker/gald3r/tools/plugins/`.
2. Copies `docker/gald3r/tools/plugins/_template/plugin_template.py` to
   `docker/gald3r/tools/plugins/<plugin_name>.py`.
3. Replaces placeholder tokens `{plugin_name}` and `{PLUGIN_NAME}` inside
   the new file with the real name and a TITLE_CASE variant.
4. Appends a new entry to `docker/gald3r/plugin_catalog.json` under
   `plugins[]` with:
   - `name`: `<plugin_name>`
   - `description`: `"TODO: one-line description of <plugin_name>"`
   - `category`: from `--category` (default `util`)
   - `tags`: `[]` (fill in manually)
   - `path`: `tools/plugins/<plugin_name>.py`
   - `credential_source`: from `--credential-source` (default `none`)
   - `version`: `"0.1.0"`
   - `is_enabled`: `true`
   - `is_coming_soon`: `false`
5. Prints next steps:
   - Edit the `TOOL_DESCRIPTION` / `TOOL_PARAMS` constants in the plugin file
   - Fill the `execute(...)` body
   - Update the catalog entry's description and tags
   - Call the `config_reload` MCP tool, or restart the gald3r MCP container

**Notes:**

- The `_template/` directory is not loaded as a real plugin by the MCP server.
- After the file is created, run `config_reload` to hot-load it without a Docker
  rebuild. If that fails (e.g. on missing dependencies), restart the container.
- The plugin's `execute(...)` signature must match `TOOL_PARAMS` exactly —
  FastMCP introspects the signature.

**Related:**

- `docker/gald3r/tools/plugins/_template/README.md` — scaffold template docs
- `docker/gald3r/plugin_catalog.json` — marketplace catalog
- `docs/MCP_TOOLS.md` — current MCP tool reference
- `g-skl-platform-claude` — covers Claude MCP integration
- T972 — task that established this command and the catalog

_Source: [g-mcp-new.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-mcp-new.md)_

---

## `@g-medic`

Before medic mode detection, determine whether this project is a WPAC participant. WPAC is configured only when .gald3r/linking/link_topology.md declares at lea

**Usage:**

@g-medic

_Source: [g-medic.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-medic.md)_

---

## `@g-medkit`

This alias delegates to @g-medic automatically.

**Usage:**

@g-medkit

_Source: [g-medkit.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-medkit.md)_

---

## `@g-migrate`

Migrate skill/API interface callers

**Usage:**

@g-migrate <skill-name> --from "<old-interface>" --to "<new-interface>" @g-migrate <skill-name> --from "<old-interface>" --to "<new-interface>" --apply @g-migrate --list-skills

**Arguments:**

| Flag | Description |
|------|-------------|
| `<skill-name>` | Name of the skill/command being migrated (e.g. `g-skl-tasks`) |
| `--from "<old>"` | Old interface string, function name, or invocation pattern to find |
| `--to "<new>"` | New interface string to replace it with |
| `--apply` | Write changes (default: dry-run only) |
| `--list-skills` | List all skill names found in .cursor/skills/ and .claude/skills/ |
| `--scope <path>` | Limit scan to a specific directory (default: entire project) |
| `--report-only` | Generate docs/ migration report without changing files |

**Examples:**

_Source: g-migrate.md_

---

@g-mission

Run an autonomous goal-locked loop until a verifiable completion condition is satisfied

Usage:

@g-mission <condition>
@g-mission <condition> --budget <N>
@g-mission <condition> --until-empty
@g-mission <condition> --until-empty --budget <N>
@g-mission status
@g-mission clear
@g-mission --from-task T{id}

What It Does:

g-mission is gald3r's autonomous completion loop. You state a verifiable end condition; the agent works toward it across as many g-go iterations as needed. After every iteration a lightweight evaluator checks whether the condition holds. If not, the loop continues. If yes, the mission is complete.

This is distinct from @g-goal (which sets a goal that g-go reads but does not loop autonomously) and from @g-go-go (which runs until tasks are exhausted). g-mission runs until YOUR stated condition is provably true — the stopping criterion is yours, not the task queue.

Related:

• Spec: see .gald3r/tasks/ for T{id} once created
• Config: .gald3r/config/ACTIVE_MISSION.md
• Depends on: @g-goal, @g-go-go, @g-go

_Source: g-mission.md_

---

@g-pers-list

List all available personality packs from .gald3r_sys/personality_packs/ and show

Usage:

@g-pers-list

Notes:

• gald3r_personality is the default installed by g-setup but is fully replaceable
• Only one personality pack is active at a time — they are swapped, not stacked
• fandom-skills is a skills-only pack (no rule file) and can be installed alongside any personality
• If .gald3r_sys/personality_packs/ is missing, inform user and exit gracefully

_Source: g-pers-list.md_

---

@g-pers-pick

Switch the active personality pack. Removes the currently active pack (if any),

Usage:

@g-pers-pick

Notes:

• All personality packs are fully swappable — including gald3r_personality
• fandom-skills is skills-only; it does not conflict with a personality pack. Use g-skill-pack-add for it
• .codex, .opencode and other rule-free platforms only get skill files if the pack includes them
• Restart your IDE session after switching for the new personality to load into context

_Source: g-pers-pick.md_

---

@g-plan

Start project planning

Usage:

@g-plan [arguments]

What This Command Does:

Guides you through creating a comprehensive project plan using the gald3r planning system.

_Source: g-plan.md_

---

@g-platform-check

Check platform capability gaps vs. the Cursor reference

Usage:

@g-platform-check                # all 23 platforms
@g-platform-check windsurf       # one platform

What This Command Does:

Reports the current capability state of one platform (or all 23 if no argument) by comparing its declared support against the Cursor reference implementation. Delegates to g-skl-platform-monitor operation CHECK and the check_platform_status.py script.

_Source: g-platform-check.md_

---

@g-platform-scan-docs

Scan a platform's official docs for breaking changes

Usage:

@g-platform-scan-docs antigravity     # high-priority: relaunched with breaking changes
@g-platform-scan-docs cursor

What This Command Does:

Crawls the official documentation of the named platform and diffs against the last crawl, surfacing sections that changed since the previous scan so they can be reviewed for gald3r compatibility impact. Delegates to g-skl-platform-monitor operation SCAN_DOCS, then drives the T514/T515 freshness consumers end-to-end: crawl-export (T646) → spec_refresh.py proposal → human-accept → generate_status.py --apply regen.

_Source: g-platform-scan-docs.md_

---

@g-platform-status

Show the cross-platform capability status index

Usage:

@g-platform-status

What This Command Does:

Displays a concise read-only summary of .gald3r/PLATFORM_STATUS.md — the honest capability index across all 23 platforms — and the rollup counts (N healthy, M need attention, K rework, U unknown). Report-only; does not modify any file.

_Source: g-platform-status.md_

---

@g-plugin-update

Re-apply / move an installed plugin to a newer (or forced) version from a local source

Usage:

@g-plugin-update

What It Does:

1. Look up the plugin's installed entry in installed.yaml; fail if not installed.
2. Resolve the source (--source, else the already-vendored .gald3r_sys/plugins/<id>/)

and read its gald3r-plugin.yaml manifest.

1. Check compatibility (gald3r_min_version host floor); fail if incompatible.
2. Compare source version against the installed version. Same version + no --force

-> up_to_date, nothing applied.

1. --dry-run: return the planned from_version -> to_version and component inventory;

apply nothing.

1. Otherwise, apply via the same path as plugin install: remove this plugin's stale

components, copy the new components into the canonical .gald3r_sys/<type>/ dirs (provenance-stamped, gald3r-core components never overwritten), and rewrite the installed.yaml entry.

Notes:

• Scope narrowing from the historical .ps1 (T1601): this is a **single-plugin,

local-source** operation. The old update_plugin.ps1's bulk "check every installed plugin against a remote HTTPS registry" loop, CHANGELOG excerpt printer, interactive confirmation prompts, upgrade.ps1 lifecycle execution, and versioned on-disk backup directory were designed-but-not-carried-forward when the engine module absorbed this op (matching INSTALL/REMOVE/LIST/NEW/CHECK_COMPAT, which were similarly "designed but never ported" per the engine module's own docstring). Remote https:// registry sources are intentionally not fetched by this engine surface.

• To enumerate installed plugins first: gald3r plugin list.
• To check a candidate source's compatibility before updating: gald3r plugin check-compat <path>.
• Lifecycle scripts (upgrade.ps1 / install.ps1 / uninstall.ps1) are data-declared

on a plugin but are never auto-run by this engine surface (ADR-015 D7).

• Sibling ops on the same gald3r plugin CLI surface: install, remove (alias

uninstall), list, new, check-compat.

_Source: g-plugin-update.md_

---

@g-pr-close

Finalize a GitHub PR after review (merge on PASS / keep Draft on FAIL)

Usage:

@g-pr-close [arguments]

Flags:

Flag	Effect
--task <id>	Explicit task ID
--no-merge	Comment + flip to Ready but skip the merge (manual merge desired)
`--strategy <squash\	rebase\	merge>`	Override the configured merge strategy
--dry-run	Print the plan without commenting/merging

Behavior:

1. Resolve task ID (--task <id> or active worktree / branch).
2. Read the review verdict from the most recent ## Status History row of the task file:
3. [✅] / verification-in-progress → completed ⇒ PASS
4. FAIL: / back-to-pending ⇒ FAIL
5. Detect fork PRs first (T1309): gh pr view <n> --json headRepositoryOwner,isCrossRepository.

If isCrossRepository: true, set is_fork=1 and skip any head-branch write (head-ref label edits, pushes to the fork) — we lack write on a contributor's fork. Base-repo operations (comment, PR labels, merge) still proceed normally.

1. On PASS:
2. g-skl-github-pr READY (Draft → Ready). (fork: skip if Ready requires head-branch write; comment instead.)
3. g-skl-github-pr COMMENT — post the review summary (verdict + reviewer agent identity + review-result commit SHA).
4. g-skl-github-pr CLOSE — merge using merge_strategy (default squash); --delete-branch when configured.
5. Merge queue (T1312): when merge_queue: enabled, merge with gh pr merge --auto <strategy-flag>

(queue the PR; GitHub merges when checks pass and the queue front is reached) instead of an immediate merge. If gh reports auto-merge/queue is unavailable on the repo plan, surface the error — do not silently fall back to an immediate merge.

• Write pr_status: merged (or pr_status: ready while queued); auto-close the linked issue_ref when auto_close_issue_on_merge: true.
• On FAIL:
• g-skl-github-pr COMMENT — post the FAIL summary explaining the unmet criteria.
• Leave the PR open as Draft (do not merge); keep pr_status: draft.
• Fork PRs (T1309) summary: merge is allowed (base-repo permission); head-branch writes are

skipped; comments/labels on the PR work. See github_config.md § "Forking workflow" and branch_protection.md § "For external contributors".

Notes:

• Auto-invoked by the g-go-review PR-close hook (T1292) after PASS/FAIL status writes,

when github_integration: enabled and github_pr_hooks: enabled.

• Honors the Autonomous Push Gate (g-rl-33): a merge is outward-facing — confirm per

pipeline policy; never merge silently.

• See g-skl-github-pr for the full operation contract.

_Source: g-pr-close.md_

---

@g-pr-open

Open a Draft GitHub PR for the active task

Usage:

@g-pr-open [arguments]

Flags:

Flag	Effect
--task <id>	Explicit task ID instead of worktree-detected
--ready	Open as Ready for review instead of Draft
--target <branch>	Override base branch (overrides stacked-PR routing, T1303)
--dry-run	Print the plan (title, body, labels, base, stack chain) without pushing or creating

Behavior:

1. Resolve the task ID:
2. --task <id> flag if given, else
3. read the active worktree's .gald3r-worktree.json (task_id), else
4. infer from the current branch name (gald3r/{task_id}/...).
5. Push the current branch to origin if not already pushed (git push -u origin <branch>).
6. Call g-skl-github-pr OPEN:
7. PR title from github_config.md pr_title_format (default {type}(T{id}): {title}).
8. PR body from ## Objective, ## Acceptance Criteria, ## Handoff Report of the task file.
9. Labels: one from task.type (feature→enhancement, bug_fix→bug, …) plus gald3r/auto.
10. Open as Draft unless --ready.
11. Write back pr_url: and pr_status: draft (or ready) + integration_scope: github

to the task frontmatter.

Notes:

• Auto-invoked by the g-go PR-open hook (T1291) on [🔄]→[🔍] when

github_integration: enabled and github_pr_hooks: enabled.

• Honors the Autonomous Push Gate (g-rl-33): the push/PR-create is outward-facing —

surface and confirm per pipeline policy; never push silently.

• See g-skl-github-pr for the full operation contract.

_Source: g-pr-open.md_

---

@g-prd-add

Create a new PRD. Activates g-skl-prds → CREATE operation.

Usage:

@g-prd-add "PRD Title"
@g-prd-add "PRD Title" --tier full
@g-prd-add "PRD Title" --frameworks "SOC2-CC6.1,HIPAA-164.312(a)"
@g-prd-add "PRD Title" --classification confidential --risk medium

_Source: g-prd-add.md_

---

@g-prd-del

Archive a PRD (soft-delete). Activates g-skl-prds → ARCHIVE operation.

Usage:

@g-prd-del prd-NNN
@g-prd-del prd-NNN --reason "Replaced by alternative compliance approach"

_Source: g-prd-del.md_

---

@g-prd-revise

Revise a released PRD. Activates g-skl-prds → REVISE operation.

Usage:

@g-prd-revise prd-NNN
@g-prd-revise prd-NNN --reason "Updated risk assessment for new threat model"

_Source: g-prd-revise.md_

---

@g-prd-upd

Update a PRD field. Activates g-skl-prds → UPDATE operation.

Usage:

@g-prd-upd prd-NNN status review
@g-prd-upd prd-NNN status approved
@g-prd-upd prd-NNN status in-implementation
@g-prd-upd prd-NNN status released
@g-prd-upd prd-NNN authorizer-name "Jane Doe"
@g-prd-upd prd-NNN authorizer-date 2026-04-25
@g-prd-upd prd-NNN authorizer-ticket "JIRA-1234"
@g-prd-upd prd-NNN add-framework "PCI-DSS-3.4"
@g-prd-upd prd-NNN risk-level high

_Source: g-prd-upd.md_

---

@g-propose

One-shot proposal generation: produces a complete proposal package from a short description.

Usage:

@g-propose "Add dark mode toggle to settings panel"
@g-propose "Replace synchronous file writes with async queue" --scope backend
@g-propose "Integrate Stripe payments" --scope payments,auth --constraints "no new deps"

What This Command Does:

Accepts a feature description and generates a self-contained proposal document at docs/proposals/YYYYMMDD_HHMMSS_Cursor_PROPOSAL_<slug>.md covering everything needed for human approval before any .gald3r/ writes occur.

One command, one file, full context.

---

_Source: g-propose.md_

---

@g-pt

Manage workflow profiles (project types)

Usage:

@g-pt [arguments]

Subcommands:

Subcommand	What it does
list	List every built-in + custom profile; marks the active one with * and (active).
use <profile>	Set workflow_profile: <profile> in .gald3r/PROJECT.md (creates/updates the frontmatter field). Validates the profile exists first.
copy <src> <new-name>	Copy <src>.yaml to <new-name>.yaml, rewriting the id:/name: inside. Refuses if the target already exists or the source is missing.
edit <profile>	Print the resolved absolute path to <profile>.yaml so an editor/agent can open it (the no-GUI-safe form of "edit").
validate <profile>	Structurally check a profile: parses as YAML, required fields present (id, name, task_statuses), no duplicate/unknown status ids, and transitions (if any) reference defined status ids. Exits non-zero on any problem.

Behavior:

Runs the helper .claude/skills/g-skl-project-types/scripts/g_pt.py:

uv run python .claude/skills/g-skl-project-types/scripts/g_pt.py list
uv run python .claude/skills/g-skl-project-types/scripts/g_pt.py use content_creation
uv run python .claude/skills/g-skl-project-types/scripts/g_pt.py copy software_dev my_workflow
uv run python .claude/skills/g-skl-project-types/scripts/g_pt.py edit my_workflow
uv run python .claude/skills/g-skl-project-types/scripts/g_pt.py validate my_workflow

Notes:

• Profiles are individual <id>.yaml files read by name — there is no

single custom.yaml. copy therefore creates <new-name>.yaml (a new custom profile), and use <new-name> activates it.

• --project-root <path> pins the .gald3r/ root (defaults to walking up from

the script). Useful for tests and out-of-tree invocation.

• Idempotent: re-running use updates the field in place (never duplicates it);

copy never overwrites an existing profile.

• Built-in profiles ship under .gald3r/config/workflow_profiles/:

software_dev, content_creation, research.

_Source: g-pt.md_

---

@g-qa

Activate quality assurance system

Usage:

@g-qa [arguments]

What This Command Does:

Activates the quality assurance system for bug tracking, quality management, and fix documentation.

_Source: g-qa.md_

---

@g-queue

Queue follow-up work into a running g-go-code worktree session, to run after the main goal completes

Usage:

@g-queue [arguments]

What It Does:

@g-queue appends a follow-up prompt to queue.md at the worktree root of an in-flight g-go-code task. Unlike @g-steer (which interrupts the current trajectory immediately), queued items are not processed mid-task — they are drained only after the main goal's acceptance criteria are all met and the task reaches [🔍] (g-go-code step 7d).

queue.md is an append-only checklist (- [ ] per item). Each call adds one item; ordering is preserved. This lets you stack up "while you're in there, also do X" work without disrupting the current goal or losing the worktree's context.

Related:

• Command: g-steer — one-shot mid-flight steering (interrupts the current trajectory)
• Command: g-go-code — the session that drains queue.md (see step 7d + "Mid-Flight Course Correction")
• Helper: gald3r worktree (-Action Queue)
• Spec: T969 — Worktree /steer + /queue
• File: <worktree>/queue.md (append-only checklist)

Let's queue.

_Source: g-queue.md_

---

@g-recon-docs

Capture a documentation URL into the vault with periodic revisit tracking.

Usage:

@g-recon-docs --url https://docs.example.com --name "ExampleDocs"
@g-recon-docs REFRESH_STALE
@g-recon-docs --url https://docs.example.com --deep   # capture + deep analysis report

Notes:

• Default refresh_days: 30 — override with --refresh-days N
• Session start shows stale count: 📚 Vault Docs: 12 registered | 3 stale
• Requires g-skl-crawl (crawl4ai) — run @g-crawl SETUP first
• Use --dry-run to list stale URLs without fetching

_Source: g-recon-docs.md_

---

@g-recon-file

Capture a local file (PDF, DOCX, XLSX, TXT, MD, CSV, RTF) into the vault knowledge store.

Usage:

@g-recon-file /path/to/document.pdf
@g-recon-file /path/to/spreadsheet.xlsx --title "Q1 Data" --topics "finance,metrics"
@g-recon-file /path/to/notes.md --deep   # capture + analysis report

What It Does:

1. Detects file type and extracts text content
2. Generates title, summary, and tags from content (or uses provided --title / --topics)
3. Writes vault note to research/files/{date}_{slug}.md
4. Registers in research/files/_index.yaml
5. Updates vault/log.md

Notes:

• Images and scanned PDFs (no text layer) produce a metadata-only stub with a warning
• Phase 3 (T112) adds LLM-based image/OCR extraction for scanned PDFs
• File is NOT copied to the vault — only a Markdown summary note is created

_Source: g-recon-file.md_

---

@g-recon-repo

Capture a GitHub repository into the vault as a structured summary note.

Usage:

@g-recon-repo https://github.com/owner/repo
@g-recon-repo https://github.com/owner/repo --deep   # capture + deep feature analysis

What It Does:

1. Reads key repo files (README, package.json/pyproject.toml/Cargo.toml, key source files)
2. Extracts: purpose, tech stack, architecture, notable patterns, license
3. Writes vault note to research/repos/{owner}__{repo}.md
4. Updates vault/research/repos/_index.yaml
5. Updates vault/log.md

Notes:

• Uses existing repos_location mirrors when available; falls back to GitHub web scraping
• Produces a lightweight summary note — for full feature harvesting, use @g-recon-repo --deep
• Output in research/repos/ follows Obsidian vault standard (frontmatter, tags, wikilinks)

See Also:

• @g-res-deep — Full deep analysis of a captured repo (5-pass strategy)
• @g-res-review — Review existing recon reports for adoption decisions
• @g-res-apply — Apply approved features from a recon report to .gald3r/

_Source: g-recon-repo.md_

---

@g-recon-url

One-time URL capture into vault research/articles/.

Usage:

@g-recon-url https://example.com/article
@g-recon-url https://example.com/article --title "Custom Title" --topics "ai,benchmarks"
@g-recon-url --urls-file my_urls.txt
@g-recon-url https://example.com/article --deep   # capture + deep analysis report

What It Does:

1. Checks if URL is already captured (dedup via _index.yaml) — skips duplicates unless --force
2. Crawls URL via g-skl-crawl (crawl4ai) → clean Markdown
3. Writes vault note to research/articles/{date}_{slug}.md
4. Registers URL in research/articles/_index.yaml
5. Updates vault/log.md

Notes:

• No revisit schedule — these are one-shot snapshots
• Use @g-recon-docs for documentation that should be refreshed periodically
• Use --force to re-capture an already-indexed URL
• Requires g-skl-crawl (crawl4ai) — run @g-crawl SETUP first

_Source: g-recon-url.md_

---

@g-recon-yt

Capture a YouTube video transcript into the vault knowledge store.

Usage:

@g-recon-yt https://www.youtube.com/watch?v=VIDEO_ID
@g-recon-yt https://www.youtube.com/watch?v=VIDEO_ID --deep   # capture + deep analysis

What It Does:

1. Fetches video metadata (title, channel, duration, upload date) via yt-dlp
2. Downloads transcript/captions (manual → auto-generated → translated, in priority order)
3. Parses VTT captions to clean text (no timestamps, deduplicated rolling lines)
4. Generates summary and key points from transcript
5. Writes vault note to research/videos/ with analysis_depth: transcript_only
6. Updates vault/log.md and vault/_index.yaml

Notes:

• No video download — transcript only
• No Docker, no MCP required (uses yt-dlp locally)
• Notes include analysis_depth: transcript_only — a future task can upgrade to full vision analysis
• If no captions are available, creates a metadata-only note with a warning

_Source: g-recon-yt.md_

---

@g-release-accelerate

Accelerate a release. Activates g-skl-release → ACCELERATE operation.

Usage:

@g-release-accelerate 002 --days 7        # pull release 002 in by 7 days
@g-release-accelerate 002 --date 2026-05-01   # retarget to an explicit date

_Source: g-release-accelerate.md_

---

@g-release-assign

Assign tasks to a release. Activates g-skl-release → ASSIGN operation.

Usage:

@g-release-assign 002 42
@g-release-assign 002 42,55,61
@g-release-assign "Spring Drop" 42,55

_Source: g-release-assign.md_

---

@g-release-new

Create a new release. Activates g-skl-release → CREATE operation.

Usage:

@g-release-new "Release Name"
@g-release-new "Release Name" --version 1.2.0
@g-release-new "Release Name" --target 2026-05-15
@g-release-new "Release Name" --cadence 21

_Source: g-release-new.md_

---

@g-release-propose

Analyze completed tasks and propose the next semantic version bump + draft release notes. Creates releases/pending/RELEASE_PROPOSAL_vX.Y.Z.md for human review.

Usage:

@g-release-propose
@g-release-propose --from v1.6.0      # explicitly set the base version
@g-release-propose --bump minor       # override the auto-detected bump level

See Also:

• @g-release-cut — accept a proposal and cut the release tag
• @g-release-publish — graduate accumulated releases to _test or public tier
• g-skl-release PROPOSE operation for full bump logic documentation

_Source: g-release-propose.md_

---

@g-release-publish

Publish ROADMAP.md. Activates g-skl-release → PUBLISH operation.

Usage:

@g-release-publish

_Source: g-release-publish.md_

---

@g-release-status

Show release status. Activates g-skl-release → STATUS operation.

Usage:

@g-release-status                  # summary of all active releases
@g-release-status 002              # detail for release 002
@g-release-status "Spring Drop"    # detail by name

_Source: g-release-status.md_

---

@g-report

Project backlog and status report

Usage:

@g-report [arguments]

What This Command Does:

Generates a detailed operational report covering commit history, task availability, and all blockers across the project. Designed for quick situational awareness — everything you need to decide what to work on next.

_Source: g-report.md_

---

@g-res-apply

Convert an approved recon report into gald3r artifacts (goals, features, subsystems, tasks).

Usage:

@g-res-apply REVIEW {slug}
@g-res-apply DRY-RUN {slug} [--mode=approved|all|category:{cat}]
@g-res-apply APPLY {slug} [--mode=approved|all|category:{cat}]  # all requires clean-room approval for every selected feature
@g-res-apply APPLY {slug} --target {child_project}   # route to a child project (T118)

Examples:

**See Also:**

- `@g-res-deep` — Analyzes a repo and produces the recon report
- `@g-res-review` — Review and approve features interactively
- `@g-task-add` — Create individual tasks manually

_Source: [g-res-apply.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-res-apply.md)_

---

## `@g-res-deep`

Deep analysis of a captured repo, URL, or vault note — produces a structured recon report. Agents are reporters; humans are editors.

**Usage:**

@g-res-deep ANALYZE https://github.com/user/repo @g-res-deep ANALYZE vault:research/repos/ownerrepo.md @g-res-deep RESUME userrepo @g-res-deep APPLY userrepo @g-res-deep APPLY --dry-run userrepo @g-res-deep STATUS user__repo

**See Also:**

- `@g-recon-repo` — Lightweight capture first (then `--deep` or this command)
- `@g-res-review` — Review existing recon reports
- `@g-res-apply` — Apply approved features to .gald3r/

_Source: [g-res-deep.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-res-deep.md)_

---

## `@g-res-review`

Review existing recon reports in vault/research/recon/ and triage features for adoption.

**Usage:**

@g-res-review # list all available recon reports @g-res-review {slug} # review a specific report @g-res-review --all-unadopted # surface all unadopted suggestions across reports

**What It Does:**

1. Scans `vault/research/recon/` for `04_FEATURES.md` files
2. Presents unadopted features for user triage:
   - `[✅]` approve → mark for `@g-res-apply`
   - `[❌]` reject → flag as dismissed
   - `[⏸]` defer → skip in APPLY, surface again next review cycle
3. Shows feature counts, source repos, and time-since-last-review per report
4. If `--topology-aware` (requires T118): cross-references capabilities.md to suggest `--target` routing

**See Also:**

- `@g-res-deep` — Run the deep analysis pass to generate a recon report
- `@g-res-apply` — Apply approved features to `.gald3r/`

_Source: [g-res-review.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-res-review.md)_

---

## `@g-review`

Deprecated — use @g-code-review instead.

**Usage:**

@g-review

_Source: [g-review.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-review.md)_

---

## `@g-rule-new`

Creates a new rule for your own project. You choose where it lives - your AI platform folder

**Usage:**

@g-rule-new <slug> @g-rule-new "no-console-logs"

_Source: [g-rule-new.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-rule-new.md)_

---

## `@g-setup`

Initialize the gald3r system

**Usage:**

1. Locate your downloaded gald3r_template folder
2. Run: .\setup_gald3r_project.ps1

(interactive installer — asks for target path and platform selection)

1. START A NEW SESSION after installation completes so skills/rules load
2. Then re-run @g-setup (or /g-setup) in the new session

**What This Command Does:**

Initializes or reinitializes the gald3r v3 task management system in the current project.
Activates the **g-skl-setup** skill which handles the full initialization workflow.

> **This is the slim gald3r version.** Experiments, linking, vault, config, and phases
> are full-version features only and must not be created here.

---

_Source: [g-setup.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-setup.md)_

---

## `@g-ship`

Ship the current [Unreleased] content as a versioned release.

**Usage:**

@g-ship major — Breaking changes, reframe, new architecture @g-ship minor — New features, additive @g-ship patch — Bug fixes, small extensions @g-ship status — Show current version and [Unreleased] content

**What It Does:**

1. Shows the current `[Unreleased]` CHANGELOG section
2. Calculates the new version number (MAJOR.MINOR.PATCH)
3. Asks for a short theme/title for the release (optional)
3a. **Release sweep (T419)** — before tagging, scans `tasks/awaiting-verification/` and reports which tasks ship (`release_hold: none`) vs. which are skipped (`manual`, `sync_required` with their sync partner). Held tasks are not included in the release; clear the hold with `@g-task clear-release-hold <id>` to ship.
4. Promotes `[Unreleased]` → `[X.Y.Z] - YYYY-MM-DD`
5. Writes a new empty `[Unreleased]` at the top
6. Bumps the `VERSION` file
7. Updates the README version badge if present
8. Creates a focused commit: `release: vX.Y.Z`
9. Creates an annotated git tag: `vX.Y.Z`
10. Asks: Push to remote?
11. Asks: Create GitHub release?

**Related:**

- `@g-git-push` — prompts for ship if `[Unreleased]` is non-empty
- `g-skl-tasks` COMPLETE — adds entries to `[Unreleased]` automatically
- `g-skl-bugs` FIX — adds `### Fixed` entries to `[Unreleased]` automatically

_Source: [g-ship.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-ship.md)_

---

## `@g-skill-new`

Creates a new skill for your own project. You choose where it lives - your AI platform folder

**Usage:**

@g-skill-new <name> @g-skill-new "my-feature"

_Source: [g-skill-new.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-skill-new.md)_

---

## `@g-skill-pack-add`

Install all skills from a pack, or a single named skill from a pack.

**Usage:**

@g-skill-pack-add

**Notes:**

- Adding a skill from a pack that is not yet listed creates a partial install entry
- Version is read from pack's `PACK.md` `version:` frontmatter
- `_evolved` variants are preserved — `add` will not overwrite a skill folder with `_evolved` suffix

_Source: [g-skill-pack-add.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-skill-pack-add.md)_

---

## `@g-skill-pack-del`

Remove all skills from a pack, or a single named skill, from all active IDE folders.

**Usage:**

@g-skill-pack-del

**Notes:**

- `_evolved` skills (user-customized) are protected from accidental deletion
- Use `--force` only when you explicitly want to remove a customized skill
- gald3r core skills (in `.claude/skills/`) are never touched by this command

_Source: [g-skill-pack-del.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-skill-pack-del.md)_

---

## `@g-skill-pack-list`

Show all available skill packs from .gald3r_sys/skill_packs/ along with which packs

**Usage:**

@g-skill-pack-list

_Source: [g-skill-pack-list.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-skill-pack-list.md)_

---

## `@g-skill-pack-save`

When you have customized a skill and want to preserve that customization in the pack

**Usage:**

@g-skill-pack-save

**Notes:**

- The `_evolved` suffix signals to installers and `g-skill-pack-del` that this is user-customized
- The original non-evolved version is preserved alongside the evolved one in the registry
- `g-skill-pack-add --update` will show a diff before overwriting an evolved skill
- Evolved skills are not overwritten by gald3r updates (version bump does not touch `_evolved` folders)

_Source: [g-skill-pack-save.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-skill-pack-save.md)_

---

## `@g-skill-review`

List and review auto-proposed skill drafts, then promote or discard

**Usage:**

@g-skill-review [arguments]

_Source: [g-skill-review.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-skill-review.md)_

---

## `@g-status`

Generate project status overview

**Usage:**

⚠️ Orphaned waiter: T1239 — dep T1238 was cancelled 2d ago. Use @g-task-upd --demote with a new plan or @g-task-upd --promote if requirements changed.

**What This Command Does:**

Provides a comprehensive status update for your gald3r project.

_Source: [g-status.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-status.md)_

---

## `@g-steer`

Steer a running g-go-code worktree session mid-flight without restarting it

**Usage:**

@g-steer [arguments]

**What It Does:**

`@g-steer` writes `steer.md` to the **worktree root** of an in-flight `g-go-code` task. The running
implementation session polls for this file at **every AC-gate iteration** (step b2.5). When found,
it injects the prompt as a high-priority steering instruction, logs `STEERED by user at turn N` to
the task's `## Status History`, then **deletes** `steer.md` so the steer fires exactly once.

This lets you redirect work in flight — narrow the focus, skip a sub-task, change an approach — without
killing the session and losing its context. It is the complement to `@g-queue` (which adds work to do
*after* the goal completes) and to `g-go-code --resume` (which restarts a crashed session).

Steering is **one-shot and latest-wins**: a second `@g-steer` before the first is consumed overwrites
the pending steer. Each new redirection requires a new `@g-steer` call.

**Related:**

- Command: `g-queue` — append follow-up work processed after the main goal completes
- Command: `g-go-code` — the session that polls for `steer.md` (see "Mid-Flight Course Correction")
- Helper: `gald3r worktree` (`-Action Steer`)
- Spec: T969 — Worktree /steer + /queue
- File: `<worktree>/steer.md` (one-shot, deleted after injection)

Let's steer.

_Source: [g-steer.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-steer.md)_

---

## `@g-subsystem-add`

Add a new subsystem to the registry. Activates g-skl-subsystems → CREATE SUBSYSTEM SPEC operation.

**Usage:**

@g-subsystem-add "subsystem-name" @g-subsystem-add "voice-speech-system" --status planned --tier adv

_Source: [g-subsystem-add.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-subsystem-add.md)_

---

## `@g-subsystem-audit`

Audit subsystem and skill tagging compliance against the L1 group hierarchy defined in

**Usage:**

@g-subsystem-audit

**Related:**

- `@g-system-rebuild` — regenerate PRODUCT_SYSTEMS.md from tags
- `add_subsystem_tags.ps1` — bulk-tag SKILL.md files
- `aggregate_subsystems.ps1` — generates PRODUCT_SYSTEMS.md
- `g-skl-subsystems` AUDIT operation — the underlying implementation
- C-026 — constraint requiring `parent_system:` on all new subsystem specs

_Source: [g-subsystem-audit.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-subsystem-audit.md)_

---

## `@g-subsystem-del`

Deprecate a subsystem. Activates g-skl-subsystems → DEPRECATE SUBSYSTEM operation.

**Usage:**

@g-subsystem-del subsystem-name @g-subsystem-del subsystem-name --reason "Merged into feature-staging-pipeline"

_Source: [g-subsystem-del.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-subsystem-del.md)_

---

## `@g-subsystem-graph`

Activate g-skl-subsystem-graph to generate or refresh .gald3r/SUBSYSTEM_GRAPH.md.

**Usage:**

@g-subsystem-graph

_Source: [g-subsystem-graph.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-subsystem-graph.md)_

---

## `@g-subsystem-upd`

Update an existing subsystem spec. Activates g-skl-subsystems → UPDATE SUBSYSTEM operation.

**Usage:**

@g-subsystem-upd subsystem-name @g-subsystem-upd subsystem-name --field status --value active @g-subsystem-upd subsystem-name --add-location "skill: g-skl-features" @g-subsystem-upd subsystem-name --log "T084-2: g-skl-features skill added"

_Source: [g-subsystem-upd.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-subsystem-upd.md)_

---

## `@g-subsystems`

List and check the subsystem registry. Activates g-skl-subsystems.

**Usage:**

@g-subsystems # sync check (default) @g-subsystems --status active # show only active subsystems @g-subsystems --status all # show all (active/planned/deprecated)

**What It Does:**

| Invocation | Operation |
|------------|-----------|
| `(no args)` | **SYNC CHECK** — audit all task files' `subsystems:` fields against SUBSYSTEMS.md; report missing entries; create stub specs for any without spec files |
| `--status active` | List active subsystems grouped by status |
| `--status all` | List all subsystems (active + planned + deprecated) with min_tier column |

_Source: [g-subsystems.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-subsystems.md)_

---

## `@g-swot-review`

Run SWOT analysis on current project phase

**Usage:**

@g-swot-review [arguments]

**Behavior:**

1. Read the `g-swot-review` skill at `.cursor/skills/g-swot-review/SKILL.md`
2. Execute all 5 analysis passes as described in the skill
3. Write report to `.gald3r/logs/swot/YYYY-MM-DD_swot_review.md`
4. Display summary to user

_Source: [g-swot-review.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-swot-review.md)_

---

## `@g-system-rebuild`

Regenerate .gald3r/PRODUCT_SYSTEMS.md by scanning all repos in the workspace for distributed

**Usage:**

@g-system-rebuild

**Related:**

- `@g-subsystem-audit` — detailed audit of tagging compliance (T1458)
- `aggregate_subsystems.ps1` — the underlying script (T1459)
- `add_subsystem_tags.ps1` — bulk tagger for initial pass (T1457)
- `PRODUCT_SYSTEMS.md` — the output (read by `@g-subsystem-audit` and `g-skl-subsystems` CREATE)

_Source: [g-system-rebuild.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-system-rebuild.md)_

---

## `@g-task-add`

Create a new task. Activates g-skl-tasks → CREATE TASK operation.

**Usage:**

@g-task-add "Task title and brief description"

_Source: [g-task-add.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-task-add.md)_

---

## `@g-task-archive`

Archive terminal task history into .gald3r/archive/ while keeping TASKS.md as an active working index.

**Usage:**

@g-task-archive --dry-run @g-task-archive --apply @g-task-archive --dry-run --include-recent

**What This Command Does:**

Delegates to **g-skl-tasks** -> ARCHIVE TASKS.

The command moves completed/failed/cancelled task history out of the active index and into count-based archive buckets:

- Index files: `.gald3r/archive/archive_tasks_0000_0999.md`, `.gald3r/archive/archive_tasks_1000_1999.md`, ...
- Task files: `.gald3r/archive/tasks/tasks_0000_0999/`, `.gald3r/archive/tasks/tasks_1000_1999/`, ...

Buckets hold at most 1000 archive entries/files and are assigned by archive entry ordinal, not by original task ID.

_Source: [g-task-archive.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-task-archive.md)_

---

## `@g-task-del`

Archive (soft-delete) a task. Activates g-skl-tasks → ARCHIVE TASK operation.

**Usage:**

@g-task-del TASK-NNN @g-task-del TASK-NNN --reason "Superseded by feat-NNN"

_Source: [g-task-del.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-task-del.md)_

---

## `@g-task-new`

Create a new task. Activates g-skl-tasks → CREATE TASK operation.

**Usage:**

@g-task-new

_Source: [g-task-new.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-task-new.md)_

---

## `@g-task-sync-check`

Validate TASKS.md matches tasks/ files. Activates g-tasks → SYNC CHECK operation.

**Usage:**

@g-task-sync-check

_Source: [g-task-sync-check.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-task-sync-check.md)_

---

## `@g-task-upd`

Update task status or fields. Activates g-skl-tasks → UPDATE STATUS operation.

**Usage:**

@g-task-upd TASK-NNN status in-progress @g-task-upd TASK-NNN priority high @g-task-upd TASK-NNN add-dependency TASK-MMM @g-task-upd --promote TASK-NNN # waiting → pending (all spec prereqs confirmed met) @g-task-upd --demote TASK-NNN --reason "Decision reversed — re-spec needed"

@g-task set-release-hold TASK-NNN manual "Holding for coordinated deploy" @g-task set-release-hold TASK-NNN sync_required "API contract change" --sync-project gald3r_agent --sync-task T890 @g-task set-release-hold TASK-NNN none "Ready to ship" # equivalent to clear @g-task clear-release-hold TASK-NNN

_Source: [g-task-upd.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-task-upd.md)_

---

## `@g-task-update`

Update task status. Activates g-skl-tasks → UPDATE STATUS operation.

**Usage:**

@g-task-update

_Source: [g-task-update.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-task-update.md)_

---

## `@g-test`

Manage test plans (fast / comprehensive / regression) for gald3r systems and features.

**Usage:**

@g-test create auth @g-test audit @g-test run auth L1 @g-test verify-gate api @g-test release-gate @g-test status

_Source: [g-test.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-test.md)_

---

## `@g-theme-edit`

Open the gald3r theme editor

**Usage:**

@g-theme-edit # list themes + open editor (throne app) or fallback menu @g-theme-edit create <name> # scaffold docs/themes/<name>.css (@import dark + :root) @g-theme-edit edit <name> --bg #101018 @g-theme-edit import <path> # import a :root block / theme file @g-theme-edit export <name> # print the theme's editable :root delta @g-theme-edit preview <name> # render the reference report with this theme @g-theme-edit activate <name> # set html_theme + rewrite _active.css

_Source: [g-theme-edit.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-theme-edit.md)_

---

## `@g-tier-setup`

Configure product tiers for this project — interactive wizard to define tier names, operational requirements, version prefixes, and remote repos. Activates g-sk

**Usage:**

@g-tier-setup # If unconfigured, defaults to SETUP; if configured, defaults to ENABLE @g-tier-setup SETUP # Explicit first-time setup @g-tier-setup ENABLE # Annotate subsystems and run tier sync @g-tier-setup SETUP --force # Overwrite existing release_profiles/ (destructive; warns first)

**Related:**

- `g-skl-tier-setup` — the skill that this command delegates to
- `g-skl-subsystems` — writes `min_tier:` on new subsystem creation
- `g-skl-release` — reads `release_profiles/` for CREATE / ASSIGN / PUBLISH
- `custom_scripts/platform_parity_sync.ps1 -TierSync` — the actual template-directory populator

_Source: [g-tier-setup.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-tier-setup.md)_

---

## `@g-triage`

Parse unstructured external input (emails, Slack dumps, meeting notes, pasted URLs) and route each item to the correct gald3r destination.

**Usage:**

@g-triage "paste your email/Slack/notes here" @g-triage --file path/to/notes.txt @g-triage https://github.com/org/repo/issues/42 @g-triage --clipboard # read from clipboard contents

**Related Commands:**

- `@g-idea-capture` — direct single-idea capture (no triage step)
- `@g-task-add` — direct task creation (no triage step)
- `@g-bug-add` — direct bug report (no triage step)
- `@g-propose` — full proposal generation from a single concept

_Source: [g-triage.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-triage.md)_

---

## `@g-update`

Check the installed gald3r version and apply framework updates.

**Usage:**

💡 gald3r update available (v{current} → v{latest}) — run @g-update

**Flags:**

| Flag | Description |
|------|-------------|
| `--check` | Display current vs latest version (no changes made) |
| `--apply` | Show step-by-step update instructions for your install type |
| `--changelog` | Display CHANGELOG.md entries newer than current installed version |
| `--dry-run` | With `--apply`: print all planned project-side changes (VERSION, release backfill, inherited constraints) without writing |

---

_Source: [g-update.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-update.md)_

---

## `@g-upgrade`

Check for gald3r updates and upgrade if available

**Usage:**

@g-upgrade → check and offer to upgrade (interactive) @g-upgrade --skip → dismiss current available version; store in .gald3r/.update_skips @g-upgrade --force → upgrade immediately without confirmation prompt

**Notes:**

- Upgrade uses `gald3r_install mode=upgrade` (MCP) or `gald3r upgrade --apply` (CLI); both preserve all `.gald3r/` user data (tasks/bugs/PLAN/etc. are on an absolute denylist)
- After upgrade, any cached skill/rule content in the current session should be treated as potentially stale — re-read skills before relying on them
- The `--force` flag is useful in CI or non-interactive contexts

_Source: [g-upgrade.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-upgrade.md)_

---

## `@g-vault-frontmatter-fix`

Retrofit Obsidian frontmatter onto vault notes missing it

**Usage:**

@g-vault-frontmatter-fix [arguments]

**Flags:**

| Flag | Effect |
|---|---|
| `--dry-run` (default) | Report + show planned frontmatter; no writes |
| `--apply` | Write (with per-file backup); requires explicit confirmation |
| `--file <path>` | Single-file mode |

**Behavior:**

Runs `.claude/skills/g-skl-vault/scripts/frontmatter_fix.py`:

1. Resolve the vault from `.gald3r/.identity` `vault_location=` (no-op when `{LOCAL}`/unset).
2. Walk `projects/*/memory.md`, `projects/*/sessions/`, `projects/*/decisions/`, `knowledge/`.
3. Skip files that already start with `---` (idempotent), and read-only / symlinked files (warned).
4. **Dry-run (default)**: print the would-be frontmatter per non-conformant file.
5. **`--apply`**: back up each file to `{vault}/.backups/{timestamp}/<relpath>` then prepend the
   block (existing content preserved byte-for-byte). UTF-8 without BOM.

```powershell
uv run python .claude/skills/g-skl-vault/scripts/frontmatter_fix.py            # dry-run
uv run python .claude/skills/g-skl-vault/scripts/frontmatter_fix.py -Apply
uv run python .claude/skills/g-skl-vault/scripts/frontmatter_fix.py -File "<path>" -Apply

Notes:

• Type inference: memory.md/sessions/ → session; decisions/ → decision;

knowledge/ → knowledge_card. title comes from the leading # header (or filename).

• Does not touch .gald3r/learned-facts.md (project-internal, not vault-stored).
• @g-vault-lint flags missing frontmatter; @g-vault-lint --auto-fix <file> calls this on one file.
• See VAULT_OBSIDIAN_STANDARD.md and g-skl-vault § Required Frontmatter.

_Source: g-vault-frontmatter-fix.md_

---

@g-vault-ingest

Ingest or update vault content

Usage:

@g-vault-ingest [arguments]

What This Command Does:

Routes new knowledge into the file-first gald3r vault with Obsidian-safe wikilinks.

_Source: g-vault-ingest.md_

---

@g-vault-lint

Lint the vault

Usage:

@g-vault-lint [arguments]

What This Command Does:

Runs a structural and freshness audit of the vault.

_Source: g-vault-lint.md_

---

@g-vault-process-inbox

Process the vault raw/ inbox

Usage:

@g-vault-process-inbox [arguments]

Behavior:

• Re-running on an empty inbox is a no-op (exit 0)
• Idempotent: never re-processes files already in processed/ or failed/
• Cross-platform: PowerShell 7+ (Windows native, pwsh on Linux/macOS)
• C-001 (file-first vault), C-006 (operations logged), C-009/C-010 (parity) apply

What This Command Does:

Invokes the Phase 2 raw inbox watcher (raw-inbox-watcher.py) which scans {vault}/raw/ for dropped files and routes each one rules-based:

Drop Type	Routed To
*.md	research/articles/
Single URL in *.txt	g-skl-ingest-url
Single YouTube URL *.txt	g-skl-ingest-youtube
Multi-line *.txt	wrapped to .md in research/articles/
*.pdf	deferred to Phase 3 → raw/failed/
*.png / *.jpg	deferred to Phase 3 → raw/failed/

On success, files move to raw/processed/YYYY-MM-DD/. On failure, files move to raw/failed/ with a sibling error.md.

A summary entry is appended to vault/log.md per run (C-006).

_Source: g-vault-process-inbox.md_

---

@g-vault-search

Search the vault

Usage:

@g-vault-search [arguments]

What This Command Does:

Searches the file-first vault without requiring MCP or database services.

_Source: g-vault-search.md_

---

@g-vault-status

Show vault status

Usage:

@g-vault-status [arguments]

What This Command Does:

Summarizes vault health, scale, and recent activity.

_Source: g-vault-status.md_

---

@g-vocab-add

Add or update an abbreviation in .gald3r/vocab.md.

Usage:

@g-vocab-add "ABBR = Full expansion text — usage context"
@g-vocab-add "CRASH = Commands/Rules/Agents/Skills/Hooks — platform folder contents"
@g-vocab-add "CRASH = Commands/Rules/Agents/Skills/Hooks — platform folder contents" --local

Flags:

• --local — write to this project only, skip WPAC propagation even if parent is reachable

What It Does:

1. Parses ABBR = expansion — context from the argument
2. Checks if the abbreviation already exists in local vocab.md (case-insensitive)
3. If new: appends a row to the ## Active Vocabulary table
4. If exists: updates the existing row
5. WPAC propagation (unless --local flag): if .gald3r/workspace/topology.md exists and declares a resolvable local parent: path, also writes the entry to the parent's .gald3r/vocab.md — making it available workspace-wide
6. Confirms with: 📖 Added: ABBR → expansion [propagated to parent: {name}] or 📖 Added: ABBR → expansion [local only]

_Source: g-vocab-add.md_

---

@g-vocab-list

Display all active abbreviations from .gald3r/vocab.md.

Usage:

@g-vocab-list
@g-vocab-list "CRASH"    # show definition for a specific abbreviation

_Source: g-vocab-list.md_

---

@g-vocab-search

Find matching abbreviations or conventions in .gald3r/vocab.md.

Usage:

@g-vocab-search "term"
@g-vocab-search "platform"   # matches CRASH (expansion mentions platform folders)

What It Does:

1. Reads .gald3r/vocab.md
2. Case-insensitive substring match of term against each row's Abbreviation, Expansion,

and Context columns (both the ## Active Vocabulary and the convention tables)

1. Prints matching rows; if none match, reports No vocab entry matches "term"

_Source: g-vocab-search.md_

---

@g-wishlist-mine

Reads a free-form, human-prose intent/wishlist document (the user's own words, no schema) and

Usage:

@g-wishlist-mine [doc-path] [--dry-run] [--target-repo <repo_id>] [--cascade]

Related:

• Skill: g-skl-wishlist-mine (implementation), g-skl-tasks (task creation), g-skl-wpac-order (cascade)
• Task: T453

_Source: g-wishlist-mine.md_

---

@g-workflow

Score complexity and expand tasks or plan sprints. Activates g-tasks → EXPAND or SPRINT PLAN.

Usage:

@g-workflow

_Source: g-workflow.md_

---

@g-workspace-export

Compatibility Alias for @g-wrkspc-export

Usage:

@g-workspace-export --dry-run
/g-workspace-export --dry-run

What This Command Does:

This long-form Workspace-Control command remains supported for backwards compatibility. Prefer @g-wrkspc-export for day-to-day use.

_Source: g-workspace-export.md_

---

@g-workspace-status

Compatibility Alias for @g-wrkspc-status

Usage:

@g-workspace-status
/g-workspace-status

What This Command Does:

This long-form Workspace-Control command remains supported for backwards compatibility. Prefer @g-wrkspc-status for day-to-day use.

_Source: g-workspace-status.md_

---

@g-workspace-sync

Compatibility Alias for @g-wrkspc-sync

Usage:

@g-workspace-sync --dry-run
/g-workspace-sync --dry-run

What This Command Does:

This long-form Workspace-Control command remains supported for backwards compatibility. Prefer @g-wrkspc-sync for day-to-day use.

_Source: g-workspace-sync.md_

---

@g-workspace-validate

Compatibility Alias for @g-wrkspc-validate

Usage:

@g-workspace-validate
/g-workspace-validate
@g-workspace-validate .gald3r/tasks/task181_workspace_commands.md

What This Command Does:

This long-form Workspace-Control command remains supported for backwards compatibility. Prefer @g-wrkspc-validate for day-to-day use.

_Source: g-workspace-validate.md_

---

@g-wpac-adopt

Register a child project under this project

Usage:

@g-wpac-adopt <target_project_path>
@g-wpac-adopt <target_project_path> --one-way

What This Command Does:

Establishes a parent → child relationship between this project and the target project. Updates link_topology.md on both sides when the target is locally accessible.

Delegates to g-skl-wpac-adopt.

Examples:

_Source: [g-wpac-adopt.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-wpac-adopt.md)_

---

## `@g-wpac-archive-inbox`

Archive stale [DONE] WPAC inbox messages and prune the index

**Usage:**

@g-wpac-archive-inbox @g-wpac-archive-inbox 14 # archive [DONE] older than 14 days

**What This Command Does:**

Moves resolved (`[DONE]`/`[RESOLVED]`) WPAC inbox messages older than a threshold (default **30 days**) out of the active index and into `.gald3r/linking/messages/archive/`, then prunes their rows from `INBOX.md`. Keeps the active index lightweight (target: <= 50 active rows). Uses the shared script `gald3r workspace inbox` (or its `.py` twin).

The inbox is a lightweight INDEX table (`INBOX.md`) backed by one file per message under `.gald3r/linking/messages/`. Archiving never deletes data: messages are relocated, and an append-only `archive_index.md` records what was moved and when.

**Notes:**

- Idempotent: re-running with nothing eligible is a no-op.
- The session-start inbox check prompts you to run this command when the active
  index carries more than 50 `[DONE]` rows.
- Open items (`[OPEN]`), pending `[ORDER]`/`[REQUEST]`, and `[CONFLICT]` rows are
  never archived.

_Source: [g-wpac-archive-inbox.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-wpac-archive-inbox.md)_

---

## `@g-wpac-ask`

Send a request to the parent project

**Usage:**

@g-wpac-ask We need architecture approval for the new vault schema before task 012 can proceed.

**What This Command Does:**

Writes a REQUEST entry to the parent project's INBOX and marks the specified local task as blocked pending parent action. Uses `g-skl-wpac-ask`.

_Source: [g-wpac-ask.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-wpac-ask.md)_

---

## `@g-wpac-claim`

Register a parent project for this project

**Usage:**

@g-wpac-claim <parent_project_path> @g-wpac-claim <parent_project_path> --one-way

**What This Command Does:**

Establishes a **child → parent** relationship between this project and the target project.
Updates `link_topology.md` on **both sides** when the parent is locally accessible.

Delegates to `g-skl-wpac-claim`.

**Examples:**

_Source: g-wpac-claim.md_

---

@g-wpac-move

Transfer files or folders to another project in the topology

Usage:

@g-wpac-move <ECOSYSTEM_ROOT>/<template_full>/.cursor/skills/g-skl-websocket-sync → example_mcp

What This Command Does:

Safely moves files or entire subsystems from this project to a parent, child, or sibling project. Includes provenance tracking, safety gates, vault log entries in both projects, and forwarding stubs. Uses g-skl-wpac-move.

_Source: g-wpac-move.md_

---

@g-wpac-notify

Send a lightweight [INFO] notification to one or more project INBOXes — no task created, no approval needed.

Usage:

@g-wpac-notify

_Source: g-wpac-notify.md_

---

@g-wpac-order

Push a task or directive to child projects

Usage:

@g-wpac-order update vault schema to v2

What This Command Does:

Broadcasts a task order from this parent project to one or more child projects using the WPAC (Project Command and Control) topology. Uses g-skl-wpac-order.

_Source: g-wpac-order.md_

---

@g-wpac-promote

Promote a controlled_member repository to a fully self-managed autonomous_child

Usage:

@g-wpac-promote <member-id> --dry-run
@g-wpac-promote <member-id> --apply

What This Command Does:

Migrates an existing Workspace-Control controlled_member (or migration_source) repository into a fully-equipped autonomous_child. This is the formal off-ramp for the g-rl-36 marker-only guard (BUG-097): a controlled_member is intentionally restricted to a marker-only .gald3r/ (.identity + PROJECT.md) and @g-skl-setup is blocked there. PROMOTE lifts that guard by flipping workspace_role, backfilling the standard framework files that postdate the original member creation, and updating the workspace manifest.

Delegates to g-skl-workspace PROMOTE operation.

Examples:

_Source: [g-wpac-promote.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-wpac-promote.md)_

---

## `@g-wpac-read`

Review and action the cross-project INBOX

**Usage:**

@g-wpac-read

**What This Command Does:**

Opens `.gald3r/workspace/inbox.md`, triages items by type, and routes each to the appropriate response action. CONFLICTs are surfaced first and block all other work until resolved. Uses `g-skl-wpac-read`.

_Source: [g-wpac-read.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-wpac-read.md)_

---

## `@g-wpac-send-to`

Send files, features, specs, ideas, or code to a related project in the ecosystem

**Usage:**

@g-wpac-send-to --parent|--sibling|--child <project_name> [options]

**What This Command Does:**

Transfers content from this project to any related project (parent, sibling, or child),
writes an INBOX notification in the destination, logs provenance in the source vault,
and optionally deletes the source after confirmation.

Delegates to `g-skl-wpac-send-to`.

**Examples:**

_Source: g-wpac-send-to.md_

---

@g-wpac-spawn

Spawn a new gald3r project from this project with full setup and WPAC topology linking

Usage:

@g-wpac-spawn <new_project_name> --sibling [options]
@g-wpac-spawn <new_project_name> --child [options]
@g-wpac-spawn <new_project_name> --parent [options]

What This Command Does:

Creates a new project in the same ecosystem root, installs gald3r (matching this project's install style), seeds it with the provided description/features/code, runs gald3r-setup subsystem discovery, and immediately registers the WPAC topology link in both projects.

Delegates to g-skl-wpac-spawn.

Examples:

_Source: [g-wpac-spawn.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-wpac-spawn.md)_

---

## `@g-wpac-status`

Show cross-project coordination status

**Usage:**

@g-wpac-status

**What This Command Does:**

Displays the full WPAC (Project Command and Control) status: this project's topology role, linked project health, open INBOX summary, and constraint overlap with peers. Delegates to `g-agnt-wpac-coordinator`.

_Source: [g-wpac-status.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-wpac-status.md)_

---

## `@g-wpac-sync`

Initiate or respond to a sibling contract sync

**Usage:**

@g-wpac-sync example_mcp — we added vault-hooks-automation subsystem

**What This Command Does:**

Exchanges updated contract information with one or more sibling projects. Advisory only — non-blocking. Both sides update their local peer topology copies. Uses `g-skl-wpac-sync`.

_Source: [g-wpac-sync.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-wpac-sync.md)_

---

## `@g-wrkspc-adopt`

Adopt an existing gald3r project into Workspace-Control

**Usage:**

@g-wrkspc-adopt --discover <ECOSYSTEM_ROOT>/example_app @g-wrkspc-adopt --dry-run --source <ECOSYSTEM_ROOT>/example_app --as example_app @g-wrkspc-adopt --apply --source <ECOSYSTEM_ROOT>/example_app --as example_app --plan .gald3r/reports/adoption_adopt-20260426-091500-example_app.md

**What This Command Does:**

Brings an existing gald3r-managed project (one that already has a populated `.gald3r/` folder with tasks, bugs, features, PRDs, subsystem specs, plans, constraints, and linking data) into the current Workspace-Control control project. Plans or applies the adoption; never writes the source project's `.gald3r/`. Delegates to `g-skl-workspace` operation `ADOPT` in one of three modes: discover (preflight + inventory), dry-run (writes the plan report), or apply (gated state change).

The full design lives at `docs/20260426_090736_Cursor_WORKSPACE_CONTROL_PROJECT_ADOPTION.md`.

_Source: [g-wrkspc-adopt.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-wrkspc-adopt.md)_

---

## `@g-wrkspc-export`

Plan a Workspace-Control export dry-run

**Usage:**

@g-wrkspc-export --dry-run /g-wrkspc-export --dry-run

**What This Command Does:**

Short alias for Workspace-Control export planning. Delegates to `g-skl-workspace` operation `EXPORT_PLAN`.

_Source: [g-wrkspc-export.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-wrkspc-export.md)_

---

## `@g-wrkspc-init`

Initialize Workspace-Control manifest

**Usage:**

@g-wrkspc-init --dry-run @g-wrkspc-init --seed docs/20260425_090100_Cursor_WORKSPACE_CONTROL_MANIFEST.yaml --dry-run @g-wrkspc-init --seed docs/20260425_090100_Cursor_WORKSPACE_CONTROL_MANIFEST.yaml --apply

**What This Command Does:**

Creates or promotes `.gald3r/linking/workspace_manifest.yaml` for a control project. Delegates to `g-skl-workspace` operation `INIT_PLAN` by default, or `INIT_APPLY` only with `--apply`.

_Source: [g-wrkspc-init.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-wrkspc-init.md)_

---

## `@g-wrkspc-member-add`

Add a Workspace-Control member to the manifest

**Usage:**

@g-wrkspc-member-add <ECOSYSTEM_ROOT>/<template_full> --id <template_full> --role controlled_member --dry-run @g-wrkspc-member-add <ECOSYSTEM_ROOT>/<template_full> --id <template_full> --role controlled_member --apply

**What This Command Does:**

Plans or applies a registry-only member addition in `.gald3r/linking/workspace_manifest.yaml`. Delegates to `g-skl-workspace` operation `MEMBER_ADD_PLAN` by default, or `MEMBER_ADD_APPLY` only with `--apply`.

_Source: [g-wrkspc-member-add.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-wrkspc-member-add.md)_

---

## `@g-wrkspc-member-list`

List Workspace-Control manifest members

**Usage:**

@g-wrkspc-member-list /g-wrkspc-member-list @g-wrkspc-member-list --role controlled_member

**What This Command Does:**

Lists only repositories declared in `.gald3r/linking/workspace_manifest.yaml`. Delegates to `g-skl-workspace` operation `MEMBER_LIST`.

_Source: [g-wrkspc-member-list.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-wrkspc-member-list.md)_

---

## `@g-wrkspc-member-remove`

Remove or retire a Workspace-Control member from the manifest

**Usage:**

@g-wrkspc-member-remove <template_adv> --dry-run @g-wrkspc-member-remove <template_adv> --apply

**What This Command Does:**

Plans or applies a registry-only member removal or retirement in `.gald3r/linking/workspace_manifest.yaml`. Delegates to `g-skl-workspace` operation `MEMBER_REMOVE_PLAN` by default, or `MEMBER_REMOVE_APPLY` only with `--apply`.

_Source: [g-wrkspc-member-remove.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-wrkspc-member-remove.md)_

---

## `@g-wrkspc-spawn`

Spawn a new local Workspace-Control member project

**Usage:**

@g-wrkspc-spawn <project_name> --id <repo_id> --path <absolute_path> --dry-run @g-wrkspc-spawn <project_name> --id <repo_id> --path <absolute_path> --apply

**Options:**

- `--description "..."` - one-line member role/mission for the manifest.
- `--template none|slim|full|adv` - future template intent only; default `none`. This command does not install gald3r templates.
- `--allow-existing-empty` - permit an existing empty target directory.
- `--role controlled_member` - default and currently the only normal spawn role.

**What This Command Does:**

Creates a brand-new local workspace member project and registers it in `.gald3r/linking/workspace_manifest.yaml`. This mirrors the simple shape of `@g-wpac-spawn`, but it is Workspace-Control membership only: no WPAC topology, no INBOX writes, no task delegation, and no history import.

Delegates to `g-skl-workspace` operation `SPAWN_PLAN` by default, or `SPAWN_APPLY` only when `$ARGUMENTS` includes `--apply`.

_Source: [g-wrkspc-spawn.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-wrkspc-spawn.md)_

---

## `@g-wrkspc-status`

Show Workspace-Control status

**Usage:**

@g-wrkspc-status /g-wrkspc-status

**What This Command Does:**

Short alias for Workspace-Control status. Delegates to `g-skl-workspace` operation `STATUS`.

_Source: [g-wrkspc-status.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-wrkspc-status.md)_

---

## `@g-wrkspc-sync`

Plan a Workspace-Control sync dry-run

**Usage:**

@g-wrkspc-sync --dry-run /g-wrkspc-sync --dry-run

**What This Command Does:**

Short alias for Workspace-Control sync planning. Delegates to `g-skl-workspace` operation `SYNC_PLAN`.

_Source: [g-wrkspc-sync.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-wrkspc-sync.md)_

---

## `@g-wrkspc-validate`

Validate Workspace-Control manifest and routing metadata

**Usage:**

@g-wrkspc-validate /g-wrkspc-validate @g-wrkspc-validate .gald3r/tasks/task203_short_workspace_control_commands.md

**What This Command Does:**

Short alias for Workspace-Control validation. Delegates to `g-skl-workspace` operation `VALIDATE`.

_Source: [g-wrkspc-validate.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-wrkspc-validate.md)_

---

## `@g-wrkspc`

Workspace-Control dispatcher

**Usage:**

@g-wrkspc [arguments]

**What This Command Does:**

Short entry point for Workspace-Control operations. Prefer the explicit subcommands below for clarity.

_Source: [g-wrkspc.md](https://github.com/Gald3r-Labs/gald3r/blob/main/project_template/.claude/commands/g-wrkspc.md)_

---

_Last updated: 2026-07-06 (gald3r v2.4.0)_