agentleFS
Sign inStart free
roronoazoroshao369roronoazoroshao369/vibe-coding-os/skills/core/cicd-integration/SKILL.md

cicd-integration

Skill1 starsChanged 5 months agoMITView on GitHub

Integrate Vibe Coding OS quality gates into GitHub Actions for automated PR checks, reusable composite actions, and weekly quality trend reports. 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. CI/CD integration is markdown-first and pipeline-local. It does not require a daemon, hosted service, or runtime expansion. Quality…

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Secrets in logs: avoid printing credentials to workflow logs.

    line 52

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Add the PR quality gate — copy .github/workflows/vibe-quality-gate.yml into the target repository.
  2. Customize gates per project — choose preset profiles or use the reusable composite action at .github/actions/vibe-quality-action/action.yml.
  3. Configure the weekly report — copy .github/workflows/vibe-quality-report.yml to generate automated weekly trend issues.
  4. Run vibe-ci-quality-summary — generate and post a PR quality summary as a bot comment, including gate status, timing breakdown, and fix recommendations.
  5. 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free