Local CLI for polyrepo workspaces

Polyrepo Workspace Kit

A thin coordination layer for local polyrepo workspaces, cross-repo validation, and generated coding-agent guidance.

View on GitHub Install docs Technical spec 
curl -fsSL https://raw.githubusercontent.com/johnkil/polyrepo-workspace-kit/main/install.sh | sh
$ wkit scenario run schema-rollout
pinning repos from local bindings
ok shared-schema test
ok app-web test
report local/reports/schema-rollout/20260419T121000Z.yaml

Canonical state

workspace:
  repos:
    - app-web
    - shared-schema
context:
  id: schema-rollout
change:
  kind: contract

Derived guidance

AGENTS.md
CLAUDE.md
.agents/skills/*
.github/copilot-instructions.md

Built for multi-repo work that still needs local truth.

The project helps humans and coding agents share one explicit workspace model without pretending every repository belongs in a monorepo or in a hosted portal.

Coordinate repositories

Register repos, relationships, contexts, and active changes in workspace manifests that are readable and reviewable.

Pin validation scenarios

Capture repo-local checks as scenario snapshots and write local evidence reports for handoff and review.

Generate agent guidance

Install derived repo-scope guidance for portable agents, Codex, OpenCode, Copilot, and Claude from canonical workspace sources.

A small model on purpose.

Canonical truth lives in manifests and guidance sources. Adapter files are generated outputs, not a second source of truth.

Workspace

Repos, contexts, relationships, rules, and live changes.

Scenario

Reviewable local validation snapshots with explicit repo pins.

Binding

Machine-local checkout paths kept out of shared canonical state.

Adapter

Derived guidance files installed into real tool discovery paths.

Read the source documents.

The landing page is only a doorway. The repository remains the product source of truth.

Technical specification Canonical model, file formats, CLI contracts, and safety rules. Install and development Source install, release archives, local build, and development commands. Implementation plan Shipped milestones, current posture, and deferred scope. Release policy Versioning, release process, and tagged archive distribution posture.