multi-repo-dev
Skill177 starsChanged 7 days agoApache-2.0View on GitHub
Manage vcs source checkouts, local Bzlmod overrides, and versioned registry publication for multi-repository development.
- Commits and pushes
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- agent-evaluationSkill
- algorithm-developmentSkill
- buildSkill
- change-reviewSkill
- container-buildSkill
- engineering-solution-designSkill
- interface-migrationSkill
- issue-localizationSkill
- lintSkill
- long-horizon-developmentSkill
- model-artifact-integrationSkill
- performance-optimizationSkill
- repository-agent-setupSkill
- simulation-regressionSkill
- test-impact-analysisSkill
- unified-core-runtimeSkill
- vendorSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 8 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 10
Use for coordinated development across Bazel modules, consumer integration, or promotion from local source validation to registry-based …
- Distinctive: line 15
Read the consumer's agent rules, repository manifest, MODULE declarations, rc files, and relevant build/test entrypoints.
- Very specific: line 24
Use the project's vcs manifest to validate and import repositories into its designated source directory.
- Very specific: line 26
Verify URLs, revisions, MODULE.bazel identities, and exported BUILD targets.
- Very specific: line 35
Keep local overrides opt-in in the consumer's .bazelrc.dev, imported by its root .bazelrc.
- Distinctive: line 43
Use module names, not repository aliases, as override keys.
- Distinctive: line 54
After local validation, publish tested source as immutable revisions or release archives, dependencies before consumers.
- Distinctive: line 57
If the exact version is absent, add its entry following the registry's policy: version metadata, matching MODULE declarations, retrievable …
- Distinctive: line 60
Never publish host-only source paths or rewrite a published version.
- Distinctive: line 70
After authorized registry publication, confirm the configured remote registry serves the versions and validate normal consumer operation …
- Distinctive: line 90
Stop at the first actionable error.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Multi-Repository Development
When
Use for coordinated development across Bazel modules, consumer integration, or promotion from local source validation to registry-based consumption.
Prerequisites
Read the consumer's agent rules, repository manifest, MODULE declarations, rc files, and relevant build/test entrypoints. Identify the checkout directory, module names, repository aliases, registry order, and approved build environment. Preserve dirty worktrees and reuse existing toolchains and caches.
Steps
1. Checkout and inspect
Use the project's vcs manifest to validate and import repositories into its
designated source directory. Inspect existing work before importing/updating.
Verify URLs, revisions, MODULE.bazel identities, and exported BUILD targets.
Checkout confirms source availability and identity, not correctness.
2. Integrate and validate locally
Declare bazel_dep in each direct consumer before integration. A root need
not repeat a transitive declaration unless it uses the module's labels directly.
Independent module development can precede consumer integration.
Keep local overrides opt-in in the consumer's .bazelrc.dev, imported by its
root .bazelrc. The following is a template; substitute verified module names
and workspace-relative paths:
common:dev --override_module=<module>=%workspace%/<checkout-path>Use module names, not repository aliases, as override keys. An override replaces a module in the dependency graph; it does not declare a dependency. Registration is not required for the overridden module, but other dependencies must resolve.
In the approved environment, use --config=dev consistently for graph
inspection, repository mapping, builds, and tests. Verify mappings point to the
intended checkouts, then run the smallest consumer targets and focused tests
covering the coordinated changes. Follow the project's lockfile policy.
3. Publish source and register versions
After local validation, publish tested source as immutable revisions or release archives, dependencies before consumers. Publishing requires authorization.
If the exact version is absent, add its entry following the registry's policy: version metadata, matching MODULE declarations, retrievable source references, required integrity hashes, and applicable patches or presubmit checks. Never publish host-only source paths or rewrite a published version. Bzlmod resolves dependencies; it does not upload or release Git repositories.
4. Validate registration and promote
Select intended release versions in the validation consumer. Disable local overrides for the entire release dependency set and use the edited registry. Inspect registry precedence so an earlier registry does not shadow the entry. Resolve, build, and test through registry-fetched source before submitting it.
After authorized registry publication, confirm the configured remote registry serves the versions and validate normal consumer operation without local overrides or the local registry. Restore temporary validation configuration without reverting pre-existing work; retain intended release version updates.
For reproducible handoffs, export exact vcs revisions after source and registry commits are published. The export does not capture uncommitted changes.
Acceptance
- Local: mappings use intended checkouts; relevant builds and tests pass.
- Registry: exact versions pass without source overrides masking dependencies.
- Publication: remote registry consumption passes without development sources.
- Handoff: exact published revisions are recorded.
Report the achieved phase. Local override success or a Git push alone does not establish release acceptance.
Failure handling
Stop at the first actionable error. Do not change versions, lockfiles, sources, cache ownership, or install packages to hide it. Obtain approval before expanding scope, and preserve unrelated work.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

