aiox-devops

Enforces mandatory quality gates before GitHub remote pushes and releases.

Updated May 6, 2025

Search Tags:#ci/cd #github #release-management #quality-gates #pull-requests #code-automation #repository-governance

Ready to run

npx skills add https://github.com/rodrigo-altissimo/qiartificial --skill aiox-devops-rodrigo-altissimo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aiox-devops
Source: https://github.com/rodrigo-altissimo/qiartificial/tree/main/.claude/skills/AIOX/agents/devops
Command: npx skills add https://github.com/rodrigo-altissimo/qiartificial --skill aiox-devops-rodrigo-altissimo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill prevents broken or insecure changes from reaching your remote GitHub repository by enforcing mandatory quality gates before any push, PR, or release.

Core Features & Use Cases

Quality-gated repository operations: Runs lint, tests, typecheck, build, and CodeRabbit checks, then requires user confirmation before any remote push.
CI/CD and workflow management: Creates or updates GitHub Actions workflows for automated PR validation and pipeline behavior.
Release and version governance: Recommends semantic version bumps, generates changelogs, tags releases, and creates GitHub releases.
Repo hygiene and issue triage: Cleans stale branches and supports issue triage and resolution workflows.

Quick Start

Run the devops agent’s pre-flight quality gates with *pre-push to verify everything passes before you push to the remote repository.

Frequently Asked Questions about aiox-devops

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

FAQPage Schema

How do I enforce quality gates before pushing code to a GitHub repository?▼

You can enforce quality gates before a GitHub push by running lint, tests, typecheck, build, and CodeRabbit checks locally. The workflow requires strict pre-push validation and user confirmation before executing any remote-authority operations.

How do I automate pull request validation using GitHub Actions CI/CD?▼

Automating pull request validation with GitHub Actions involves creating or updating workflows for automated PR checks. This ensures pipeline behavior validates code changes through quality gates before any merges occur.

What is the best way to manage semantic versioning and GitHub releases?▼

Managing semantic versioning and GitHub releases is best handled by recommending version bumps, generating changelogs, tagging releases, and creating GitHub releases while maintaining repository governance and version discipline.

Why do I need pre-push validation for CI/CD workflows?▼

Pre-push validation for CI/CD workflows is needed to prevent broken or insecure changes from reaching your remote GitHub repository. It enforces mandatory quality gates including CodeRabbit CRITICAL blocking before any code automation executes.

How do I clean up stale branches and triage issues in GitHub?▼

To clean up stale branches and triage issues in GitHub, you apply repository hygiene workflows that remove inactive branches and support issue triage alongside controlled release management operations.

Can I use CodeRabbit checks to block critical issues before a GitHub release?▼

Yes, you can use CodeRabbit checks to block critical issues before a GitHub release. The workflow enforces CodeRabbit CRITICAL blocking as part of its mandatory pre-push validation and repository integrity checks.