Repository Manager
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LLM_AGENT_MODEL | Yes | Model used by specialist agent nodes | |
| LLM_ROUTER_MODEL | Yes | Model used by the router node | |
| REPO_MANAGER_URL | No | Base URL of the target service | http://localhost:8000 |
| GRAPH_ROUTER_TIMEOUT | No | Router-node timeout (seconds) | 300.0 |
| REPO_MANAGER_PASSWORD | Yes | Password for authentication | |
| REPO_MANAGER_USERNAME | No | Username for authentication | admin |
| GRAPH_VERIFIER_TIMEOUT | No | Verifier-node timeout (seconds) | 300.0 |
| REPOSITORY_MANAGER_WORKSPACE | Yes | Root directory of the git workspace to manage |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Expert tool for managing hierarchical Git workspaces, engineering bulk operations, and documentation.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| repository_manager_add_projectB | Stage all changes (git add -A) for a single Git project. |
| repository_manager_add_projectsC | Stage all changes for multiple projects in parallel. |
| repository_manager_build_projectsB | Build projects serially so compilation cannot exhaust the workstation. |
| repository_manager_bulk_bumpB | Bumps the version for all projects in the workspace in parallel. |
| repository_manager_bump_versionA | Bump the version of the project using bump2version. Args: part (str): The part of the version to bump (major, minor, patch). allow_dirty (bool): Whether to allow dirty working directory. path (str): The path to the project directory. dry_run (bool): Whether to perform a dry run. verbose (bool): Whether to use verbose output (for dry-run visibility). force (bool): If the target version's tag already exists locally (an orphan tag from a prior partial bump that left the version file un-updated), delete that local tag and re-bump instead of silently skipping. The orphan tag must NOT be on the remote. Returns: GitResult: Result of the operation. |
| repository_manager_cleanup_artifactsC | Removes test artifacts and temporary files from the specified directory. |
| repository_manager_clone_projectsC | Clone all specified Git projects in parallel using multiple threads. Returns: List[GitResult]: A list of GitResult objects, one for each clone operation. |
| repository_manager_clone_repositoryB | Clone a single Git repository to a specific target path. Args: url (str): The repository URL to clone. target_path (str): The absolute path where the repository should be cloned. Returns: GitResult: The result of the Git clone command. |
| repository_manager_commit_code_projectA | Stage ALL changes (git add -A), optionally gate on pre-commit, then commit. This is the per-repo "commit our feature code" step the release pipeline
runs BEFORE bumping versions. Unlike :meth: If pre-commit fails for real (not just auto-format), the failure is surfaced and nothing is committed. |
| repository_manager_commit_code_projectsB | Concurrently stage + pre-commit + commit feature code across projects. The "add all our code, pre-commit, then commit" release-prep step,
throttled by |
| repository_manager_commit_projectB | Commit staged changes (git commit -m "{message}") for a single Git project. |
| repository_manager_commit_projectsC | Commit staged changes for multiple projects in parallel. |
| repository_manager_create_projectB | Create a new project directory and initialize it as a git repository. Args: path (str): The path of the project directory to create. Returns: GitResult: Result of the operation. |
| repository_manager_discover_projectsA | Scan self.path for immediate subdirectories containing a .git folder. Populates and returns self.project_map. |
| repository_manager_generate_markdown_summaryC | Generates a beautiful markdown summary of bulk operation results. |
| repository_manager_generate_workspace_templateC | Generates a workspace.yml template at the specified path. |
| repository_manager_get_consolidated_skill_pathsA | Returns absolute paths to the 15 specific building and documentation skills. |
| repository_manager_get_project_mapA | Returns the mapping of repository URLs to their local project paths. Ensures paths are absolute and expanded. |
| repository_manager_get_readmeA | Get the content and path of the README.md file in the specified path. Args: path (str, optional): The directory path. Defaults to self.path. Returns: ReadmeResult: Object containing 'content' and 'path' of the README.md file. |
| repository_manager_get_workspace_projectsA | Returns a list of project basenames (e.g. 'genius-agent') defined in the workspace. |
| repository_manager_git_actionC | Execute a Git command in the specified directory. The operation is admitted through descriptor-pinned helpers before any subprocess is started. |
| repository_manager_install_projectC | Install a Python project using pip install -e .[extra]. |
| repository_manager_install_projectsC | Bulk installs Python and Node projects in the workspace. |
| repository_manager_list_branchesA | Returns a dictionary mapping project basenames to their current active git branch. |
| repository_manager_load_projects_from_yamlC | Loads repository URLs from a YAML workspace file using Pydantic models. Strictly determines self.path relative to the configuration file. |
| repository_manager_pre_commitB | Execute pre-commit commands in the specified path. Args: run (bool): Whether to run 'pre-commit run --all-files'. Default True. autoupdate (bool): Whether to run 'pre-commit autoupdate'. Default False. path (str, optional): Path to run in. Defaults to self.path. |
| repository_manager_pre_commit_projectsC | Execute pre-commit commands for all projects in parallel. Returns: List[GitResult]: A list of GitResult objects. |
| repository_manager_pull_projectA | Pull updates for a single Git project and optionally checkout the default branch. Args: path (str): The path to the project to pull. Defaults to self.path. Returns: GitResult: The result of the pull operation. |
| repository_manager_pull_projectsB | Pull updates for multiple projects in parallel. |
| repository_manager_push_projectA | Atomically publish a clean checkout's exact current branch and release tag. Publication runs from a sealed private admin repository, uses only the authorized direct destination, and reads every remote ref back before reporting success. Dirty state, gate failure, identity/config drift, non-fast-forward updates, tag collisions, and partial atomic updates all refuse publication; GitHub push protection returns an actionable error. |
| repository_manager_push_projectsC | Push updates for multiple projects in parallel. |
| repository_manager_save_workspace_configC | Saves the current or provided WorkspaceConfig to a YAML file. |
| repository_manager_set_threadsC | Set the number of threads for parallel processing. Args: threads (int): The number of threads. Notes: If the input is invalid, defaults 6 |
| repository_manager_setup_from_yamlA | Sets up the workspace structure from a YAML file.
|
| repository_manager_test_projectsC | Execute pytests for the specified projects in parallel. Args: progress_phase: Phase name for live progress updates. progress_dict: Shared mutable dict for live progress reporting. |
| repository_manager_update_dependencyC | Update a package's pinned version in a deps file (pyproject or requirements). |
| repository_manager_validate_and_releaseC | Validate projects in parallel and report whether all passed. |
| repository_manager_validate_single_projectA | Validates a single repository by running its FAST-tier gates. Delegates to :func: |
| repository_manager_worktree_hygieneA | Audit (and optionally prune) session worktrees as a release-flow step. Wraps :meth: |
| rm_git_cloneC | Clone (rm_git). Typed bulk Git operations; arbitrary host commands are prohibited. |
| rm_git_enumerateC | Enumerate (rm_git). Typed bulk Git operations; arbitrary host commands are prohibited. |
| rm_git_pullC | Pull (rm_git). Typed bulk Git operations; arbitrary host commands are prohibited. |
| rm_git_pushC | Push (rm_git). Typed bulk Git operations; arbitrary host commands are prohibited. |
| rm_git_addC | Add (rm_git). Typed bulk Git operations; arbitrary host commands are prohibited. |
| rm_git_commitC | Commit (rm_git). Typed bulk Git operations; arbitrary host commands are prohibited. |
| rm_git_pre_commitC | Pre commit (rm_git). Typed bulk Git operations; arbitrary host commands are prohibited. |
| rm_git_commit_codeB | Commit code (rm_git). Typed bulk Git operations; arbitrary host commands are prohibited. |
| rm_git_statusC | Status (rm_git). Typed bulk Git operations; arbitrary host commands are prohibited. |
| rm_git_cancelC | Cancel (rm_git). Typed bulk Git operations; arbitrary host commands are prohibited. |
| rm_git_rawC | Raw (rm_git). Typed bulk Git operations; arbitrary host commands are prohibited. |
| repository_ingest_repositoriesB | Natively ingest git repositories into epistemic-graph as typed :GitRepository nodes. Enumerates repositories across a GitLab instance / GitHub org via the real VCS
enumerator and pushes them (typed :GitRepository nodes with vcs/clone_url/web_url/
default_branch provenance) into the knowledge graph via the fast engine client.
Best-effort: returns |
| rm_lane_startC | Start (rm_lane). The lane lifecycle for concurrent agents and humans (CONCEPT:RM-LANE-DOCTOR). Every check behind this tool exists because a specific collision destroyed
real work while the rule that would have prevented it was written down, in
prose, in front of the actor who broke it: editing a canonical checkout a
background
|
| rm_lane_doctorB | Doctor (rm_lane). The lane lifecycle for concurrent agents and humans (CONCEPT:RM-LANE-DOCTOR). Every check behind this tool exists because a specific collision destroyed
real work while the rule that would have prevented it was written down, in
prose, in front of the actor who broke it: editing a canonical checkout a
background
|
| rm_lane_healC | Heal (rm_lane). The lane lifecycle for concurrent agents and humans (CONCEPT:RM-LANE-DOCTOR). Every check behind this tool exists because a specific collision destroyed
real work while the rule that would have prevented it was written down, in
prose, in front of the actor who broke it: editing a canonical checkout a
background
|
| rm_lane_envC | Env (rm_lane). The lane lifecycle for concurrent agents and humans (CONCEPT:RM-LANE-DOCTOR). Every check behind this tool exists because a specific collision destroyed
real work while the rule that would have prevented it was written down, in
prose, in front of the actor who broke it: editing a canonical checkout a
background
|
| rm_lane_finishC | Finish (rm_lane). The lane lifecycle for concurrent agents and humans (CONCEPT:RM-LANE-DOCTOR). Every check behind this tool exists because a specific collision destroyed
real work while the rule that would have prevented it was written down, in
prose, in front of the actor who broke it: editing a canonical checkout a
background
|
| rm_worktree_addC | Add (rm_worktree). Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE). Each session works a repo in its own worktree on its own branch under
|
| rm_worktree_auditC | Audit (rm_worktree). Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE). Each session works a repo in its own worktree on its own branch under
|
| rm_worktree_bulk_addC | Bulk add (rm_worktree). Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE). Each session works a repo in its own worktree on its own branch under
|
| rm_worktree_listC | List (rm_worktree). Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE). Each session works a repo in its own worktree on its own branch under
|
| rm_worktree_mergeC | Merge (rm_worktree). Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE). Each session works a repo in its own worktree on its own branch under
|
| rm_worktree_pruneC | Prune (rm_worktree). Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE). Each session works a repo in its own worktree on its own branch under
|
| rm_worktree_removeC | Remove (rm_worktree). Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE). Each session works a repo in its own worktree on its own branch under
|
| rm_worktree_reset_branchC | Reset branch (rm_worktree). Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE). Each session works a repo in its own worktree on its own branch under
|
| rm_worktree_syncC | Sync (rm_worktree). Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE). Each session works a repo in its own worktree on its own branch under
|
| rm_merge_queue_enqueueA | Enqueue (rm_merge_queue). Serialized merge queue for ANY git repository (CONCEPT:RM-MERGE-QUEUE). The canonical driver of parallel development: lanes take worktrees, work,
then hand branches here, and the queue gates them as merged,
fast-forwards the base, and prunes the worktree and branch. Set The queue does not know what a gate is. Gates are declared in the
target repository's own Gating is differential: only a failure the base ref does not already produce blocks a candidate — the base is legitimately red here, and an absolute gate once deadlocked a queue and stranded 19 branches. A baseline that cannot be produced REFUSES the candidate; it never degrades to allow-all.
|
| rm_merge_queue_statusC | Status (rm_merge_queue). Serialized merge queue for ANY git repository (CONCEPT:RM-MERGE-QUEUE). The canonical driver of parallel development: lanes take worktrees, work,
then hand branches here, and the queue gates them as merged,
fast-forwards the base, and prunes the worktree and branch. Set The queue does not know what a gate is. Gates are declared in the
target repository's own Gating is differential: only a failure the base ref does not already produce blocks a candidate — the base is legitimately red here, and an absolute gate once deadlocked a queue and stranded 19 branches. A baseline that cannot be produced REFUSES the candidate; it never degrades to allow-all.
|
| rm_merge_queue_withdrawC | Withdraw (rm_merge_queue). Serialized merge queue for ANY git repository (CONCEPT:RM-MERGE-QUEUE). The canonical driver of parallel development: lanes take worktrees, work,
then hand branches here, and the queue gates them as merged,
fast-forwards the base, and prunes the worktree and branch. Set The queue does not know what a gate is. Gates are declared in the
target repository's own Gating is differential: only a failure the base ref does not already produce blocks a candidate — the base is legitimately red here, and an absolute gate once deadlocked a queue and stranded 19 branches. A baseline that cannot be produced REFUSES the candidate; it never degrades to allow-all.
|
| rm_merge_queue_runA | Run (rm_merge_queue). Serialized merge queue for ANY git repository (CONCEPT:RM-MERGE-QUEUE). The canonical driver of parallel development: lanes take worktrees, work,
then hand branches here, and the queue gates them as merged,
fast-forwards the base, and prunes the worktree and branch. Set The queue does not know what a gate is. Gates are declared in the
target repository's own Gating is differential: only a failure the base ref does not already produce blocks a candidate — the base is legitimately red here, and an absolute gate once deadlocked a queue and stranded 19 branches. A baseline that cannot be produced REFUSES the candidate; it never degrades to allow-all.
|
| rm_merge_queue_configC | Config (rm_merge_queue). Serialized merge queue for ANY git repository (CONCEPT:RM-MERGE-QUEUE). The canonical driver of parallel development: lanes take worktrees, work,
then hand branches here, and the queue gates them as merged,
fast-forwards the base, and prunes the worktree and branch. Set The queue does not know what a gate is. Gates are declared in the
target repository's own Gating is differential: only a failure the base ref does not already produce blocks a candidate — the base is legitimately red here, and an absolute gate once deadlocked a queue and stranded 19 branches. A baseline that cannot be produced REFUSES the candidate; it never degrades to allow-all.
|
| rm_build_requestB | Request (rm_build). Content-addressed build broker for ANY repository (CONCEPT:RM-TASK-LEDGER). Keyed by Honest degradation: a dirty tree or an unfingerprintable toolchain BUILDS — it never serves a possibly-stale artifact and never silently skips the cache as though it were consulted. Co-location: this tool always passes Arbitration is advisory (D-CP-8): an agent running |
| rm_build_statusC | Status (rm_build). Content-addressed build broker for ANY repository (CONCEPT:RM-TASK-LEDGER). Keyed by Honest degradation: a dirty tree or an unfingerprintable toolchain BUILDS — it never serves a possibly-stale artifact and never silently skips the cache as though it were consulted. Co-location: this tool always passes Arbitration is advisory (D-CP-8): an agent running |
| rm_build_artifactsC | Artifacts (rm_build). Content-addressed build broker for ANY repository (CONCEPT:RM-TASK-LEDGER). Keyed by Honest degradation: a dirty tree or an unfingerprintable toolchain BUILDS — it never serves a possibly-stale artifact and never silently skips the cache as though it were consulted. Co-location: this tool always passes Arbitration is advisory (D-CP-8): an agent running |
| rm_build_explainC | Explain (rm_build). Content-addressed build broker for ANY repository (CONCEPT:RM-TASK-LEDGER). Keyed by Honest degradation: a dirty tree or an unfingerprintable toolchain BUILDS — it never serves a possibly-stale artifact and never silently skips the cache as though it were consulted. Co-location: this tool always passes Arbitration is advisory (D-CP-8): an agent running |
| rm_build_gcC | Gc (rm_build). Content-addressed build broker for ANY repository (CONCEPT:RM-TASK-LEDGER). Keyed by Honest degradation: a dirty tree or an unfingerprintable toolchain BUILDS — it never serves a possibly-stale artifact and never silently skips the cache as though it were consulted. Co-location: this tool always passes Arbitration is advisory (D-CP-8): an agent running |
| rm_projects_installB | Install (rm_projects). Bulk install, build, and validate Python projects. The 'validate' action submits validation as a background job and returns a job_id immediately. Use 'validate_status' with that job_id to poll progress and retrieve results once complete. |
| rm_projects_buildA | Build (rm_projects). Bulk install, build, and validate Python projects. The 'validate' action submits validation as a background job and returns a job_id immediately. Use 'validate_status' with that job_id to poll progress and retrieve results once complete. |
| rm_projects_validateA | Validate (rm_projects). Bulk install, build, and validate Python projects. The 'validate' action submits validation as a background job and returns a job_id immediately. Use 'validate_status' with that job_id to poll progress and retrieve results once complete. |
| rm_projects_validate_statusB | Validate status (rm_projects). Bulk install, build, and validate Python projects. The 'validate' action submits validation as a background job and returns a job_id immediately. Use 'validate_status' with that job_id to poll progress and retrieve results once complete. |
| rm_docs_readiness_previewC | Preview (rm_docs_readiness). Preview/apply/verify artifacts after per-repository readiness setup. |
| rm_docs_readiness_applyC | Apply (rm_docs_readiness). Preview/apply/verify artifacts after per-repository readiness setup. |
| rm_docs_readiness_verifyC | Verify (rm_docs_readiness). Preview/apply/verify artifacts after per-repository readiness setup. |
| rm_gates_runB | Run (rm_gates). Run and inspect the two-tier (fast/heavy) pre-commit gate across repos. The single tool that can actually drive both tiers of the two-tier gate
model: |
| rm_gates_retestB | Retest (rm_gates). Run and inspect the two-tier (fast/heavy) pre-commit gate across repos. The single tool that can actually drive both tiers of the two-tier gate
model: |
| rm_gates_statusC | Status (rm_gates). Run and inspect the two-tier (fast/heavy) pre-commit gate across repos. The single tool that can actually drive both tiers of the two-tier gate
model: |
| rm_gates_explainC | Explain (rm_gates). Run and inspect the two-tier (fast/heavy) pre-commit gate across repos. The single tool that can actually drive both tiers of the two-tier gate
model: |
| rm_gates_profileC | Profile (rm_gates). Run and inspect the two-tier (fast/heavy) pre-commit gate across repos. The single tool that can actually drive both tiers of the two-tier gate
model: |
| rm_gates_audit_fail_fastB | Audit fail fast (rm_gates). Run and inspect the two-tier (fast/heavy) pre-commit gate across repos. The single tool that can actually drive both tiers of the two-tier gate
model: |
| rm_gates_xdist_planC | Xdist plan (rm_gates). Run and inspect the two-tier (fast/heavy) pre-commit gate across repos. The single tool that can actually drive both tiers of the two-tier gate
model: |
| rm_gates_xdist_applyC | Xdist apply (rm_gates). Run and inspect the two-tier (fast/heavy) pre-commit gate across repos. The single tool that can actually drive both tiers of the two-tier gate
model: |
| rm_gates_phase_directionB | Phase direction (rm_gates). Run and inspect the two-tier (fast/heavy) pre-commit gate across repos. The single tool that can actually drive both tiers of the two-tier gate
model: |
| rm_gates_reposC | Repos (rm_gates). Run and inspect the two-tier (fast/heavy) pre-commit gate across repos. The single tool that can actually drive both tiers of the two-tier gate
model: |
| rm_gates_phase_direction_hereC | Phase direction here (rm_gates). Run and inspect the two-tier (fast/heavy) pre-commit gate across repos. The single tool that can actually drive both tiers of the two-tier gate
model: |
| rm_rollout_planC | Plan (rm_rollout). |
| rm_rollout_applyD | Apply (rm_rollout). |
| rm_rollout_statusD | Status (rm_rollout). |
| rm_rollout_releaseD | Release (rm_rollout). |
| rm_workspace_listC | List (rm_workspace). Core workspace organization and configuration. |
| rm_workspace_list_branchesC | List branches (rm_workspace). Core workspace organization and configuration. |
| rm_workspace_setupC | Setup (rm_workspace). Core workspace organization and configuration. |
| rm_workspace_templateC | Template (rm_workspace). Core workspace organization and configuration. |
| rm_workspace_saveC | Save (rm_workspace). Core workspace organization and configuration. |
| rm_workspace_fleet_evidence_checkC | Fleet evidence check (rm_workspace). Core workspace organization and configuration. |
| rm_concepts_reserveB | Reserve (rm_concepts). Concept-id claim coordination against RMDD-16's central authority. Repository-manager never allocates a concept id itself: every action
here is a thin, MCP/CLI-neutral consumer of an injected authority
port. When the central authority ( |
| rm_concepts_getC | Get (rm_concepts). Concept-id claim coordination against RMDD-16's central authority. Repository-manager never allocates a concept id itself: every action
here is a thin, MCP/CLI-neutral consumer of an injected authority
port. When the central authority ( |
| rm_concepts_listC | List (rm_concepts). Concept-id claim coordination against RMDD-16's central authority. Repository-manager never allocates a concept id itself: every action
here is a thin, MCP/CLI-neutral consumer of an injected authority
port. When the central authority ( |
| rm_concepts_materializeC | Materialize (rm_concepts). Concept-id claim coordination against RMDD-16's central authority. Repository-manager never allocates a concept id itself: every action
here is a thin, MCP/CLI-neutral consumer of an injected authority
port. When the central authority ( |
| rm_concepts_releaseC | Release (rm_concepts). Concept-id claim coordination against RMDD-16's central authority. Repository-manager never allocates a concept id itself: every action
here is a thin, MCP/CLI-neutral consumer of an injected authority
port. When the central authority ( |
| rm_concepts_verify_candidateC | Verify candidate (rm_concepts). Concept-id claim coordination against RMDD-16's central authority. Repository-manager never allocates a concept id itself: every action
here is a thin, MCP/CLI-neutral consumer of an injected authority
port. When the central authority ( |
| rm_concepts_verify_generationC | Verify generation (rm_concepts). Concept-id claim coordination against RMDD-16's central authority. Repository-manager never allocates a concept id itself: every action
here is a thin, MCP/CLI-neutral consumer of an injected authority
port. When the central authority ( |
| rm_concepts_reconcileB | Reconcile (rm_concepts). Concept-id claim coordination against RMDD-16's central authority. Repository-manager never allocates a concept id itself: every action
here is a thin, MCP/CLI-neutral consumer of an injected authority
port. When the central authority ( |
| rm_remote_workers_register_workerC | Register worker (rm_remote_workers). Remote worker registry, immutable source staging, and artifact transport. Composes RMDD-15's |
| rm_remote_workers_seed_from_inventoryC | Seed from inventory (rm_remote_workers). Remote worker registry, immutable source staging, and artifact transport. Composes RMDD-15's |
| rm_remote_workers_profileC | Profile (rm_remote_workers). Remote worker registry, immutable source staging, and artifact transport. Composes RMDD-15's |
| rm_remote_workers_recheckC | Recheck (rm_remote_workers). Remote worker registry, immutable source staging, and artifact transport. Composes RMDD-15's |
| rm_remote_workers_stage_sourceC | Stage source (rm_remote_workers). Remote worker registry, immutable source staging, and artifact transport. Composes RMDD-15's |
| rm_remote_workers_verify_sourceC | Verify source (rm_remote_workers). Remote worker registry, immutable source staging, and artifact transport. Composes RMDD-15's |
| rm_remote_workers_receive_artifactC | Receive artifact (rm_remote_workers). Remote worker registry, immutable source staging, and artifact transport. Composes RMDD-15's |
| rm_remote_workers_dispatch_buildC | Dispatch build (rm_remote_workers). Remote worker registry, immutable source staging, and artifact transport. Composes RMDD-15's |
| rm_remote_workers_host_loss_reconcileB | Host loss reconcile (rm_remote_workers). Remote worker registry, immutable source staging, and artifact transport. Composes RMDD-15's |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| connector-status | Ask for this connector server's current operational status. |
| repository-manager-concept-steward | |
| repository-manager-operator | |
| repository-manager-release-engineer | |
| repository-manager-repository-maintainer |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| _connector_status_resource | Native resource exposing this server's static status payload. |
| ontology://repository-manager/repository.ttl | |
| ontology://repository-manager/contracts.ttl | |
| connector-resources | Data sources, ontology mappings and resources of this connector. |
| repository-manager-candidate-certification/SKILL.md | Understand and verify a branch candidate's and a sealed generation's certification state — the Candidate/Generation lifecycle vocabulary, the validation-stage/evidence model, and the `rm_concepts_verify_candidate` / `verify_generation` marker-collision checks — before trusting a merge-queue outcome as landable. This is the vocabulary and marker-verification layer; the actual batching/differential-gating/bisection mechanics that decide landability live in `rm_merge_queue_*` and are documented in repository-manager-merge-and- reconcile, not duplicated here. Use when an agent must explain why a candidate is in a given state, verify a candidate's or generation's introduced CONCEPT: markers, or reason about a rejected/bisected generation. Do NOT use this skill to actually land a branch (repository-manager-merge-and-reconcile) or to reserve a concept id (repository-manager-concept-coordination). |
| repository-manager-candidate-certification/_manifest | File listing for repository-manager-candidate-certification |
| repository-manager-workspace-validation/SKILL.md | Install, build, and validate the managed projects of a workspace via the repository-manager MCP server — run pre-commit + pytest validation per project and install/build ecosystems. Use when the agent must ensure all projects are valid, fix project errors, or run the validation suite. To raise a dependency floor across the fleet use `rm_rollout` / `repository-manager rollout` (repository-manager-workspace-release). Do NOT use for isolated session worktrees (repository-manager-worktree-orchestration) or bulk clone/pull/push (repository-manager-bulk-git-operations). |
| repository-manager-workspace-validation/_manifest | File listing for repository-manager-workspace-validation |
| repository-manager-development/SKILL.md | Deliver a small, source-backed repository-manager change from an isolated worktree through focused validation, normal review, and evidence-based publication. Use this skill for repository-manager's own MCP adapter, CLI, packaging, skills, workflows, and development gates; use the narrower lifecycle and release skills for their detailed operations. |
| repository-manager-development/_manifest | File listing for repository-manager-development |
| repository-manager-gate-execution/SKILL.md | Run and inspect the two-tier (fast/heavy) pre-commit gate across repos via `rm_gates_*`, and validate a fix without re-running the whole wave: `run` to populate the durable gate ledger, `retest` to narrow a re-run to only the hooks the ledger last recorded failing (with automatic full-wave escalation on an all-pass), and `profile` to find the slow hooks. Covers the gate ledger's clear-on-improve/staleness/shippability semantics, the cargo-vs-pytest/go fail-fast-flag asymmetry, and three environment traps that reliably produce false gate verdicts. Use when an agent must run a repo's fast or heavy gate, re-validate only what just failed, explain a failure, or find what is slow. Do NOT use for the merge queue's own differential gate-vs-base comparison (repository-manager-merge-and-reconcile), Python install/build via `rm_projects_*` (repository-manager-workspace-validation), or content-addressed build caching (repository-manager-build-coordination). |
| repository-manager-gate-execution/_manifest | File listing for repository-manager-gate-execution |
| repository-manager-bulk-git-operations/SKILL.md | Bulk, parallel git operations across a whole workspace of repositories via the repository-manager MCP server — clone, pull, push, add, commit, pre-commit, and enumerate every repo across a GitLab instance / GitHub org into an ingest manifest (which also natively ingests them into the knowledge graph as typed :GitRepository nodes). Raw host git commands are permanently retired and always refused. Use when the agent must operate over many repos at once or discover the full repo inventory. Do NOT use for single-session worktree branches (repository-manager-worktree-orchestration) or per-project install/validate/ version bumps (repository-manager-workspace-validation). |
| repository-manager-bulk-git-operations/_manifest | File listing for repository-manager-bulk-git-operations |
| repository-manager-lane-lifecycle/SKILL.md | Run one unit of work — one agent session or one person — as an isolated lane in a repository many other lanes are editing at the same time. Covers opening a lane (worktree + partitioned build/test/hook state), staying isolated while working, diagnosing a lane that is behaving impossibly, and closing it out. Use whenever you are about to edit a repository that other agents or humans are also editing, when a test fails in a way that cannot be true, when a build will not go green, or when work has gone missing. Do NOT use for landing a branch and resolving conflicts (repository-manager-merge-and-reconcile) or for workspace-wide sweeps across many repos (repository-manager-fleet-scale-operations). |
| repository-manager-lane-lifecycle/_manifest | File listing for repository-manager-lane-lifecycle |
| repository-manager-fleet-scale-operations/SKILL.md | Run development across MANY repositories and many concurrent lanes at once — bulk worktree creation, workspace-wide worktree audits and classification (merged / active / stale / dangling / orphaned), safe mass pruning, draining several repositories' merge queues in parallel, and sizing concurrency against the real binding constraint (disk I/O and swap, not the agent cap). Use when launching or reclaiming a wave of lanes, when worktrees have accumulated, or when deciding how many heavy jobs may run at once. Do NOT use for a single lane's lifecycle (repository-manager-lane-lifecycle) or for landing and reconciling one branch (repository-manager-merge-and-reconcile). |
| repository-manager-fleet-scale-operations/_manifest | File listing for repository-manager-fleet-scale-operations |
| repository-manager-development-lifecycle/SKILL.md | The default entrypoint for one unit of work — plan, start, work with a live heartbeat, check, submit, watch status, and abort — composed entirely from the repository-manager MCP/CLI surface (rm_lane_*, rm_worktree_*, rm_merge_queue_*, and rm_concepts_*). It never opens a raw shell, runs a direct compiler, hand-merges, or writes an unreserved concept marker; every step routes to the governed action that already exists. Use this FIRST for any repository change an agent will land. Do NOT use for many-repository fan-out (repository-manager-fleet-scale-operations), bulk git across repos (repository-manager-bulk-git-operations), build-cache operation (repository-manager-build-coordination), or remote-worker capacity (repository-manager-worker-operations) — those are named lower down in this skill's routing map. |
| repository-manager-development-lifecycle/_manifest | File listing for repository-manager-development-lifecycle |
| repository-manager-merge-and-reconcile/SKILL.md | Land a branch into a shared base that dozens of other lanes are landing into at the same time, and reconcile it when it conflicts. Covers the serialized merge queue, per-repository gate declarations, differential gating against a base ref that is legitimately red, measuring the MERGED tree rather than the branch tip, the conflict-resolution decision procedure (generated-file / semantic-divergence / base-moved / gate-red), and safe pruning. Use when a branch is ready to land, when a merge conflicts, when a gate is red and you must decide whether that is NEW, or when a queue candidate is rejected. Do NOT use for opening or isolating a lane (repository-manager-lane-lifecycle) or for workspace-wide sweeps (repository-manager-fleet-scale-operations). |
| repository-manager-merge-and-reconcile/_manifest | File listing for repository-manager-merge-and-reconcile |
| repository-manager-parallel-lane-orchestration/SKILL.md | Run a program as one central orchestrator plus many parallel worker agents: brief each lane, land its branch into main locally the moment it arrives, prune the branch and worktree immediately, and push only once the program is complete. Covers the lane briefing contract, land-as-they-arrive merge discipline, provider-before-consumer ordering for cross-repo changes, adjudicating contradictory lane reports, and the verification rules that catch a lane (or the orchestrator) being confidently wrong. Use when dispatching more than one worker agent at a time, when deciding whether a returned lane is safe to land, or when reconciling a workspace back to zero branches and zero worktrees. Do NOT use for the mechanics of a single merge or conflict (repository-manager-merge-and-reconcile), for opening one lane (repository-manager-lane-lifecycle), or for release/publish (repository-manager-workspace-release). |
| repository-manager-parallel-lane-orchestration/_manifest | File listing for repository-manager-parallel-lane-orchestration |
| repository-manager-build-coordination/SKILL.md | Content-addressed build/cache coordination for ANY repository via the repository-manager MCP server — dedup-or-build requests, cache-key status, published artifacts, why a key missed cache, and bounded cache reclamation. Routes agents away from a bare, uncoordinated `cargo build`/`uv sync`/`pnpm build` that duplicates work every other lane asking for the same (repo, tree-sha, feature-set, toolchain, target) has already paid for. Use when an agent needs a repository's build artifacts, wants to know whether a build is cached, or must reclaim old cache entries. Do NOT use for the packaging-style `rm_projects_*` install/build (repository-manager-workspace-validation), for the merge queue's own gate execution (repository-manager-merge-and-reconcile), or for sizing how many heavy builds may run at once (repository-manager-fleet-scale-operations). |
| repository-manager-build-coordination/_manifest | File listing for repository-manager-build-coordination |
| repository-manager-workspace-release/SKILL.md | Roll a dependency floor across the fleet deterministically and manage the `workspace.yml` manifest — via `rm_rollout` (or `repository-manager rollout`) and `rm_workspace_*`. A rollout selects the workspace.yml group's non-archived repos that depend on the package, plans per repo from main into a resumable ledger, applies each change in a fresh worktree through a pull request with auto-merge, reports merged/failing/pending, and tags `v<version>` only after the PR merged and main's floor is met. Nothing reaches main except through a PR. Use for "roll scion-sdk X to all connectors", "which rollout PRs are failing", "tag the repos whose rollout merged", or scaffolding/saving `workspace.yml`. Do NOT use for per-project validation (repository-manager-workspace-validation) or bulk clone/pull/push (repository-manager-bulk-git-operations). |
| repository-manager-workspace-release/_manifest | File listing for repository-manager-workspace-release |
| repository-manager-worker-operations/SKILL.md | Register a remote host's weighted capacity and authorized repository roots, read its profile, run the dispatch-time entitlement recheck, stage/verify an immutable source commit onto it with a fixed clone/fetch/checkout command sequence, stream artifacts/logs back, and reconcile a lost host — via the repository-manager `rm_remote_workers_*` MCP tool / `--remote-workers` CLI family. Routes agents away from a raw SSH/tunnel command or a hand-rolled clone onto a remote host. ⚠ `recheck`/live dispatch refuse honestly without the optional tunnel-manager dependency, and `host_loss_reconcile` always refuses today — read the fail-closed section before assuming either works. Use when placing or staging work on a non-local host. Do NOT use for a purely local build (repository-manager-build-coordination) or for the lane/worktree lifecycle itself (repository-manager-lane-lifecycle). |
| repository-manager-worker-operations/_manifest | File listing for repository-manager-worker-operations |
| repository-manager-concept-coordination/SKILL.md | Reserve, inspect, release, and materialize a CONCEPT:ID claim, and verify a candidate's or generation's introduced concept markers against those claims, via the repository-manager `rm_concepts_*` MCP tool / `--concepts` CLI family. Routes agents away from hand-writing a `CONCEPT:` marker without first reserving its id, which is exactly how two concurrent lanes collide on the same identifier. Use before writing any new `CONCEPT:` marker, or to verify a candidate/generation's markers before it lands. ⚠ On `main` as of this lane, every mutating action refuses honestly with `ConceptAuthorityUnavailable` — read the fail-closed section before assuming this tool allocates anything. Do NOT use for the lane/worktree lifecycle itself (repository-manager-lane-lifecycle) or for landing a branch (repository-manager-merge-and-reconcile). |
| repository-manager-concept-coordination/_manifest | File listing for repository-manager-concept-coordination |
| repository-manager-worktree-orchestration/SKILL.md | Concurrent multi-session git worktree orchestration via the repository-manager MCP server — create, list, sync, merge, prune, and audit linked worktrees under a shared workspace. Use when the agent must open an isolated branch worktree for a session, list/audit which worktrees are merged / active / stale / dangling, sync a worktree against its base, merge finished work back, or safely prune merged worktrees. Do NOT use for bulk clone/pull/push across repos (repository-manager-bulk-git-operations) or per-project validation/version bumps (repository-manager-workspace-validation). |
| repository-manager-worktree-orchestration/_manifest | File listing for repository-manager-worktree-orchestration |
| repository-manager-operations/SKILL.md | Operate repository-manager through its governed MCP and Arbora capabilities, including its development-lifecycle, lane, worktree, merge-queue, build, workspace validation/release, concept-coordination, and remote-worker-operations workflows (see references/catalog.md for the full, current list). Use when a request requires this provider's read, change, automation, ingestion, troubleshooting, or evidence workflows. |
| repository-manager-operations/_manifest | File listing for repository-manager-operations |
TDQS
Scored across 120 tools
There is massive overlap across families: repository_manager_add_project vs rm_git_add, pull_project vs rm_git_pull, commit_project vs rm_git_commit, and many rm_gates_* tools share nearly identical descriptions. Several families (rm_lane, rm_merge_queue, rm_build, rm_worktree, rm_concepts, rm_remote_workers) repeat the same description for every action, so an agent cannot reliably infer which tool to use.
Names are snake_case throughout, but the surface mixes long repository_manager_* prefixes with shorter rm_* families, and some tools use vague or internal action suffixes such as rm_gates_phase_direction_here and rm_gates_explain/profile. The repeated family prefixes help somewhat, but the inconsistent dual naming scheme and duplicated action vocabulary make it feel ad hoc.
At 120 tools, the server is far beyond a reasonable tool surface for repository management. Many tools are near-duplicates, internal workflow phases, or thin wrappers around the same Git operations, so the count is an extreme mismatch rather than a well-scoped set.
The surface broadly covers cloning, pulling, pushing, committing, building, testing, validation, worktrees, merge queues, and workspace setup, so core repository workflows are present. However, there are notable gaps and placeholder-like areas such as empty rm_rollout descriptions, no clear project deletion/removal path, and no obvious branch creation/checkout/diff/log lifecycle outside a generic git action.