CI/CD Validation & Merge Workflow

Automate pre-push validation and merge workflows for the cqlite project.

17|5|Updated Jul 14, 2025

Search Tags:#validation #merge #rust #cargo #github-actions #ci-cd

Ready to run

npx skills add https://github.com/pmcfadin/cqlite --skill ci-cd-validation-merge-workflow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: CI/CD Validation & Merge Workflow
Source: https://github.com/pmcfadin/cqlite/tree/main/.claude/skills/ci-cd-validation
Command: npx skills add https://github.com/pmcfadin/cqlite --skill ci-cd-validation-merge-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured CI/CD validation and merge workflow to reduce broken builds and release risk. It guides pre-push validation, CI monitoring, merge prerequisites, and release quality gates so teams can push code with confidence.

Core Features & Use Cases

Pre-push validation guidance: cargo fmt, clippy with zero warnings, feature gate checks, tests, and coverage gates.
CI Monitoring: guidelines for viewing and interpreting CI status, logs, and coverage reports across platforms.
Merge & Release Gates: standardized merge procedures ensuring branch up-to-date, conflicts resolved, and minimum coverage thresholds met.

Quick Start

Use this skill when preparing to push changes, validating PRs, or releasing new versions. Start by reviewing the validation checklist and merge process, then follow the steps outlined in validation-checklist.md and merge-process.md.

Frequently Asked Questions about CI/CD Validation & Merge Workflow

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

FAQPage Schema

How do I set up pre-push validation for a Rust project before merging?▼

Pre-push validation runs cargo fmt for formatting, cargo clippy with -D warnings for linting, feature-gated builds, and unit and integration tests locally before pushing. This catches issues early, ensures zero Clippy warnings, and verifies ≥90% test coverage before code reaches CI, reducing broken builds and merge conflicts.

What checks should pass in GitHub Actions CI before merging a PR?▼

GitHub Actions CI validates formatting, linting with zero warnings, minimal and full feature builds, unit and integration tests, property tests, and coverage thresholds. Merge is gated on CI status passing, ensuring consistent quality across all builds and meeting functional requirements before code integrates.

Can I automate cargo fmt and cargo clippy checks in my workflow?▼

Yes. Cargo fmt and cargo clippy with -D warnings can be automated as pre-push checks locally and enforced in GitHub Actions CI pipelines. This standardizes code style, eliminates warnings, and gates merges until all linting passes, reducing manual review overhead.

What's the best way to validate feature gates in Rust before release?▼

Feature-gated builds test code paths with different feature combinations to ensure each feature compiles and functions independently. Combined with ≥90% test coverage checks and property tests, this validates feature gates work correctly before release and prevents feature-related failures.

How do I know when a PR is ready to merge?▼

A PR is merge-ready when the branch is up-to-date, conflicts are resolved, CI status passes all checks, test coverage meets the ≥90% threshold, and merge prerequisites are confirmed. This workflow ensures standardized quality gates and reduces release risk.