Skip to content

mgiovani/ai-arsenal / skills/ci-local

ci-local

Verified

Run the checks a GitHub Actions workflow would run, locally, when Actions is unavailable or out of quota. Parses .github/workflows/*.yml, extracts the jobs/steps that gate merges (lint, typecheck, test, build), translates them to local commands respecting the workflow's pinned node/python versions and env, executes them sequentially, and reports a parity table of what passed locally vs. what can't be replicated (service containers, secrets, matrix dimensions) and why. Activates on "CI quota", "Actions is down/unavailable", "run CI locally", "verify like CI would", "run the pipeline on my machine", or a pre-push request to check a branch the way CI checks it. Not for generating a new workflow file (use ci-generate), not for debugging why a specific CI run failed on GitHub (use fix-bug or review-code), and not for the release/hotfix gating process itself (use gitflow), this skill only produces the local stand-in when the real thing isn't reachable.

FileKindSize
SKILL.mdskill md6.9 KB
evals/evals.jsonconfig2.9 KB
evals/trigger-eval.jsonconfig2.1 KB

evals/evals.json

View on GitHub
{
  "skill": "ci-local",
  "evals": [
    {
      "id": "quota-exhausted-node-project",
      "prompt": "GitHub Actions is out of quota again this week, can you run all the CI checks locally before I push?",
      "assertions": [
        "Reads .github/workflows/*.yml to discover the jobs/steps that gate merges before running anything",
        "Extracts and uses the workflow's pinned node/python version (e.g. from actions/setup-node or .nvmrc) rather than whatever happens to be on PATH",
        "Runs the extracted lint/test/build commands sequentially and reports pass/fail for each, with results traceable to actual command output rather than assumed",
        "Produces a parity table noting any CI steps that could not be replicated locally (services, secrets, matrix) and why",
        "Does not modify or commit the GitHub Actions workflow files themselves"
      ]
    },
    {
      "id": "targeted-job-flag",
      "prompt": "run just the lint job from .github/workflows/ci.yml locally, don't bother with the whole pipeline (--job lint)",
      "assertions": [
        "Skips globbing for other workflow files and reads only the specified workflow file",
        "Extracts and runs only the named job's steps, not every job defined in the file",
        "Reports a parity table scoped to that one job rather than the full workflow",
        "Does not run steps belonging to other jobs in the same file"
      ]
    },
    {
      "id": "ci-down-services-and-secrets",
      "prompt": "Our CI is down and the workflow uses a postgres service container plus some repo secrets for the test job — run what you can locally and tell me what you can't",
      "assertions": [
        "Identifies the services: block and secrets: usage from the workflow yaml as things needing special handling",
        "Explicitly flags the postgres service and any secret-dependent steps as not directly replicable, explaining why (no service container / missing secret value)",
        "Does not fabricate or assume a pass/fail result for a step it could not actually run",
        "Still executes and reports results for steps that don't depend on the service or the missing secrets",
        "Parity report clearly separates ran-and-passed/failed entries from skipped-can't-replicate entries"
      ]
    },
    {
      "id": "no-github-actions-refusal",
      "prompt": "verify this branch the way CI would before I push — the repo uses a .gitlab-ci.yml, there's no .github/workflows directory",
      "assertions": [
        "States plainly that this skill only handles GitHub Actions workflows and there is no .github/workflows to mirror",
        "Does not invent or guess at a generic lint/test/build sequence to run in place of a real workflow",
        "Runs no build, test, lint, or other command before reporting the refusal — no shell command is executed",
        "Stops after reporting the gap instead of attempting a partial or best-guess translation of the GitLab CI config"
      ]
    }
  ]
}
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall