aiox-devops

Coordinate pre-push quality gates, semantic versioning, and GitHub release operations.

Updated May 25, 2026
One-click install
npx skills add https://github.com/FelipeMaines/ProjetoWeb --skill aiox-devops-felipemaines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aiox-devops
Source: https://github.com/FelipeMaines/ProjetoWeb/tree/main/.claude/skills/AIOX/agents/devops
Command: npx skills add https://github.com/FelipeMaines/ProjetoWeb --skill aiox-devops-felipemaines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents broken or insecure code from reaching your main branch by enforcing mandatory quality gates, controlled versioning, and safe GitHub operations before any remote push or release happens.

Core Features & Use Cases

  • Pre-push quality gates: Runs required checks (including lint/test/typecheck/build and CodeRabbit CRITICAL issue blocking) and ensures repository cleanliness before any push.
  • Controlled GitHub push & PR automation: Manages push/PR creation under the rule that only this agent is authorized for remote git push operations.
  • CI/CD and release/version management: Sets up or updates GitHub Actions, generates changelogs, and creates versioned releases following semantic versioning and release SOP.

Quick Start

Run a full readiness check and prepare a safe release by asking: "Execute *pre-push, then create the release for the next semantic version."

Frequently Asked Questions about aiox-devops

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

FAQPage Schema
How do I enforce mandatory quality gates before a remote git push to GitHub?

You can enforce pre-push quality gates by running an automated agent that executes lint, test, typecheck, and build checks, while blocking any remote git push operations containing CRITICAL code review issues until resolved.

What is semantic versioning and how does it integrate with CI/CD release management?

Semantic versioning integrates with CI/CD release management by automating changelog generation, creating versioned releases, and updating GitHub Actions workflows to follow a structured release standard operating procedure.

Can I automate GitHub PR validation and repository cleanup without manual intervention?

Yes, you can automate GitHub PR validation and repository cleanup by delegating controlled remote operations to a dedicated agent that ensures repository cleanliness and enforces automated checks before executing actions.

Does this approach require user confirmation for irreversible git push and merge actions?

Yes, this repository governance approach requires explicit user confirmation for irreversible git push and merge actions, ensuring only the authorized agent executes remote operations after all mandatory checks pass.

What's the best way to block broken code from reaching the main branch?

The best way to block broken code from reaching the main branch is implementing a pre-push quality gate that enforces mandatory checks like CodeRabbit CRITICAL issue blocking, linting, and testing before authorizing remote pushes.

When do I need a controlled agent for GitHub remote operations?

You need a controlled agent for GitHub remote operations when your workflow requires exclusive authority for push actions, automated PR validation, and strict adherence to release management and semantic versioning standards.