mav-bp-cicd

Enforce CI/CD governance and quality gates across GitHub Actions, GitLab CI, and Azure DevOps.

10|2|Updated Mar 3, 2026

Search Tags:#deployment #pipeline #stages #ci-cd #quality-gates #secrets-management #environment-promotion

One-click install

npx skills add https://github.com/thermiteau/maverick --skill mav-bp-cicd

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: mav-bp-cicd
Source: https://github.com/thermiteau/maverick/tree/main/skills/mav-bp-cicd
Command: npx skills add https://github.com/thermiteau/maverick --skill mav-bp-cicd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Platform-agnostic CI/CD conventions to enforce quality, security, and maintainability across pipelines.

Core Features & Use Cases

Stage-based guidance applicable to any CI/CD platform (Validate, Build, Test, Package, Deploy)
Mandatory gates (lint, type check, unit tests, security checks) and safe promotion rules
Secrets management and environment promotion patterns to prevent credential exposure
Governance, auditing, and cross-team collaboration support for standard workflows
Use Case: Apply these standards to ensure consistent pipelines across GitHub Actions, GitLab CI, and Azure DevOps

Quick Start

Configure the CI/CD pipelines in your repository by applying these standards and enabling the guardrails for immediate enforcement.

Frequently Asked Questions about mav-bp-cicd

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

FAQPage Schema

How do I enforce consistent CI/CD pipelines across GitHub Actions, GitLab CI, and Azure DevOps?▼

CI/CD pipeline consistency across GitHub Actions, GitLab CI, and Azure DevOps is enforced by applying platform-agnostic conventions for stage order, mandatory quality gates, and safe environment promotion rules.

What quality gates should a CI/CD pipeline have before promoting artifacts?▼

CI/CD pipelines should enforce mandatory quality gates including lint, type checks, unit tests, and security checks before safely promoting artifacts from development through production environments.

How does secrets management work during environment promotion in CI/CD?▼

Secrets management during environment promotion prevents credential exposure by enforcing standardized patterns for handling secrets across pipeline stages from development to production.

What is the correct stage order for a safe CI/CD pipeline?▼

A safe CI/CD pipeline follows a stage-based order of Validate, Build, Test, Package, and Deploy to ensure consistent governance and artifact integrity across environments.

Can I apply cross-platform CI/CD governance to existing pipelines without rewriting them?▼

Cross-platform CI/CD governance can be applied to existing pipelines by configuring repository standards and enabling guardrails to enforce stage order, quality gates, and audit-friendly promotion rules.

Why do I need audit-friendly promotion rules in CI/CD pipelines?▼

Audit-friendly promotion rules in CI/CD pipelines are needed to support governance, ensure cross-team collaboration, and maintain secure artifact retention during environment promotion.