Cicd integration

Skill roronoazoroshao369/vibe-coding-os/skills/core/cicd-integration

Vibe Coding OS — Claude/Codex/Cursor skill framework with 139 skills, 111 commands, 95 templates, 22 tracked sources, 28/28 validation gates PASS. Quality Shield, Engineering Discipline Pack, plugin marketplace.

Install

npx -y skills add roronoazoroshao369/vibe-coding-os --skill cicd-integration

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.9 KB, 804 tokens by cl100k_base, as published. Nobody here has run it

CI/CD Integration

Integrate Vibe Coding OS quality gates into GitHub Actions for automated PR checks, reusable composite actions, and weekly quality trend reports.

Purpose

Automate quality verification in CI/CD pipelines so every pull request runs validate:all, emits quality telemetry, and surfaces results as PR comments and annotations. This skill covers the PR quality gate workflow, the reusable composite action, and the weekly quality report workflow.

When to use

You want every PR to automatically run repository validation, injection scan, secret scan, and quality engine gates.
You want a reusable GitHub composite action that other repos can reference to run Vibe Coding OS quality gates.
You want a weekly quality report that opens a GitHub issue with session metrics and trend data.
You want vibe-ci-quality-summary to post or update a PR comment with structured quality results.

Inputs

GitHub repository with Vibe Coding OS installed and npm run validate:all passing locally.
GitHub Actions enabled with workflow write permission for checks and PR comments.
Optional: quality engine profile (lean, standard, heavy) for gate selection.
Optional: telemetry data under docs/metrics/ for weekly report generation.

Workflow

Add the PR quality gate — copy .github/workflows/vibe-quality-gate.yml into the target repository.
Customize gates per project — choose preset profiles or use the reusable composite action at .github/actions/vibe-quality-action/action.yml.
Configure the weekly report — copy .github/workflows/vibe-quality-report.yml to generate automated weekly trend issues.
Run vibe-ci-quality-summary — generate and post a PR quality summary as a bot comment, including gate status, timing breakdown, and fix recommendations.
Review annotations — failed gates emit GitHub annotations inline in the changed file diff.

Outputs

PR quality gate workflow that runs validate:all and uploads a quality report artifact.
Reusable composite action that other repos can reference with uses:.
Weekly quality report opened as a GitHub issue.
PR comment quality summary rendered by vibe-ci-quality-summary.

Failure modes

Missing dependencies: workflow fails because npm ci cannot resolve packages — ensure package-lock.json is committed.
Secrets in logs: avoid printing credentials to workflow logs; the built-in secret scan is intentionally included.
False-positive secret scan: review detector patterns in scripts/validate-secrets.mjs and add exclusions where appropriate.
Report artifact missing: confirm scripts/quality-engine.mjs and scripts/quality-engine-report.mjs exist; the workflow includes a fallback summary.

Verification checklist

.github/workflows/vibe-quality-gate.yml runs npm run validate:all and npm run validate:secrets.
Quality report is uploaded as a workflow artifact on every run.
PR comment is posted or updated with quality summary.
Weekly report workflow opens a GitHub issue with trend data.
Reusable action passes inputs and produces valid outputs.
No credentials, tokens, or secrets appear in workflow logs.
All gates pass before merge (validate:all 26/26).

Related assets

Command: commands/vibe-ci-quality-summary.md
Guide: docs/cicd-integration-guide.md
Workflow: .github/workflows/vibe-quality-gate.yml
Workflow: .github/workflows/vibe-quality-report.yml
Action: .github/actions/vibe-quality-action/action.yml

Notes

CI/CD integration is markdown-first and pipeline-local. It does not require a daemon, hosted service, or runtime expansion. Quality gates and report generation are composable and referenceable from any GitHub Actions workflow.

Gives 0 of the 12 instructions most ci cd skills give in 804 tokens

Counted across 392 of the 394 authors here whose files we hold, read 2026-08-06

pin third-party actions to full commit SHAsin 33 of 392
cache dependencies appropriatelyin 24 of 392, across 12 files
optimize pipelines exceeding ten minutesin 20 of 392, across 6 files
enforce all quality gates before mergein 20 of 392, across 7 files
Configure branch protection rulesin 19 of 392, across 5 files
use environments for deployment trackingin 19 of 392, across 7 files
implement manual gates for productionin 19 of 392, across 7 files
implement security scanningin 18 of 392, across 5 files
fix failing code instead of disabling checksin 18 of 392, across 4 files
use CI/CD variables for secretsin 18 of 392, across 6 files
move checks upstream in the pipelinein 17 of 392, across 3 files
use specific image tagsin 17 of 392, across 5 files

Said here and by no other author read

choose preset profiles or reusable action
copy weekly quality report workflow file
generate and post PR quality summary comment
review failed gate inline annotations
ensure package lock file is committed
add secret scan exclusions for false positives

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.