Skip to content

ddtcorex/maestro-skills / skills/govard-toolbox

govard-toolbox

Flagged

Use 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.

FileKindSize
SKILL.mdskill md10.4 KB
references/AUDIT.mdmarkdown4.6 KB
references/COMMANDS.mdmarkdown7.3 KB
references/CONFIGURATION.mdmarkdown2.2 KB
references/DEPLOYMENT.mdmarkdown4.8 KB
references/FAQ.mdmarkdown3.5 KB
references/GUIDES.mdmarkdown2.8 KB
references/HOST-WITHOUT-DOCKER.mdmarkdown1.8 KB
references/SANDBOX.mdmarkdown5.0 KB
references/VERIFY.mdmarkdown23.8 KB

references/SANDBOX.md

View on GitHub
# Sandbox Rehearsal Target

A derived project that plays a production remote over real SSH/rsync: `govard sandbox up` renders the origin project's own blueprint (PHP series, services) into one container, so `govard deploy --remote sandbox --yes` rehearses the exact deploy path. See `SKILL.md` Deployment for the deploy side.

```bash
govard sandbox up --profile full --php <series> --docroot symlink  # fresh: seeds once from the running origin env
govard sandbox status     # absent | dormant | running (+ profile/PHP from container labels)
govard sandbox ssh        # shell into the rehearsal target
govard deploy --remote sandbox --yes   # rehearse; also db dump -e sandbox, remote exec sandbox -- …, sync -e sandbox
govard sandbox reset      # wipe deploy dirs (--docroot reshapes); re-seed shared files after
govard sandbox down       # stop + remove container, keep volumes; --volumes deletes them, --purge also removes image+key+mirror
```

## Synthetic remote (nothing is configured, ever)

While the container runs, the literal name `sandbox` resolves as a synthetic remote from live Docker state; no `remotes.sandbox` block is written. `govard remote list` always prints its row (`sandbox | (implicit) | running|dormant|absent`). `sandbox` is reserved: `govard remote add sandbox` is refused, and a leftover `remotes.sandbox` block is shadowed with a warning (delete it).

## Seed-once gate

The seed runs only on a fresh container from the still-running origin env (DB dump with DEFINER-strip then import, one media tree, one framework-rewritten env file with `base_url` on the sandbox URL). Origin down: `up` refuses and says to start it with `govard env up` first, or pass `--no-seed`; `--no-seed` starts deliberately empty; `--recreate` rebuilds the image and container; `--reseed` refreshes the database and files from the origin even when the sandbox already holds them; plain reuse keeps data. Magento note: `env.php` is rewritten and service hosts are localized to loopback.

## Profiles and docroot

`basic` (sshd/rsync/git) / `php` (default; adds php-cli, composer, node) / `full` (adds a database and a cache). `--php` picks the PHP series (default: the project's `stack.php_version` when it names a series; an existing sandbox keeps its series), `--db` picks the `full` profile's database (`mariadb:<series>`; a MySQL stack is refused rather than rehearsed on another engine), and `--docroot absent|symlink|real` shapes the target: `absent`/`symlink` select the atomic swap, `real` selects in-place publish. An explicit conflicting `--profile` on a running sandbox is refused with a `--recreate` hint.

## Traps

- Fresh `symlink` sandbox: `remote exec` fails on the dangling `current` until the first deploy. Deploy first or use `--docroot real`.
- No search service is provided by the sandbox, so a search-dependent step can fail. If `setup:upgrade` does, disable the search modules in a scratch release, or join the origin env's network and borrow its engine (revert afterwards).
- The sandbox mirrors the project's **git repository**: the project must be a git repo with the work committed, and tracked build output (for example Magento's `pub/static`) breaks the release build. Keep `.govard/` and build output out of git.
- The origin must be installed and running: an empty origin database makes the seed fail on missing core tables.
- The seed copies the database and the framework's media tree. It does **not** seed environment files that live outside the repository, so a first deploy fails at the migrate step until the target has them (`shared/.env`, `shared/.env.local`, `shared/wp-config.php`: see the framework skill). `sandbox reset` wipes `shared/`, so re-seed afterwards. Write them non-interactively with `printf '...' | govard sandbox ssh`.
- The `full` profile waits for its database to answer, using the MariaDB client names (`mariadb-admin`, `mariadb`, `mariadb-dump`) when the image ships no `mysql*` ones. A seed that fails half way is retried by the next plain `up`.
- `sandbox ssh` opens an interactive shell; `sandbox ssh -- <cmd>` runs one command without a tty and returns the command's own exit status (a command without `--` is a usage error). `govard remote exec sandbox -- <cmd>` is the deploy-aware alternative. `govard open <target> -e sandbox` resolves the synthetic remote.
- `.govard/sandbox/` (the private key) ignores itself, so `git add -A` never stages it. `sandbox down --purge` removes the images of every profile built for the project.
- `deploy unlock --force` clears the lock but not maintenance mode; a deploy that failed mid-way can leave the live release returning 503 until a later deploy or `--resume` completes.
- `up` waits for a real SSH login, not just an open TCP port. No Docker means exit `3` `CAPABILITY_MISSING`.

Recipe extras (`deploy.settings.sandbox_packages|extensions|services|tools`) REPLACE the recipe lists (`sandbox_tools` only takes binaries from the engine's known list). `up` best-effort registers the slug on the shared SSH gateway (`127.0.0.1:2222`); absence never fails sandbox ops.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall