Ci cd specialist
Skill rafaelghif/antigravity-agents/.agents/skills/ci-cd-specialist
Enterprise-Grade Guardrails, Zero-Assumption Execution, and Quality Gates for Autonomous AI Coding Agents.
npx -y skills add rafaelghif/antigravity-agents --skill ci-cd-specialistAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
DevOps and Pipeline management skill to ensure code passes server-side CI/CD environments.
SKILL.md
1.6 KB, as published. Nobody here has run it
CI/CD Specialist Skill
Objective
To bridge the gap between local development and server-side execution. Prevents the "It works on my machine" syndrome by rigorously auditing Dockerfiles, CI yaml files, and remote pipeline logs.
When to Execute
- When a PR check or pipeline fails (e.g., GitHub Actions red cross).
- When modifying
.github/workflows/,.gitlab-ci.yml, orDockerfile. - When deploying the application to an environment.
Execution Steps
-
Pipeline Discovery:
- Inspect the
.github/workflows/or equivalent directory. - Understand the runner environment (Ubuntu, Alpine), Node/Python versions, and required environment variables or secrets.
- Inspect the
-
Log Analysis:
- When fixing a pipeline failure, DO NOT guess.
- Analyze the exact step that failed in the CI/CD log. Identify if the failure is due to a missing dependency, a network timeout, a failing test, or a syntax error.
-
Local Simulation:
- Before committing a fix for a CI issue, attempt to simulate the exact CI command locally if possible (e.g., running
npm run lintordocker buildwith the exact flags used by the CI).
- Before committing a fix for a CI issue, attempt to simulate the exact CI command locally if possible (e.g., running
-
Security Check:
- Ensure that the pipeline does not echo or log secrets.
- Verify that third-party actions/images use specific commit SHAs (Provenance) rather than mutable tags like
latestorv1.