swarmxq-ci-release-architect

Configures GitHub Actions quality gates, pnpm caching, and release checklists for SwarmXQ CI pipelines.

1|Updated Aug 25, 2026
One-click install
npx skills add https://github.com/sabiscore/swarmxq --skill swarmxq-ci-release-architect-sabiscore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swarmxq-ci-release-architect
Source: https://github.com/sabiscore/swarmxq/tree/main/.ai/skills/swarmxq-ci-release-architect
Command: npx skills add https://github.com/sabiscore/swarmxq --skill swarmxq-ci-release-architect-sabiscore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintaining a consistent CI/CD pipeline for the SwarmXQ monorepo requires enforcing an 8-gate quality checklist (TypeScript compilation, vitest suites, regression scripts, next build, and invariant checks) across every pull request, and misconfigured gates let console.* drift, type errors, and dependency inconsistencies reach the main branch. ## Core Features & Use Cases - 8-Gate Quality Pipeline: Defines the exact execution order for tsc --noEmit across three packages, two vitest suites, five offline regression scripts, next build, and invariant checks (console.* zero-tolerance, process.env coverage, TONE_RULES completeness). - GitHub Actions Configuration: Provides a production-ready ci.yml with pnpm store caching keyed on pnpm-lock.yaml, Node 20 setup, frozen-lockfile installs, and job timeouts. - Offline CI Protocol: Documents which gates run without Ollama or Redis and how to mark skipped gates explicitly with if: false conditions. - Release Governance: Standardizes CHANGELOG.md entry format, semantic release tagging (vMAJOR.MINOR.PATCH), and branch protection requirements for main. - Use Case: When a pull request fails Gate 8a because a console.log slipped into apps/swarmx-api/src/services, use this Skill to diagnose the invariant violation, fix the offending file, and verify the grep check returns zero hits before merging. ## Quick Start Ask the AI to review the current .github/workflows/ci.yml against the 8-gate checklist and identify any missing or misordered quality gates.

Frequently Asked Questions about swarmxq-ci-release-architect

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

FAQPage Schema
How do I set up a GitHub Actions quality gate for a pnpm monorepo?

Use pnpm/action-setup with actions/setup-node configured with cache: pnpm, then run pnpm install --frozen-lockfile followed by per-package gates like pnpm -F <package> tsc --noEmit and vitest run. Order gates sequentially so type errors surface before test and build stages.

How do I cache the pnpm store in GitHub Actions?

Enable caching through the cache: pnpm option in actions/setup-node, or use actions/cache with the pnpm store path and a key hashed from pnpm-lock.yaml. Including the lock file in the key invalidates stale caches when dependencies change and prevents intermittent CI failures.

Can CI regression tests run without Ollama or Redis?

Yes, the five regression scripts (adaptive-timeout, video-pipeline, eviction-metrics, system-health, reasoning-sanitizer) are pure offline logic tests requiring no Ollama or Redis. Gates requiring live services must be explicitly skipped with an if: false condition and a comment, never marked as passing.

Why does my CI pipeline fail on console.log statements?

The console.* invariant check runs grep -rn 'console\.' over the API services and routes directories and fails the build on any hit. Remove or replace all console calls in those directories; the zero-tolerance rule prevents log drift from reaching the main branch.

What branch protection settings should main have for CI gating?

Require the quality gate status check to pass, block direct pushes and force pushes, require branches to be up to date, and include administrators in the restrictions. Add required approvals once the team has two or more members.