swarmxq-ci-release-architect

Configures GitHub Actions quality gates, regression scripts, and release checklists for SwarmXQ CI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents broken TypeScript contracts, console.* drift, and quality regressions from reaching the main branch by enforcing a deterministic 8-gate CI pipeline and release protocol. ## Core Features & Use Cases - 8-Gate Quality Pipeline: Sequences tsc checks across three packages, vitest suites, five offline regression scripts, next build, and invariant checks (console.* zero-tolerance, env schema coverage, TONE_RULES completeness). - GitHub Actions Configuration: Provides a production ci.yml with pnpm store caching keyed on pnpm-lock.yaml, frozen-lockfile installs, job timeouts, and offline Ollama stub guidance. - Release Governance: Defines CHANGELOG entry format, semantic release tagging, and branch protection requirements for main. - Use Case: When a PR to main fails Gate 8a because a console.log slipped into apps/swarmx-api/src/services, use this Skill to diagnose the violation, fix it, and verify the invariant check returns zero hits. ## Quick Start Ask the AI to audit .github/workflows/ci.yml against the 8-gate release checklist and report any missing or misordered 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?

Define a single job that runs pnpm install --frozen-lockfile, then sequences tsc --noEmit per package, vitest run per app, regression scripts via npx tsx, and next build. Cache the pnpm store with a key hashing pnpm-lock.yaml to avoid stale dependency installs.

How do I enforce a zero console.log policy in CI?

Add a grep-based invariant step that counts console.* hits in your services and routes directories and exits 1 if any are found. This makes the check blocking so violations fail the pipeline before merge.

Can regression scripts run in CI 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. Tests needing live services must be explicitly skipped with an if: false condition and a comment, never marked as passing.

Why does pnpm caching cause intermittent CI failures?

Failures occur when the cache key omits pnpm-lock.yaml, so dependency changes reuse a stale store. Include hashFiles('**/pnpm-lock.yaml') in the cache key with a runner-os restore-keys fallback.

What branch protection settings should main have?

Require the quality gate status check, block direct and force pushes, require up-to-date branches, and include administrators. Add one required approval with stale review dismissal once the team has two or more members.