ci-verify

valuecodes's avatarfrom valuecodes

Run and interpret pnpm lint, pnpm typecheck, pnpm build, and pnpm format in a Turborepo monorepo; diagnose CI-style failures; propose minimal diffs; and deliver a fix plan, files touched, and validation commands checklist. Use when verifying CI readiness or fixing lint/typecheck/build/format failures in Turborepo repositories.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 10, 2026
[CI and CD]

When & Why to Use This Skill

This Claude skill automates the verification and fixing of CI pipelines within Turborepo monorepos using pnpm. It streamlines the process of diagnosing and resolving linting, type-checking, build, and formatting errors, ensuring codebases are CI-ready by providing minimal, targeted diffs and a structured validation checklist.

Use Cases

  • Pre-push CI Readiness: Automatically run the full suite of lint, typecheck, and build commands to ensure local changes pass CI requirements before pushing to a remote repository.
  • Automated Monorepo Debugging: Quickly identify the root cause of failures in specific packages within a complex Turborepo structure and receive precise fix proposals.
  • Code Quality Maintenance: Efficiently resolve linting and formatting violations across multiple packages while adhering to repository-specific style guides and constraints.
  • TypeScript Error Resolution: Diagnose and fix complex type-checking failures at the source using safe narrowing techniques to maintain high type safety without resorting to 'any'.
nameci-verify
descriptionRun and interpret pnpm lint, pnpm typecheck, pnpm build, and pnpm format in a Turborepo monorepo; diagnose CI-style failures; propose minimal diffs; and deliver a fix plan, files touched, and validation commands checklist. Use when verifying CI readiness or fixing lint/typecheck/build/format failures in Turborepo repositories.

CI Verify

Act as a CI-focused fixer for Turborepo monorepos using pnpm. Keep diffs minimal and follow repository rules (AGENTS.md, README, and package-specific docs). CI is the source of truth.

Workflow

  1. Read repo guidance and constraints before running commands.
  2. Run the CI-aligned commands in this order at the repo root:
    • pnpm lint
    • pnpm typecheck
    • pnpm build
    • pnpm format
  3. Interpret failures. Identify the first failing package and root cause.
  4. Propose the smallest, safest change that fixes the failure. Avoid refactors and repo reshuffles.
  5. Apply the minimal diff. Do not add new dependencies unless clearly necessary. If necessary, ask first.
  6. Re-run the failing command(s) locally. Re-run the full set before final response when feasible.

Failure Diagnosis Heuristics

  • Lint failures: fix rule violations with the smallest change. Prefer local suppression only when justified.
  • Typecheck failures: fix incorrect types at the source. Avoid any. Use unknown with narrowing when needed.
  • Build failures: check config mismatches, missing exports, or invalid imports. Favor small fixes over config changes.
  • Format failures: prefer targeted formatting when possible (package-scoped or file-scoped) to avoid unrelated diffs.
  • If a command fails due to environment issues (Node/pnpm mismatch), call it out and align with repo versions.

Output Requirements

Always finish with a checklist that includes:

  • Fix plan: brief numbered steps.
  • Files touched: list of files changed (or "none").
  • Validation commands: list the commands that were run or should be run.

Keep the response concise and CI-focused. If no changes are needed, state that explicitly and still include the checklist.