For platform & DevEx teams with many repos
v0.1 · pre-release · not yet on npm

CDK for GitHub Actions.

Ship a CI change to 80 repos as one release. Write workflows as TypeScript, publish them as an npm package, and let Renovate deliver every change, breaking ones included, as a migrated, SHA-pinned PR in each repo. Stop using it and the committed YAML keeps working.

A single release of @acme/wf-node-ci 2.0.0 fans out into pull requests in acme/api, acme/web, acme/billing, acme/auth and acme/search. Each PR changes the config, the generated ci.yml and the lockfile, and passes cikick check.

The problem

Your CI is already a fleet.
It just isn't managed like one.

Every repo got its workflow by copying the last one. Then each copy lived its own life.

Nine repos, one intent, five spellings

Nobody decided this. It's what copy-paste does over two years. Updating means opening nine PRs by hand, so it doesn't happen.

A new secret value reached 2 of 9 repos

Distributing the new value is a ticket per repo, tracked in someone's spreadsheet. Seven repos keep running on the key you meant to retire.

A moving tag is a supply-chain hole

This is not hypothetical: in March 2025 the widely usedtj-actions/changed-files action was compromised and its existing version tags were re-pointed at a commit that printed secrets into workflow logs (CVE-2025-30066). Workflows pinned to a full commit SHA kept running the commit they had been reviewed against. The fix is old advice: pin by SHA. cikick does it at every synth and records it in a lockfile; cikick lock --refresh moves the pins forward.

The idea

Constructs in. Pinned YAML out.

Like AWS CDK, but for workflows. You describe CI as typed TypeScript objects; cikick synth walks the construct tree and writes plain .github/workflows/*.yml, resolves every action to a commit SHA, and records it incikick.lock.json. The generated YAML runs without cikick; cikick check is an optional CI gate.

1 You write cikick.config.ts

cikick.config.ts
import { NodeCi } from '@acme/wf-node-ci';import { applyBaseline } from '@cikick/policies'; export default (app) => {  new NodeCi(app, 'node', {    nodeVersion: 22,    packageManager: 'pnpm',  });  applyBaseline(app); // policies};

2 YAML and a lockfile

.github/workflows/ci.yml
# Generated by cikick — do not edit. Run `npx cikick synth`.name: CIon: # push to main, pull_requestpermissions:  contents: readjobs:  build:    timeout-minutes: 30    steps:      - uses: actions/checkout@11d5960a3267… # v4      - uses: pnpm/action-setup@b906affcce14… # v4      - uses: actions/setup-node@49933ea5288c… # v4      # …
cikick.lock.json
{  "actions": {    "actions/checkout@v4": {      "sha": "11d5960a3267…",      "resolvedAt": "2026-11-22T10:36Z"    }, …  },  "packages": { "@acme/wf-node-ci": "2.0.0" }}

A cikick.config.ts file that instantiates a NodeCi construct is synthesized (via a construct tree) and rendered to ci.yml where every action is pinned to a commit SHA with a version comment, plus a cikick.lock.json recording each resolved SHA.

In between: synth builds a construct tree (App → NodeCi → Workflow → Jobs, plus managed files like renovate.json). Aspects visit every node to add permissions or timeouts, or rewrite deprecated actions.

  • Typed props instead of YAML anchors and string templating. A breaking change fails at compile time.
  • Distributed as npm packages. Your platform team ships @acme/wf-node-ci; repos depend on it like any library.
  • Every repo can still deviate through props, escape hatches (addOverride) and aspects. No fork needed.
  • Pins move forward on purpose. They are resolved at synth with git ls-remote and recorded in the lockfile. cikick lock --refresh re-resolves them; run it on a schedule (e.g. a weekly workflow) and review the resulting diff.
  • Reviewable. Generated YAML is committed, and cikick check fails CI if it drifts from the config.

The update loop

A breaking change becomes a pull request, not a migration project.

The platform team releases a new major. Every repo gets a PR that already contains the migration. Humans review a diff; nobody hunts for a Slack thread.

  1. shared package repo

    Publish @acme/wf-node-ci 2.0.0

    A breaking rename ships with a codemod. One release, written once by the platform team.

  2. every consumer repo

    Renovate opens a PR

    It bumps the dependency like any other, and runs npx cikick update as a post-upgrade task.

  3. in the PR branch

    cikick update runs the migration

    Migrations between the locked and installed versions run in order, editing cikick.config.ts with ts-morph.

    $ npx cikick update@acme/wf-node-ci: 1.4.0 -> 2.0.0migrate @acme/wf-node-ci@2.0.0: Rename NodeCi prop `node` to `nodeVersion`…renamed 1 `node` prop(s) to `nodeVersion`deleted legacy .github/workflows/node.ymlwrote .github/workflows/ci.ymlwrote cikick.lock.json
  4. in the PR branch

    Synth, then the PR shows the diff

    The config edit and the file changes land in one PR, so a reviewer sees exactly what changed before anything merges.

    cikick.config.ts-  new NodeCi(app, 'node', { node: 22 })+  new NodeCi(app, 'node', { nodeVersion: 22 }).github/workflows/node.yml-  (legacy generated file removed).github/workflows/ci.yml-        node-version: 20+        node-version: 22cikick.lock.json-  "packages": { "@acme/wf-node-ci": "1.4.0" }+  "packages": { "@acme/wf-node-ci": "2.0.0" }
  5. in CI

    cikick check goes green

    Generated files match the config, the lock covers every action, and policy checks pass. Merge.

    check passed npx cikick check exits 0

If a migration throws, cikick update stops with the error and exits non-zero. It does not synth or update the lockfile, so cikick check fails and the PR stays red. Edits the earlier migrations made are left in the working tree for you to inspect. Once cikick check is green, Renovate automerge is an option you can enable in your Renovate config.

Without a codemod you can still ship a check with enforceAfter: a warning today, a CI error after a date you choose.

Fleet

One command across the repos you chose. Nothing else.

cikick-fleet works from a fleet.json allowlist that you select. It never means "everything in the org". Inventory, settings drift, secret age and rotation all run against that list. Anything outside it is refused.

$ cikick-fleet secrets report --group publishersstale           acme/api  NPM_TOKEN  212d (max 90)stale           acme/web  NPM_TOKEN  212d (max 90)… 7 more$ cikick-fleet secrets rotate NPM_TOKEN --group publishers \    --value-from-env NEW_NPM_TOKENDry run: nothing written. Re-run with --yes to rotate.$ … --yesupdated  acme/api NPM_TOKENupdated  acme/web NPM_TOKEN… 7 more

A terminal: a secrets report lists stale NPM_TOKEN secrets, then a dry-run and a confirmed rotate push a new value to each selected repository.

cikick-fleet pushes a value you provide to every selected repo or environment and reports its age. Minting and revoking at the provider (npm, cloud) is still yours.

  • Explicit selection. cikick-fleet select lists repos you administer; you pick. Commands refuse any repo outside fleet.json.
  • Dry-run by default. settings apply and secrets rotate write nothing without --yes.
  • Values never printed. Read from an env var or stdin, sealed with libsodium to each repo's public key, then PUT to GitHub.
  • Access it needs. A token in GITHUB_TOKEN or GH_TOKEN, and admin on each selected repo (select only lists repos where permissions.admin is true).
  • Rulesets are report-only. settings apply writes repo settings, but rulesets are only reported as drift, never changed.
  • Fleet-wide visibility. cikick-fleet inventory and report --html show which repos run which shared-package version, and how many action references are unpinned.
  • Why not org-level secrets? Org secrets share one value across repos and have no age policy. Use them when one value for all selected repos is fine. cikick-fleet covers per-repo and environment-scoped secrets, repos across several owners, and tells you how old each value is.
  • Policies, not vibes. secretPolicies give each secret a max age; secrets report exits non-zero when something is stale or missing.

Why not just…

Honest comparisons.

Most of these are better than cikick at the thing they do. cikick earns its place only when you need shared, versioned, migratable workflows across many repos.

How cikick compares with other ways to share GitHub Actions workflows across repositories
CapabilitycikickReusable workflowsComposite actionsOrg rulesets / required workflowsOrg-level secretsRenovate / DependabotFile sync / multi-repo PR toolsprojengithub-workflows-ktzizmor / actionlint
Shared across reposYes: npm packagesYes: nativePartial: steps onlyYes: enforced centrallyYesNo: per-repo copiesPartial: copy files outYes: npm packagesPartial: Kotlin scripts/libsNot applicable: analysis only
Per-repo customisationYes: props, addOverride, aspectsPartial: inputs, secrets, job-level settings; not stepsPartial: inputs onlyNo: same workflow everywherePartial: select repos; one valueNot applicablePartial: via templating (unverified)Yes: escape hatchesYes: codeNot applicable
Breaking-change migrationsYes: versioned codemods via cikick updateNoNoNoNot applicableNo: bumps stringsPartial: scripted, not versionedPartial: re-synth; breaks surface as compile errors, no shipped codemods (unverified)No: (unverified)No
SHA pinningYes: at synth (refresh is manual: lock --refresh)Partial: caller pins @sha by handPartial: by handPartial: by hand in the one fileNot applicableYes: Renovate digest pinning; Dependabot bumps SHAs (pinning on its own: unverified)NoUnverified: unverifiedUnverified: unverifiedPartial: flags unpinned uses (zizmor)
LockfileYes: cikick.lock.jsonNoNoNoNot applicableNoNoUnverified: unverifiedNo: (unverified)No
Secret distribution / fleet opsPartial: age report + push a value to selected repos; no mint/revokeNoNoNoPartial: one value, many repos; no age policyNoNoNoNoNo
Static analysisPartial: 5 stock checks + custom ChecksNoNoNoNot applicableNoNoNoYes: typed action inputsYes: deeper than cikick
No build stepNo: synth stepYesYesYesYesYesYesNo: synth stepNo: script stepYes
MaturityNo: 0.1, unpublishedYes: GAYes: GAYes: plan availability: unverifiedYesYesPartial: variesYes: widely usedPartial: active, nicheYes
  • yes
  • partial
  • no
  • unverified
  • not applicable

Third-party cells reflect our reading of their docs as of Nov 2026; cells marked ? or "unverified" are ones we have not confirmed. Corrections welcome.

Notes: use it when…

  • Reusable workflows. Use them when the pipeline is the same and a few inputs differ; native, no tooling, and the simplest thing that works. Callers can pass inputs, secrets and job-level settings (permissions, strategy, concurrency, if, needs) but cannot add or change a step inside the called jobs. Each caller pins its own @ref and needs a bump PR; orgs that use @main skip those PRs, at the cost of unreviewed changes going live in every repo at once. A cikick Job can uses: a reusable workflow and cikick pins its ref.
  • Composite actions. Use them to bundle steps (setup, build, deploy) behind one uses:. They cannot define jobs, triggers, permissions or needs, so the workflow skeleton is still copy-pasted. Keep them; cikick generates the skeleton that calls them.
  • Org rulesets / required workflows. Use them when you need central enforcement with no per-repo PR and every repo should run the same workflow. They do not offer per-repo customisation or migrations. Check plan availability for your org.
  • Workflow templates. Starter workflows in an org's .github repo help new repos begin from a good default. They are copied once, so later changes do not reach existing repos.
  • Org-level secrets. Use them when one value should reach many repos in an org; scope it to selected repos. Environment-scoped secrets, per-repo values and repos outside one org are where it stops. cikick-fleet pushes a value you provide and reports age; minting and revoking at the provider is still yours.
  • Renovate / Dependabot. Use them if your problem is only stale action versions; Renovate can pin digests (helpers:pinGitHubActionDigests). They bump strings and do not know your shared workflow renamed an input. cikick uses Renovate as the delivery truck, then runs cikick update.
  • File sync / multi-repo PR tools. repo-file-sync-action, multi-gitter and turbolift copy files or script changes across repos and open PRs. As far as we can tell they do not version migrations or pin actions, but they need no build step and suit a one-off change.
  • projen. The closest relative: TypeScript-defined, synthesized config with GitHub workflow support, far broader and more mature. Pick one generator per repo; if projen already works for you, you may not need cikick. As far as we know it ships no migrations inside shared packages.
  • github-workflows-kt. A Kotlin DSL with typed action bindings, so with: inputs are checked at compile time. A real advantage in a Kotlin shop that cikick lacks. An alternative, not a companion; choose by language.
  • zizmor / actionlint. Dedicated static analysis, deeper than cikick's stock checks. They find problems but do not generate or update workflows. Run them on cikick's generated YAML too.

cikick is a good fit when

  • You have roughly 10+ repos with similar pipelines, and a team that can own a shared package.
  • Breaking changes to shared CI happen, and you want them as migrations, not announcements.
  • Auditors or security want every action pinned and every secret on a rotation clock.

It is probably the wrong call when

  • You have a handful of repos. Reusable workflows plus Renovate are less machinery.
  • Nobody wants a build step between editing CI and running it. cikick adds one.
  • Many repos are Go, Python or Java. Every consumer repo needs Node and a package.json with cikick as a dev dependency.
  • You need a mature, battle-tested ecosystem today. cikick is version 0.1.

Quickstart

Build it from source, check a real consumer.

This clones the cikick monorepo, builds every package from source, then runs cikick check onexamples/consumer: a repo that uses a shared package, with its generated ci.yml andcikick.lock.json committed. The check verifies they match the config, offline.

cikick is pre-release (0.1.0) and its packages are not yet published to a registry, so there is no npm install yet. The guide covers wiring it into your own repo.

terminal
git clone https://github.com/cikick/cikick && cd cikick
# the 2nd install links the built bins
pnpm install && pnpm build && pnpm install
cd examples/consumer && pnpm exec cikick check