conf-mini-sites

Release Conf Mini-Sites to PRODUCTION — deploy the Forge app to its production environment AND both Cloudflare Workers (control + dispatch) to their production environment, via the GitHub-Release → release.yml pipeline. Single app, no variants (the collapse of conf-app's lite/full/diagramly canary). Pre-flight (on master, pushed, CI green, prod prerequisites present) → compose delta-derived release notes → create + publish a vX.Y.Z GitHub Release (which fires the deploy) → wait for the workflow → verify the live build (built-in prod smoke + check-version + a targeted spot check of what shipped). Use when the user wants to release, deploy, ship, cut a release, or promote Conf Mini-Sites to production. Triggers on "release app", "release to prod", "deploy to production", "ship the mini-site app", "cut a release", "release conf-mini-sites", "push to production".

Start the conf-mini-sites Cloudflare Workers locally — the dispatch (serve gateway) and remote (control/provisioner) Workers, each with its own wrangler config. Use when setting up local dev for the Workers, running them with wrangler dev, or debugging grant minting / verification locally.

Monitor and fix failing GitHub Actions CI checks on PRs for ZenUml/conf-mini-sites. Use when the user says "babysit PR", "check PR status", "fix CI", "PR is failing", "watch this PR", "why is CI red", or when used with /loop to continuously monitor a PR. Also use when E2E test flakiness, typecheck issues, or unit test failures block merging. Triggers on any PR monitoring, CI failure diagnosis, or automated fix-and-retry workflow.

Confirm which build of Conf Mini-Sites is live — the deployed Forge app version per environment, the live control + dispatch Worker versions, and (on a real page) that the macro resolved its per-instance reference. Use after a deploy, in a spot check, or in PVT to confirm the expected build is running. Triggers on "check version", "what version is live", "confirm the deploy", "which build is on lite-dev", "is my deploy live".

Create a Confluence page carrying the Conf Mini-Sites Forge macro (key `mini-site`) entirely via REST API — no browser, no editor UI. Use whenever you need a real page that renders a mini-site (to validate a serve/dispatch change, a CSP tweak, or a relative-path resolution fix) without driving the Publisher modal. Optionally pre-publishes a multi-file bundle to the page's instance so it renders live on first load. Triggers on "create test page", "render test", "API test page", "skip the editor", "stand up a mini-site page", or when validating a dispatch/serve fix.

Count Conf Mini-Sites Forge app installs per environment (production / staging / development) plus the delta vs prior snapshots from 1 day and 7 days ago (which sites were added / removed since the last check). Use whenever the user asks "how many installs", "how many tenants", "how many sites have the mini-sites app", "install count", "any new installs", "did anyone uninstall", "active sites", "where is mini-sites installed", "list installs", "show installed sites". Source-of-truth is Atlassian's Forge platform via `forge install list` — there is one app id (no lite/full/diagramly variants), so the skill takes no variant argument.

Run a Forge tunnel to test local conf-mini-sites Forge app changes on a live Confluence instance. Use when the user wants to test the mini-site macro locally, run forge tunnel, debug the Forge Custom UI on a live site, or verify manifest/resolver changes before deploying. Triggers on "forge tunnel", "tunnel to confluence", "test the mini-site locally", "run tunnel", "test on lite-dev", or any request to proxy local Forge app code to a live Atlassian site.

Merge a green PR to master and verify CI succeeds. Use when the user says "merge", "land", "land PR", "merge this", or when a PR has passed CI and is ready to merge. This does NOT deploy to production — that is a separate release step.

Mark a Draft PR as Ready for Review on ZenUml/conf-mini-sites so the next CI run includes E2E. Use when the user says "mark ready", "ready PR", "ready for review", "trigger e2e", "run e2e on this PR", "open it up for review", or wants to verify with E2E without committing to a merge yet. Useful mid-development when you don't want to wait until the last minute to find out if E2E passes.

Reproduce a bug in Conf Mini-Sites. Extract the bug from the current conversation or user prompt, then reproduce it in the SIMPLEST environment that exercises the affected code path. Use when the user says "repro", "reproduce", "can you repro this", "reproduce the bug", "verify this bug", or describes a bug they want confirmed. Try environments in strict order: a unit/integration test first, then local `wrangler dev`, then the deployed dev Workers via curl, then a real Confluence page as last resort.

Create a branch, run local validation, create a PR and **merge** on master. Use when the user says "ship", "ship it", "ship this branch", "merge this", or wants to go from local branch to merged in one command. Stops at the first failure. Does NOT deploy to production — that is a separate release step after shipping.

Ad hoc, AI-driven verification of a specific Conf Mini-Sites behavior — not a checked-in E2E test. Use after developing a feature, fixing a bug, validating a branch, or post-deploy. Drives Playwright MCP for the Forge Custom UI + the nested dispatch-served mini-site iframe, or CLI (curl / wrangler / forge) for backend signals (provision, grant, serve, lifecycle). Triggers on "spot check", "run a spot check on X", "spot check this fix", "spot check on lite-dev", "verify the render", "verify on the dev site".

Push the current branch and create or reuse a PR on ZenUml/conf-mini-sites. Use when the user says "submit", "create PR", "push and PR", "open a pull request", "submit branch", or wants to publish their work as a PR without merging. After the PR exists it always babysits CI (via babysit-pr — monitor + auto-fix). Does not merge — use land-pr for that.

Run local validation checks on the current branch before shipping. Use when the user says "validate", "check branch", "am I good", "run tests", "preflight", "is this ready", or wants to verify their branch passes all checks before pushing or creating a PR. Also use as a precondition check before invoking submit-branch or ship-branch.