ci

Generate reproducible GitHub Actions workflows for Forge projects with drift detection.

4|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/reliant-labs/forge --skill ci-reliant-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci
Source: https://github.com/reliant-labs/forge/tree/main/internal/templates/project/skills/forge/ci
Command: npx skills add https://github.com/reliant-labs/forge --skill ci-reliant-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Forge CI scaffolding solves the problem of setting up consistent, secure GitHub Actions pipelines without manual drift, fragile edits, or forgetting essential checks across linting, testing, builds, and security scanning.

Core Features & Use Cases

  • Tier-1 codegen with guardrails: Generates banner-protected Tier-1 workflows (so they’re reproducible and regenerated by forge generate) while preventing accidental hand edits from silently diverging from the declared config.
  • Clear extension paths for customization: Lets you extend CI either by using ci.extra_jobs to append jobs into the generated ci.yml, or by adding Tier-2 workflows that forge never overwrites.
  • Local verification helpers: Documents forge ci verify-generated and other helper subcommands so teams can run the same gates locally (e.g., drift detection, KCL validation, vuln scan, and migration safety).

Use case example: You want every PR to automatically run Go + frontend lint, unit tests with race mode, build artifacts (including multi-arch images when configured), vulnerability scanning, and (optionally) E2E—while still adding a team-specific docs job without forking or editing generated CI YAML by hand.

Quick Start

Run forge ci verify-generated to confirm the checked-in workflows match what forge would generate from your current forge.yaml.

Frequently Asked Questions about ci

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

FAQPage Schema
How do I generate GitHub Actions workflows that include Go tests, frontend gates, and security scanning?

Generated CI workflows are protected by banners and tracked to prevent silent divergence from your declared configuration. This ensures reproducible pipeline regeneration while stopping accidental manual edits from breaking your automated CI setup.

Can I add custom jobs to generated CI workflows without editing the YAML by hand?

Yes, you can extend CI by using the ci.extra_jobs configuration to append jobs into the generated ci.yml, or by adding parallel Tier-2 workflows. This allows custom CI customization without risking overwrites during forge generate runs.

How do I verify my checked-in GitHub Actions workflows match my current Forge configuration?

Run the forge ci verify-generated command to confirm your checked-in workflows match what Forge would generate from your current configuration. This local helper detects generator drift and validates KCL, vuln scans, and migration safety.

Does Forge CI support multi-arch image builds and optional E2E testing in GitHub Actions?

Forge CI supports building multi-arch images when configured, alongside optional E2E testing, vulnerability scanning, and environment-based deploy automation. This ensures production-grade release gates are enforced directly within your GitHub Actions pipelines.

What is the difference between Tier-1 and Tier-2 workflows in Forge CI?

Tier-1 workflows are generated and reproducible, protected by banners to prevent manual edits, while Tier-2 workflows are user-owned and never overwritten by Forge. This boundary maintains safe regeneration while allowing custom pipeline extensions.