Skip to main content
Glama
Sign In
cohors

cohors

by rushirb2001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Commit

commit

Stage tracked and untracked changes and record them with a message across selected repositories; dry-run first to preview targets, then confirm to apply without rewriting history.

Instructions

git add -A + git commit -m across the selected repos (stages tracked AND untracked; "nothing to commit" is a no-op). Never amends or rewrites history. Pair with push to finish a cross-repo change. Requires selector and message. Executing needs --allow-writes AND confirm:true; dry_run:true previews the target set with neither.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "selector": "<selector>",
      "message": "<message>"
    },
    "name": "commit"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually act; preview first with dry_run.
dry_runNoPreview the resolved target set without acting.
messageYesCommit message, applied to every selected repo (required).
selectorYesPredicate that selects repos across the fleet; set fields to AND them, omit a field for no constraint (ADR-024). Scope: all (bool — the whole fleet), ids[str], name (glob, e.g. "pay*"), path_glob (* stays within one path segment, ** crosses /), root, group (a config-defined cluster name, e.g. "payments"). Local state: dirty, ahead (alias unpushed), behind, diverged, no_upstream, unpublished (a branch never pushed although the repo has a remote), stale_fetch (remote not fetched for over 14 days), has_stash, detached, conflicted, in_operation (merge/rebase/… mid-flight), error, branch (exact name), attention ("any"|"notice"|"warn"|"risk"). Remote (needs a GitHub token): ci ("passing"|"failing"|"pending"|"none"), min_prs (int). Combine: any_of[selector] (OR), not (selector). The empty selector {} matches NOTHING by design — pass {"all": true} for the whole fleet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations: discloses staging scope, that a clean tree is a no-op, that history is never amended or rewritten, and that execution is gated by both an --allow-writes flag and confirm:true while dry_run bypasses both gates. These are exactly the behavioral facts an agent needs before invoking a mutation, none of which the annotations convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, front-loaded with the concrete command semantics, then constraints, then the safety gate. Parentheticals carry non-obvious facts rather than filler; nothing is redundant with the schema or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a fleet-wide mutation with a rich nested selector and no output schema, the definition covers staging, no-op behavior, history safety, and the write gate. It stops short of saying what is reported back per repo or how partial failures across the selected set are handled, which is the remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description adds real meaning: message is applied to every selected repo, confirm must be true to act, and dry_run previews without either gate. The only unaddressed piece is the selector's compound logic, which the schema already documents thoroughly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the concrete operations it performs ("git add -A + git commit -m <message> across the selected repos") plus the exact staging semantics (tracked AND untracked). This is a specific verb+resource statement that an agent can immediately distinguish from siblings like push or changes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing guidance by naming the complement ("Pair with push to finish a cross-repo change") and the prerequisite flow (preview with dry_run, then confirm). It does not spell out when NOT to use this tool versus alternatives such as stash, but the pairing and precondition guidance covers most selection decisions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools