aiox-devops

Run automated quality gates and control GitHub push, PR, and release operations.

Updated May 8, 2026
One-click install
npx skills add https://github.com/Elevaria-bia/elevaria-bia.github.io --skill aiox-devops-elevaria-bia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aiox-devops
Source: https://github.com/Elevaria-bia/elevaria-bia.github.io/tree/main/meu-projeto/.claude/skills/AIOX/agents/devops
Command: npx skills add https://github.com/Elevaria-bia/elevaria-bia.github.io --skill aiox-devops-elevaria-bia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents broken code from reaching your main branch by enforcing mandatory CI quality gates and by centralizing all remote GitHub push/PR/release actions into a controlled workflow.

Core Features & Use Cases

  • Pre-push quality gates: Runs lint, tests, typecheck, build, and CodeRabbit checks, then requires explicit user confirmation before any push.
  • Versioning and releases: Recommends and applies semantic version bumps, generates changelogs, tags versions, and creates GitHub releases.
  • Repository governance operations: Detects repository context, creates PRs, configures/updates CI workflows, and cleans up stale branches.
  • Use case: After finishing Story 3.14, run the full gate suite, confirm the recommended version bump, push to the remote, and open a PR only if all checks pass.

Quick Start

Use the aiox-devops skill to run pre-push checks and prepare for a safe push by asking for quality gating before deploying changes.

Frequently Asked Questions about aiox-devops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent broken code from being pushed to my GitHub main branch?

Pre-push quality gates prevent broken code from reaching your GitHub main branch by running lint, tests, typecheck, and build checks before requiring explicit user confirmation for any remote push operation.

How do I automate semantic versioning and GitHub releases after passing CI checks?

Automate semantic versioning and GitHub releases by applying recommended version bumps, generating changelogs, tagging versions, and creating releases automatically once all mandatory CI quality gates pass successfully.

Do I need CodeRabbit integration to use GitHub pre-push validation?

Yes, CodeRabbit integration is required for GitHub pre-push validation workflows, as it enforces repository integrity by running automated quality gates alongside lint, tests, and typecheck before remote push operations.

What's the best way to clean up stale branches and manage pull requests on GitHub?

Repository governance operations clean up stale branches and manage pull requests by detecting repository context, creating PRs, and configuring CI workflows while maintaining strict push, PR, and release controls.

Can I configure CI/CD workflows and quality gates directly through GitHub CLI actions?

Yes, you can configure and update CI/CD workflows and quality gates through user-confirmed GitHub CLI actions, which centralize remote push, PR, and release operations into a controlled workflow.

Why does my GitHub push require explicit user confirmation during release automation?

Explicit user confirmation is required during release automation to enforce repository integrity, ensuring exclusive git push and GitHub CLI actions only execute after all quality gates and CodeRabbit checks pass.