Watch Flux Rollout
After a push or merge, watch a CircleCI + FluxCD deploy until it lands — CI green, then the k8s Deployment image tag moves and pods go ready — then run a read-only smoke test scoped to the change. Goal-terminating loop; stops on landing or failure.
Install
npx skills add flurdy/agent-skills --skill watch-flux-rolloutgit clone --depth 1 https://github.com/flurdy/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/watch-flux-rollout ~/.claude/skills/watch-flux-rolloutPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Watch Flux Rollout
Watch a CircleCI + FluxCD deploy of one commit until it's live, then smoke-test the change —
the kubectl/CircleCI sister of `/watch-actions-rollout` (which watches GitHub Actions CD). Built for
single-repo services deployed the Flux image-automation way: CircleCI builds and pushes an
image tagged `<base>.<CIRCLE_BUILD_NUM>`, a Flux ImagePolicy bumps the Deployment, the cluster
rolls it out.
The rollout-confirmation semantics are extracted from the multirepo `/release-manager` (step 4)
and `deploy-status.sh` flow: the exact post-push tag is **unknowable at push time** (the build
number is assigned when CircleCI runs), so "deployed" means the live tag has **moved off** the
pre-push baseline — never an exact-tag match.
## Usage
```
/watch-flux-rollout # latest origin/main commit
/watch-flux-rollout <sha> # specific commit
/watch-flux-rollout --no-smoke # watch the rollout only, skip the smoke test
```
## Execution telemetry
Only for a normal valid execution request, not when reading this file as context, record once:
```text
~/.agents/skills/watch-telemetry/scripts/watch_telemetry.py record watch-flux-rollout {harness} invocation
```
Bind `{harness}` to `pi` or `claude` from the known current harness, never a model name or shell
probe; otherwise skip. Use only already-permitted recording. Never enable collection, change
permissions, or wait for telemetry approval. Missing/denied/failed recording must not block work.Details
- Skill name
watch-flux-rollout- Repository
- flurdy/agent-skills
- Path
skills/watch-flux-rollout/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Watch Flux Rollout skill do?
After a push or merge, watch a CircleCI + FluxCD deploy until it lands — CI green, then the k8s Deployment image tag moves and pods go ready — then run a read-only smoke test scoped to the change. Goal-terminating loop; stops on landing or failure.
How do I install the Watch Flux Rollout skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add flurdy/agent-skills --skill watch-flux-rollout. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Watch Flux Rollout popular?
It lives in flurdy/agent-skills, which has 9 GitHub stars and 0 forks.
Related skills
Architect
9flurdy/agent-skills
Architecture and implementation planning gate for complex or high-blast-radius work. Produces evidence-backed decisions, reviewable slices, acceptance evidence, and conditional human review ownership without editing code.
Artifact Hygiene
9flurdy/agent-skills
Run a local-only, read-only advisory audit of publishable working-tree files and unpublished branch history with redaction-safe findings.
Backlog Groom
9flurdy/agent-skills
Auto-detects workspace unfinished backlogs across unique stores; otherwise local open beads. Flags thin prose, missing labels, drift, lifecycle and duplicates. Report-only; mutations need approval, destructive ones individually.
Watch Rollout
9flurdy/agent-skills
Choose and launch the appropriate rollout watcher. Prompts between implemented deployment stacks unless an explicit selector is supplied, then delegates without weakening stack-specific safety.
Watch Actions Rollout
9flurdy/agent-skills
After a merge, watch the GitHub Actions deploy until the gating job lands, then run a scoped smoke test against staging (browser for UI, GET for read-only API). Goal-terminating loop — stops when the deploy lands and the smoke completes, or fails.
Spec to Symphony
5adelrioj/claude-skills
Use when a groomed Linear ticket already carries its design spec and the build must be handed to a Symphony autonomous pipeline — puts the spec on the remote under the filename that deployment actually reads, then arms the existing ticket so the poller dispatches it. The ticket must already exist; this skill never creates one. Triggers on: hand off to symphony, hand the build to symphony, arm the pipeline, arm the ticket, spec to symphony, spec-to-symphony.
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.