Omniscio

Customize the Dev Pipeline

- Use it as it comes. With no settings at all, every repo gets the full Dev Pipeline. - Start from a preset. pack.mjs init --preset lean (or standard, strict, docs) writes a ready-made team pipeline into your repo. - Shape everything else with the files below. Settings committed to the repo apply to the whole team. Settings in your home folder apply to you alone.

On this page

Where each setting lives

What you want to change Where Applies to
Which steps run, their names, order and stops .claude/dev-pipeline/phases.json (the pack), or Dev Pipeline → Setup → All settings → Pipeline pack (this repo) Everyone in the repo
A step that must pass commands, or runs only for certain files custom[].run / custom[].when in phases.json, or the same panel card Everyone in the repo
A shared pipeline for many repos extends in phases.json, pointing at a company pack Every repo that extends it
Which builder model writes the code models.build in phases.json, or Setup → build model Everyone / you
House rules checked before build and before merge .claude/dev-pipeline/standards.md Everyone in the repo
What counts as a tiny change for the Quick Lane .claude/dev-pipeline/quick-lane.json Everyone in the repo
The repo's test, lint, typecheck and build commands, base branch pipeline block in .claude/foundations.json Everyone in the repo
Your own overrides of those commands .claude/foundations.local.json (not committed) You, on this computer
Your own extra steps ~/.claude/dev-pipeline/phases.json (turn on custom phases in Setup) You, in every repo
Your own standing instructions for a step ~/.claude/dev-pipeline/custom/phase-1.md … phase-6.md, all-phases.md You, in every repo
Which stops clear themselves (your stops, see Which steps wait for you), AI review, Scout, Step Back Dev Pipeline panel → Setup You, in every repo

Recipes

Start a repo from a preset

node ~/.claude/skills/dev-pipeline/scripts/pack.mjs presets
node ~/.claude/skills/dev-pipeline/scripts/pack.mjs init --preset lean
node ~/.claude/skills/dev-pipeline/scripts/pack.mjs schema

The last line turns on autocomplete for phases.json in your editor. Commit the folder it wrote.

Rename, remove or un-stop a step

{
  "version": 2,
  "phases": [
    { "id": "build", "title": "Implement", "emoji": "🛠️" },
    { "id": "elegance", "enabled": false },
    { "id": "docs", "gate": false }
  ]
}

Add a step that must pass a command

{
  "version": 2,
  "custom": [
    { "id": "e2e", "title": "End-to-end tests", "insertAfter": "build", "run": ["npm run test:e2e"] }
  ]
}

The first failing command stops the step and shows you what failed. Command steps must come after Build.

Run a step only when certain files change

{
  "version": 2,
  "custom": [
    {
      "id": "migration-review",
      "title": "Migration review",
      "insertAfter": "build",
      "when": { "paths": ["db/migrations/**", "**/*.sql"] },
      "instructions": "Check every new migration is reversible and safe to run twice."
    }
  ]
}

When the branch touches no matching file, the step skips itself and the run carries on.

Share one pipeline across many repos

Put the pack in its own git repository, then in each project:

{ "version": 2, "extends": ["https://github.com/your-team/pipeline-pack#<40-character commit id>"] }

pack.mjs update moves the pin to the pack's newest commit. A company pack can mark a step "locked": true so no project below it can remove or loosen it.

Set the house rules

Write .claude/dev-pipeline/standards.md with two sections, ## Before you build and ## Before you merge. The Standards Check and the Standards Audit read them on every run. With no file, a general set of senior-engineering rules is used.

Tell the pipeline how your repo is tested

{
  "pipeline": {
    "profileVersion": 1,
    "checks": {
      "test": { "command": "pytest", "source": "user" },
      "lint": { "command": "ruff check .", "source": "user" }
    },
    "baseBranch": "main"
  }
}

That block goes in .claude/foundations.json. Anything you leave out is detected from the repo (npm, Python, Cargo, Go, Make, Maven, Gradle, Ruby and PHP projects are recognized).

Pick how your team's work lands

Every way of landing work stays available, and your team picks one in the pipeline block of .claude/foundations.json:

{ "pipeline": { "land": { "strategy": "pull-request" } } }
  • local-merge — merge into your own main copy; with a mint command, the lander does it.
  • pull-request — push the run's branch and open a draft pull request.
  • tag — stamp the branch, then make the same checked local merge.
  • command — run your own finish, named in land.command.

Which road one computer takes is that computer's setting. In Omniscio a computer whose lander is off, or that isn't the main computer, finishes with a pull request.

Widen or narrow the Quick Lane

{ "maxLines": 30, "maxFiles": 3, "offLimits": ["src/payments/**"] }

That goes in .claude/dev-pipeline/quick-lane.json. The limits are read from the base branch, so a branch can't loosen its own bar.

Off switches

Each of these environment variables turns one part off, on that computer:

  • DEV_PIPELINE_DISABLE_PACKS=1 — ignore every pack change and company pack.
  • DEV_PIPELINE_DISABLE_BUNDLED_STANDARDS=1 — no Standards Check or Standards Audit.
  • DEV_PIPELINE_DISABLE_BUNDLED_SCOUT=1 — no Scout Report.
  • DEV_PIPELINE_DISABLE_BUNDLED_AI_REVIEW=1 — no AI Code Review steps.
  • DEV_PIPELINE_DISABLE_STEP_BACK=1 — no Step Back.

Good to know

  • Check before you commit. pack.mjs check lists every problem with your pack, and pack.mjs show prints the steps the pipeline will run, including every command and file pattern.
  • Commands in a pack run on every teammate's computer. Review a pack change the way you review code.
  • What your own pipeline file may change is the repo's call. A team pack can let a developer's personal file only tighten steps (the default), also remove and rename unlocked ones, or change no steps at all — it only matters if you switched on your own custom phases. See Who may change the pipeline on their own machine.
  • A run keeps the pipeline it started with. Editing a pack mid-run doesn't change a run already under way.
  • Settings that no longer exist. standards.preset, review.gates, ui.harness and the phases block of foundations.json were accepted but never acted on, and they are gone. The block now carries only settings something reads, so nothing you write there is silently ignored. A repo that still writes one keeps its whole profile — the Add-a-repo card, and the run's own report, name each retired setting and where it lives now: the house-rules file for standards, phases.json for per-step models and instructions, and the review steps in this tab.

Last verified 2026-11-13