Git Commit Message Generator (from a Diff)
omnial/x402-commit-message-generate
Given a git diff (and an optional message style: conventional, angular, or simple), returns a generated commit subject and body, the inferred change type (e.g. 'feat', 'fix') and scope, whether the change is a breaking change, and a one-line summary of the files touched. With the conventional style, full_message can repeat the type and scope prefix (feat(validate): feat(validate): ...); subject carries it once. Your input is sent to an outside service for processing; remove secrets and personal data first.
Price
Up to $0.0811 per call; you pay what the call used
You pay the price shown. If a call turns out to cost more than its quote, you pay the actual price, capped at twice the quote. No monthly minimum. Top-ups start at $5.00.
Data source
Generated by Anthropic's Claude from the inputs you provide.
Use it
Your AI assistant does the work: it finds this tool, shows you the price first, runs it, and you are charged when the run finishes. There is nothing to set up for this tool in particular.
Connect once and your AI can find and run this tool, and any other it needs.
For developers: the calls your assistant makes
// 1. search: find the tool
omnial_search({ query: "what you need" })
// 2. inspect: price and input schema
omnial_inspect({ tool: "omnial/x402-commit-message-generate" })
// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "omnial/x402-commit-message-generate" })
// 4. run: price the exact call first, then run it
omnial_execute({ tool: "omnial/x402-commit-message-generate", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "omnial/x402-commit-message-generate", input: { /* ... */ } })
// 5. settle: the call is charged when it finishes, nothing to doNot connected yet? Point your MCP client at https://mcp.eden-engine.com/mcp, then copy a config for your client.
Pricing
Every charge this tool can incur.
| Charge | Price |
|---|---|
Per call | $0.0811 |
- Updated
- Oct 27, 2026
Input and output schemas
Input schema
{
"type": "object",
"required": [
"diff"
],
"properties": {
"diff": {
"type": "string"
},
"style": {
"type": "string",
"description": "conventional/angular/simple"
}
},
"additionalProperties": false
}Output schema
{
"type": "object",
"properties": {
"body": {
"type": [
"string",
"null"
],
"description": "A longer explanation of the change. Observed null on a short, self-explanatory fix and populated on a feature addition -- not always present."
},
"type": {
"type": "string",
"description": "The inferred conventional-commit change type, e.g. 'feat', 'fix'."
},
"scope": {
"type": "string",
"description": "The inferred area of the codebase the change touches, e.g. 'validate'."
},
"subject": {
"type": "string",
"description": "A short, single-line commit subject describing the change."
},
"files_summary": {
"type": "string",
"description": "A one-line, human-readable summary of what changed in the touched file(s)."
},
"breaking_change": {
"type": "boolean",
"description": "Whether the generated message flags this as a breaking change."
}
},
"description": "The generated commit-message record.",
"additionalProperties": true
}