agentleFS
Sign inStart free
stoa-platformstoa-platform/stoa/.claude/skills/monitor-cd/SKILL.md

monitor-cd

Skill9 starsChanged 7 months agoApache-2.0View on GitHub

Continuous post-merge CD monitoring using /loop. Runs /deploy-check on interval until all checks pass or timeout.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run continuous CD verification after a merge to main.

    line 15
  2. Very specific:

    Use the /loop command to schedule recurring /deploy-check at the specified interval

    line 27
  3. Distinctive:

    Stop automatically when all checks pass (verdict: Go)

    line 36
  4. Very specific:

    If $ARGUMENTS is empty, use 5m as default interval.

    line 45
  5. Distinctive:

    After merging a PR to main (especially code changes that trigger Docker build + ArgoCD sync)

    line 49
  6. Distinctive:

    After a hotfix deployment

    line 50
  7. Distinctive:

    When ArgoCD sync seems stuck

    line 51
  8. Very specific:

    When you can verify manually with a single /deploy-check

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Monitor CD — Continuous Deployment Verification

Run continuous CD verification after a merge to main.

Usage

/monitor-cd        → runs /deploy-check every 5 minutes (default)
/monitor-cd 2m     → runs every 2 minutes

Workflow

  1. Parse interval from $ARGUMENTS (default: 5m)
  2. Use the /loop command to schedule recurring /deploy-check at the specified interval
  3. Each iteration runs the full deploy-check:
    • CI on main (latest workflow run)
    • API health (api.gostoa.dev)
    • Gateway health (mcp.gostoa.dev)
    • Console + Portal (200 check)
    • Pod status (kubectl)
    • ArgoCD sync status
  4. Report results as a table after each check
  5. Stop automatically when all checks pass (verdict: Go)

Command

Run this:

/loop $ARGUMENTS /deploy-check

If $ARGUMENTS is empty, use 5m as default interval.

When to Use

  • After merging a PR to main (especially code changes that trigger Docker build + ArgoCD sync)
  • After a hotfix deployment
  • When ArgoCD sync seems stuck

When NOT to Use

  • For docs-only changes (no CD pipeline triggered)
  • When you can verify manually with a single /deploy-check

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free