// Publish the docs site to GHCR with a main-<sha> tag and bump site/helm/values.yaml so Argo CD picks it up — without cutting a SemVer release. Use when docs/site changes need to go live between releases.
Run, build, smoke-test, and screenshot the dot-agent-deck binary against an isolated sandbox. Use when asked to "run dot-agent-deck", "launch the TUI", "take a screenshot of the dashboard", "verify the CLI smoke", or "test a change locally" against the dot-agent-deck binary.
Analyze the blast radius of a proposed Kubernetes operation. Accepts free-text input: kubectl commands (e.g., "kubectl delete pvc data-postgres-0 -n production"), YAML manifests, or plain-English descriptions (e.g., "what happens if I delete the postgres database?"). Returns whether the operation is safe and a detailed dependency analysis with confidence levels.
Create a release tag based on accumulated changelog fragments. Run when ready to cut a release.
Write documentation with real, validated examples. Executes commands through the user to capture actual output. Use for any new documentation or major doc updates.
| name | publish-docs |
| description | Publish the docs site to GHCR with a main-<sha> tag and bump site/helm/values.yaml so Argo CD picks it up — without cutting a SemVer release. Use when docs/site changes need to go live between releases. |
| user-invocable | true |
Publishes a docs-only image to ghcr.io/vfarcic/dot-agent-deck-docs with a main-<short-sha> tag and updates site/helm/values.yaml so Argo CD picks it up. Does not create a release, version bump, binary build, Homebrew formula, Scoop manifest, or GitHub release.
main and you want them live now./dot-ai-tag-release instead. The release workflow already publishes docs as part of the release via the same underlying docs-publish.yml workflow.The workflow dispatches against origin/main, so make sure you know what's there:
git fetch origin
git checkout main
git pull --rebase origin main
If the user is in a worktree, fetch is enough — they don't need to switch branches; gh workflow run --ref main dispatches against the remote ref regardless of local checkout.
LAST_TAG=$(git tag --list 'v*' --sort=-v:refname | grep -E '^v[0-9]+\.[0-9]+\.[0-9]+$' | head -1)
echo "Last release: ${LAST_TAG}"
git log --oneline "${LAST_TAG}..origin/main" -- docs/ site/
git diff --stat "${LAST_TAG}..origin/main" -- docs/ site/
If there are no docs/site changes since the last release, inform the user and stop — there is nothing meaningful to publish.
Present:
site/helm/values.yaml image.tag (e.g. v0.26.0).main-<short-sha> where short-sha is git rev-parse --short=7 origin/main.Ask the user to confirm before triggering the workflow.
gh workflow run docs-publish.yml --ref main
sleep 5
RUN_ID=$(gh run list --workflow=docs-publish.yml --branch=main --limit 1 --json databaseId --jq '.[0].databaseId')
gh run watch "$RUN_ID"
On success, tell the user:
main-<sha>).chore: publish docs image main-<sha> [skip ci] commit was pushed to main — they should git pull to pick it up.values.yaml change and sync within a minute or two; the site at https://agent-deck.devopstoolkit.ai will update shortly after.main-<sha> tag. The next /dot-ai-tag-release will re-pin it to v<semver> automatically.values.yaml diff is empty, so no commit happens.:latest is untouched: manual runs never push or move the :latest tag. That tag follows formal releases only./prd-done, /dot-ai-prd-full, or any release skill — it would interfere with the release path's own docs publish step.changelog.d/ is needed.