Skip to main content

Orchestrate:CI Expansion Design

Date: 2026-02-24 Status: Approved

Problem

The orchestrate:ci skill generates basic lint/test/build workflows but the rossoctl/rossoctl main repo has evolved a comprehensive CI standard with 14 workflows covering security scanning, dependency review, action pinning, least-privilege permissions, and more. Satellite repos in the rossoctl org score 0.5-3.5 out of 5 on CI maturity. The orchestrate skills need to encode the full standard.

Analysis

Rossoctl Org CI Maturity

RepoScoreKey Gaps
rossoctl (main)4/5No unit tests in CI, no CODEOWNERS, dependabot Actions-only
rossoctl-operator3.5/5Nested workflow structure, no security scanning
plugins-adapter3/5No dependabot, no security scanning
.github3/5Org config, reusable workflows
cortex2/5Tests commented out, no security scanning
agent-examples1.5/5Tests commented out, no pre-commit
agentic-control-plane1/5No CI at all
workload-harness0.5/5No CI at all

Org-Wide Gaps

  • No repo has CODEOWNERS
  • No satellite repo has security scanning
  • Only 2/7 satellites run tests in CI
  • Dependabot never covers application dependencies
  • No coverage reporting anywhere

Design

Skill Restructuring

orchestrate:ci expands from basic lint/test/build to comprehensive CI blueprint:

  • Tier 1 (Universal): ci.yml, security-scans.yml, dependabot.yml (all ecosystems), scorecard, action pinning check
  • Tier 2 (Conditional): Container builds, multi-arch, stale/PR-verifier (org reusable workflows)
  • Tier 3 (Advanced Optional): Comment-triggered E2E, post-merge security, TOCTOU protection

orchestrate:security narrows to governance-only: CODEOWNERS, SECURITY.md, CONTRIBUTING.md, LICENSE, .gitignore audit, branch protection docs.

orchestrate:scan gains CI maturity detection: security scanning coverage, dependabot ecosystem completeness, action pinning compliance, permissions model, container build presence.

Output Style

Hybrid: structured guidance for architecture decisions + verbatim YAML snippets for security-critical patterns (permissions blocks, Trivy config, dependabot multi-ecosystem, CodeQL setup, dependency review with license deny list).

Size Estimates

  • orchestrate:ci: ~350-400 lines (up from 157)
  • orchestrate:scan: ~220 lines (up from 180)
  • orchestrate:security: ~140 lines (down from 173)