Skip to main content
Glama

LogNexus Commit: Atomic commit with Git Note and review gate

lognexus_commit

Create atomic Git commits with conventional messages, authorship trailers, contract validation, optional task completion, and Git Note attachment for LogNexus branches.

Instructions

Atomically create a Git commit with conventional commit format, authorship trailers, subtask file contract validation, optional task finishing, and Git Note attachment in a single operation. Use when creating any commit on a LogNexus branch, including the atomic subtask commits that close a Tn. Not for retro-attaching a note to a commit that already exists (use lognexus_note_attach), and not for bypassing the gate: the commit engine refuses to run on a protected branch and rejects files outside the contract.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "author": "deepseek/chat (kimi-code)",
      "message": "feat(#26/T3): normalize MCP tool titles and schema examples",
      "finishTask": true
    },
    "name": "lognexus_commit"
  }
}

Input Schema

NameRequiredDescriptionDefault
tierNoOperational routing tier ('tier-1', 'tier-2', 'tier-3').
authorNoAuthor trailer identity, e.g. 'gemini/flash (antigravity)'.
messageYesConventional commit message, e.g. 'feat(#15/T1): add atomic commit CLI and tool'.
reviewerNoOptional reviewer trailer identity, e.g. 'gemini/pro (review-gate)'.
escalatedNoIf true, acknowledges a tier-1 author working on a tier-3 subtask (records 'escalated: true' in the Git Note).
allowEmptyNoIf true, allows creating an empty commit.
finishTaskNoIf true, marks the active subtask as completed in the persistent state.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.6
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "author": "deepseek/chat (kimi-code)",
      +    "finishTask": true,
      +    "message": "feat(#26/T3): normalize MCP tool titles and schema examples"
      +  }
      +]
    • changedInput schema / properties / tier / description
      Previous value: -"Optional routing tier override. Defaults to the tier inferred from the author identity."New value: +"Operational routing tier ('tier-1', 'tier-2', 'tier-3')."
  2. Changed2 schema fields changedv1.2.5
    • addedInput schema / properties / escalated
      Added value: +{
      +  "description": "If true, acknowledges a tier-1 author working on a tier-3 subtask (records 'escalated: true' in the Git Note).",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / tier
      Added value: +{
      +  "description": "Optional routing tier override. Defaults to the tier inferred from the author identity.",
      +  "enum": [
      +    "tier-1",
      +    "tier-2",
      +    "tier-3"
      +  ],
      +  "type": "string"
      +}
  3. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose key behavior: atomicity, that the engine refuses to run on a protected branch, and that it rejects files outside the contract. It stops short of stating the success response shape (e.g. commit SHA) or what happens to state if finishing fails midway.

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

Conciseness4/5

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

Two sentences, front-loaded with the core operation and dense but purposeful — no filler. It is on the longer side and packs several concepts (contract validation, gate, finishing) into clause form, which slightly taxes scanning but nothing is wasted.

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 7-parameter mutation tool with no output schema and no annotations, the description covers the essential operating constraints (protected branch, file contract, atomicity). It could be more complete about the return value and interaction between finishTask and commit failure, but no critical calling information is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter including enum and trailer identities is already documented in the schema. The description adds essentially no parameter-level detail beyond what structured fields provide, so baseline 3 applies.

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?

States specific verb and resource ('Atomically create a Git commit') and enumerates the bundled operations (conventional format, trailers, contract validation, task finishing, note attachment). It explicitly differentiates from the sibling lognexus_note_attach, so an agent can select it without opening schemas.

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

Usage Guidelines5/5

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

Gives an explicit when ('creating any commit on a LogNexus branch, including the atomic subtask commits that close a Tn') and two explicit when-nots with the alternative named (retro-attaching a note → lognexus_note_attach; bypassing the gate → refused). Routing is unambiguous.

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