repowiseWorkspace — multi-repo commands
Manage repos in a repowise workspace — list, add, remove, scan, and pick the default.
A workspace is a parent directory containing several git repos. Indexing them together unlocks cross-repo co-changes, API contract matching, and federated MCP queries. See Workspace setup for the concept.
repowise workspace list
Show all repos in the workspace with their indexing status.
repowise workspace list [PATH]repowise workspace add
Add a repo to the workspace. PATH can be relative or absolute.
repowise workspace add PATH [OPTIONS]Prop
Type
repowise workspace add ../backend
repowise workspace add ../backend --alias backend-api --indexrepowise workspace remove
Remove a repo from the workspace config. The repo's .repowise/
directory is preserved on disk — only the workspace entry is dropped.
repowise workspace remove ALIASrepowise workspace scan
Scan the workspace root for new git repos not yet in the config.
repowise workspace scan [PATH] [OPTIONS]Prop
Type
repowise workspace scan
repowise workspace scan --yesrepowise workspace set-default
Change the default (primary) repo. The default is what tools target
when you omit repo= in MCP calls or don't pass --repo to the CLI.
repowise workspace set-default ALIASrepowise workspace diagnostics
Explain the cross-repo contract link count: per-repo provider and consumer counts, unmatched consumers grouped by reason, and orphan providers. See Extraction diagnostics.
repowise workspace diagnostics # human-readable report
repowise workspace diagnostics --json # raw JSON
repowise workspace diagnostics --repo api # limit to one reporepowise workspace check
Architecture lint: check the declared conformance: rules against the
system graph and detect dependency cycles. Exits non-zero on any
finding, so it gates CI. See
Architecture conformance.
repowise workspace check # human-readable report; exit 1 on findings
repowise workspace check --json # raw report JSONrepowise workspace metrics
Architecture-complexity metrics: propagation cost, the cyclic core, per-service roles, and a deterministic 1-10 architecture score. See Architecture metrics.
repowise workspace metrics # human-readable summary
repowise workspace metrics --json # raw metrics JSONMost workspace-aware operations live on other commands —
repowise update --workspace, repowise watch -w,
repowise hook install --workspace, repowise generate-claude-md -w.
Code health — health, risk
repowise health scores every file from deterministic biomarkers across three signals (defect risk, maintainability, performance); repowise risk scores the defect risk of a commit or diff range. Both are zero-LLM and run in seconds.
Decisions — capture, list, govern
Record architectural decisions so the why survives the team. Mine git history for proposals, confirm or dismiss them, deprecate stale ones, and check decision health.