fix-my-deployment
Skill0 starsChanged 5 months agoGPL-3.0View on GitHub
Diagnose and repair or update an EXISTING University of Idaho RCDS/IIDS deployment in the `ui-iids/kubernetes-apps` GitOps repo — audit its ArgoCD + Kustomize manifests against the canonical `apps/rcds/apps/deploy-template/` example and the app repo's CI, find what is broken or drifted, and fix it. Handles two cases — (1) REPAIR a broken deploy (ImagePullBackOff, pods pending, sync green but nothing running, previews never appearing), or (2) UPDATE a working deploy (new services, new env vars re-sealed with `kubeseal`, backing services, storage, adding PR previews or SonarQube, promoting to live). Reaches the cluster read-only through either a local kubeconfig or a service account over SSH to a master node, and uses Docker or Podman locally (defaulting to Podman). Does its kubernetes-apps work on a dated `fix/agent-fix-*` branch and opens a PR against `main` labeled `coding-agent` + `fix-deploy` for the user to review and merge. Use when the user says "fix my deployment", "my deployment is broken", "my pods won't start", "ArgoCD won't sync", "update my deployment", "add a service to my deployment", "add env vars to my deployment", "re-seal my secrets", "my preview builds aren't working", "check my kubeconfig", "why won't my pods start", or invokes /fix-my-deployment.
- Reads credentials
- Commits and pushes
In this repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- brainstormSkill
- clean-codeSkill
- deploy-my-applicationSkill
- document-codebaseSkill
- fastapiSkill
- flask-apisSkill
- flaskSkill
- mentorSkill
- orchestratorSkill
- pr-reviewSkill
- rcds-brand-designSkill
- refresh-my-skillsSkill
- review-prSkill
- test-coverageSkill
- track-my-workSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
31 rules. About 0 are common, 15 are distinctive, and 16 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈15
Distinctive · estimate
This author's own choices. Worth a look.
16
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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
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.