Documents CI/CD pipeline changes, security implications, and rollback plans before deployment config edits.
npx skills add https://github.com/Vimurai/ai-os --skill ci-gate-vimurai
Please help me install this Agent Skill. Skill: ci_gate Source: https://github.com/Vimurai/ai-os/tree/main/.claude/skills/ci_gate Command: npx skills add https://github.com/Vimurai/ai-os --skill ci-gate-vimurai
.ai/DEVOPS.md before any edits happen. ## Core Features & Use Cases - Mandatory Change Documentation: Records what is changing, why, security implications (new secrets, network access, permissions), and a rollback plan in .ai/DEVOPS.md before edits. - Pipeline Order Enforcement: Enforces the canonical stage order — lint, typecheck, test, build, deploy — with deploy restricted to protected branches. - Audited Skip Mechanism: Blocks --no-verify bypasses; deliberate skips require AI_OS_CI_SKIP=1 with a recorded reason (D-072). - Use Case: Before adding a new deployment step to a GitHub Actions workflow, the gate requires you to document the new secrets it needs and how to revert it, then verify the change on a branch with ai ci run before merging. ## Quick Start Ask the agent to update the GitHub Actions deploy workflow and require the CI gate documentation in .ai/DEVOPS.md first.High-intent search queries and answers about installing and using this skill.
Document the change in .ai/DEVOPS.md before editing: what is changing and why, security implications such as new secrets or permissions, and a rollback plan. Then test the change on a branch and confirm a green ai ci run before merging.
The enforced order is lint, typecheck, test, build, then deploy. Build runs only if tests pass, and deploy runs only on protected branches after a successful build.
No, --no-verify bypasses are not allowed. A deliberate skip requires setting AI_OS_CI_SKIP=1 with AI_OS_CI_SKIP_REASON explaining why, and the skip is recorded for audit (D-072).
You must record whether the change needs new secrets, new network access, or new permissions, plus a rollback plan describing how to revert if the pipeline breaks.
Always test pipeline changes on a branch first, never modify the main CI blindly. Merge only after ai ci run reports green and ai ci status confirms it.
f4rkh4dEnforce security and reliability hygiene rules for GitHub Actions workflows.
joeczarRebase a PR onto main, run review pass, verify CI, and merge.
makyua-sanMonitor production deployments for console errors, performance regressions, and page failures.
vecearAutomate security reviews of pull requests using a standardized checklist.