ci cd generator

DevOps Community

Skill notes

When to Use

The skill has two operating modes — generation (the default, walks Phase 0 → 6 below) and audit (read-only review of an existing pipeline, walks Phase A0 → A5 in references/AUDIT.md).

Generation mode

A new repository (Go, Rust, or TypeScript) has no .github/workflows/ directory and the user wants CI/CD wired up An existing repository has an ad-hoc workflow that the user wants replaced with a complete, opinionated baseline The user explicitly asks for "criar CI", "gerar pipeline", "scaffold workflow", or invokes /valarmindskills:ci-cd-generator A polyglot monorepo needs per-language pipelines (run the skill once per project root)

Audit mode

The repository already has workflows authored before this skill existed and the user wants them reviewed A security incident exposed a CI weakness (compromised secret, malicious action) and the user wants the full surface checked Pre-release gate: confirm the workflows match the security level the team thinks they are running at The user explicitly asks for "auditar pipeline", "audit CI pipeline", "review existing workflow"

Do not use when

The user wants to fix or refactor a single line in an existing workflow — open the YAML directly or use @github-pr-review. For a full pipeline audit, switch to audit mode instead. The CI platform is GitLab CI, CircleCI, Buildkite, or Jenkins — this skill is GitHub Actions only The project language is not Go, Rust, or TypeScript (Node.js / Bun / Deno) The user wants to deploy infrastructure (Terraform, Pulumi, Kubernetes manifests) — pipeline ≠ infra

Prerequisites

Tool · Purpose · Install gh (GitHub CLI) · Branch protection, secrets management, dispatch · brew install gh then gh auth login actionlint · Static lint of generated YAML · brew install actionlint yamllint · Style and structural lint · brew install yamllint Language toolchain on host · Local sanity check before commit · go, cargo, bun/pnpm/npm per project

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
DevOps
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Manual integration
External API key
Not required
Operating systems
Linux · Docker
Runtime requirements
Node.js · Bun · Deno · Docker
Detected file/system behavior
  • Read-only
  • Write / modify
  • Env read
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 0 — Project Detection

Detect language, package manager, and runtime before generating anything. Run the steps in order; stop at the first conclusive match per axis. Persist as `$LANG ∈ {go, rust, typescript}`, plus per-language sub-fields (`$RUNTIME`, `$PM`, `$WORKSPACE`). The next phases branch on these values. `$LANG` · Reference to load · Default file emitted `go` · references/GO.md · `.github/workflows/ci.yml` `rust` · references/RUST.md · `.github/workflows/ci.yml`

02
Phase 1 — Collect Preferences

Ask the user only for inputs that cannot be inferred. Use one consolidated `AskUserQuestion` block, never one question per phase. Input · Required · Default · Inferable from Coverage threshold · No · `60` (per user heuristic) · None — must default Security level · No · `standard` (SAST + SCA + secret scan) · None — must default Container scan · No · `true` if `Dockerfile` exists, else `false` · `test -f Dockerfile`

03
Phase 2 — Apply User Heuristics

The pipeline emits five opinionated checks regardless of language. Each is sourced from the project owner's notes and is mandatory unless the user opts out explicitly. · Heuristic · Default behavior · Override flag 1 · Coverage gate ≥ 60% (warn ≥ 80%) · Pipeline fails below threshold · `--coverage=N` or "ignore coverage" 2 · N+1 detection · Integration tests assert max query count per request · `--no-n1`

04
Phase 3 — Wire Security Gates

Branch on the security level chosen in Phase 1. Each gate is a separate job that runs in parallel with the test job whenever possible. Gate · `minimal` · `standard` · `strict` `actionlint` self-check · ✓ · ✓ · ✓ Lint + format · ✓ · ✓ · ✓ Unit + integration tests · ✓ · ✓ · ✓

05
Phase 4 — Generate Workflow YAML

Emit the YAML in this skeleton, populated from the language-specific reference: Per-language fully populated workflows (with matrix, cache, environment variables, and the canonical job graph) live in: references/GO.md — `actions/setup-go@v5`, `go test -race -cover -covermode=atomic`, `staticcheck`, `golangci-lint`, `govulncheck`, optional `goreleaser` references/RUST.md — `actions-rust-lang/setup-rust-toolchain@v1`, `Swatinem/rust-cache@v2`, `cargo fmt --check`, `cargo clippy -D warnings`, `cargo nextest`, `cargo-llvm-cov`, `cargo-audit`, `cargo-deny`

06
Phase 5 — Validation & Dry-Run

Before reporting success, run the local checks: Each finding is added to the post-generation report. If `actionlint` reports errors, abort and emit the diff for the user instead of writing the file. The full validation matrix and the optional `gh workflow run --ref <branch> ci.yml` smoke test are in references/CHECKLIST.md.

07
Phase 6 — Deliver

Write the workflow file(s) to `.github/workflows/`. Default filename: `ci.yml`. Optional: `release.yml`, `nightly-load.yml`. Write `.github/dependabot.yml` if Phase 1 enabled it. Emit the generation report (see Output format). Surface the suggested branch protection rules — do not apply them automatically. Provide the `gh` command the user can run. Hand off to `@github-commit` to commit the new files; do not commit unless the user explicitly approves.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.