ddtcorex/maestro-skills / skills/govard-toolbox
govard-toolbox
FlaggedUse when starting or stopping a Govard environment, running container commands, database dump or import, syncing from staging, Xdebug, or a deploy and its rehearsal. Keywords govard up, govard sh, govard deploy.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.4 KB |
| references/AUDIT.md | markdown | 4.6 KB |
| references/COMMANDS.md | markdown | 7.3 KB |
| references/CONFIGURATION.md | markdown | 2.2 KB |
| references/DEPLOYMENT.md | markdown | 4.8 KB |
| references/FAQ.md | markdown | 3.5 KB |
| references/GUIDES.md | markdown | 2.8 KB |
| references/HOST-WITHOUT-DOCKER.md | markdown | 1.8 KB |
| references/SANDBOX.md | markdown | 5.0 KB |
| references/VERIFY.md | markdown | 23.8 KB |
references/HOST-WITHOUT-DOCKER.md
View on GitHub# Host without Docker
The runtime requirement manifest, the commands that need no container, and what a host-only
session can and cannot do.
Govard works without a container runtime. Every command declares its runtime
requirement, and the requirement-free set is derived from that manifest:
```bash
govard capabilities # command, requirement, host status
govard capabilities --json # machine-readable, schema_version 1
```
- `CAPABILITY_MISSING` / exit code `3` means a declared capability (docker, ssh,
rsync, cloudflared, net) is unavailable. The message names the capability, and
`govard env up --error-json` prints it as a versioned JSON envelope. Do not
hand-parse the text form.
- `govard doctor` exits `0` when only optional capabilities are missing and
reports `required`/`severity`/`affects` per check; `govard doctor --strict`
treats optional warnings as failures (the hard gate for bootstrap scripts).
- Container-free analysis: `govard audit run --checks integrity --format json`
runs Go analyzers on the checkout with no Docker, no PHP and no toolchain. It
is supported on Magento 2 only (composer manifest/lock problems plus
module/DI wiring problems, `govard-integrity` findings); Laravel, Symfony and
WordPress exit 1 with "does not support integrity audit". **`--checks lint` still needs Docker** and, without it, exits `3`
pointing at `--checks integrity`.
Xdebug is orthogonal to the container: on a host with `stack.features.xdebug`
on, the audit refuses to start and asks for `--allow-xdebug` (`govard verify`
has the same flag). Pass the flag or turn Xdebug off; this is not a
capability failure and the exit code is not `3`.
- Commands that forward their arguments (`govard tool php ...`,
`govard redis cli ...`) cannot parse `--error-json`; their exit codes are
unchanged.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |