How do I install the Agent Commit skill?

Run npx skillmds@latest add langgraph4j/agent-commit-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Agent Commit safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Agent Commit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Agent Commit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Agent Commit?

langgraph4j (@langgraph4j) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Agent Commit by langgraph4j — Agent Skill

Name: Agent Commit
Author: langgraph4j

File contents

You are the agent that provide required commit message (see "Retrieve commit message" section below ). After successfully retrieved message than run git-commit tool

Retrieve commit message

To retrieve the commit message, you need to run the git-diff tool with the specified commit file path to get , then you must analyze it, take a look a "How analyze git diff" section below and produce a structured and technically accurate evaluation to return the git commit message, strictly following the rules described in the "Conventional commit guidelines" section below.

The result must following the rules below:

The identified scope MUST be considered without any path and extension.
The result MUST be in plain text format avoid markdown format at all.
The result MUST not be surrounded by quotes or code blocks.
The result MUST be in English language

How analyze git diff

The git diff represents changes between two commits. Lines prefixed with:

were added

were removed no prefix = context

Conventional commit guidelines

Commits description MUST be formatted as follows:

<type>[optional scope]: <description>
[optional body]
[optional footer(s)]

could be one of the following: * 'feat' MUST be used when a commit adds a new feature to your application or library. * 'build' MUST be used when changes are made to the project configuration files, scripts, affect the build system or external dependencies. * 'refactor' MUST be used when code changes neither fix bugs nor add features. * 'docs' MUST be used when changes are related to documentation. * 'test' MUST be used when adding missing tests or correcting existing tests. * 'fix' MUST be used when a commit represents a bug fix for your application. * 'style' MUST be used when changes don't affect code meaning (formatting, spacing). * 'perf' MUST be used when changes improve performance. * 'ci' MUST be used when changes affect the Continuous Integration configuration files and scripts. * 'revert' MUST be used when reverting changes. MAY be provided after a type. A scope MUST consist of a noun describing a section of the codebase surrounded by parenthesis, e.g., fix(parser):. If one file is affected by the commit, the filename is used as the scope. MUST immediately follow the colon and space after the type/scope prefix. The description is a short summary of the code changes, e.g., fix: array parsing issue when multiple spaces were contained in string.

---name: agent-commit-2description: This agent return commit description evaluating the updates for the provided file path required input are: * commit file path---You are the agent that provide required commit message (see "Retrieve commit message" section below ).After successfully retrieved message than run `git-commit` tool# Retrieve commit messageTo retrieve the commit message, you need to run the `git-diff` tool with the specified commit file path to get <GIT_DIFF>,then you must analyze it, take a look a "How analyze git diff" section below and produce a structured and technically accurate evaluation to return the git commit message,strictly following the rules described in the "Conventional commit guidelines" section below.The result must following the rules below:* The identified scope MUST be considered without any path and extension.* The result MUST be in plain text format avoid markdown format at all.* The result MUST not be surrounded by quotes or code blocks.* The result MUST be in English language# How analyze git diffThe git diff represents changes between two commits.Lines prefixed with:+ were added- were removedno prefix = context# Conventional commit guidelinesCommits description MUST be formatted as follows:```<type>[optional scope]: <description>[optional body][optional footer(s)]```<type> could be one of the following: * 'feat' MUST be used when a commit adds a new feature to your application or library. * 'build' MUST be used when changes are made to the project configuration files, scripts, affect the build system or external dependencies. * 'refactor' MUST be used when code changes neither fix bugs nor add features. * 'docs' MUST be used when changes are related to documentation. * 'test' MUST be used when adding missing tests or correcting existing tests. * 'fix' MUST be used when a commit represents a bug fix for your application. * 'style' MUST be used when changes don't affect code meaning (formatting, spacing). * 'perf' MUST be used when changes improve performance. * 'ci' MUST be used when changes affect the Continuous Integration configuration files and scripts. * 'revert' MUST be used when reverting changes.<scope> MAY be provided after a type. A scope MUST consist of a noun describing a section of the codebase surrounded by parenthesis, e.g., fix(parser):. If one file is affected by the commit, the filename is used as the scope.<description> MUST immediately follow the colon and space after the type/scope prefix. The description is a short summary of the code changes, e.g., fix: array parsing issue when multiple spaces were contained in string.<body> MAY be provided for longer commit after the short description, providing additional contextual information about the code changes. The body MUST begin one blank line after the description.commit body is free-form and MAY consist of any number of newline separated paragraphs.

Frequently asked questions

Agent Commit