langgraph4j/agent-commit
langchain4j/langchain4j-agent/src/test/resources/skills/agent-commit/SKILL.md
This agent return commit description evaluating the updates for the provided file path required input are: * commit file path
$ install --global
skillsauthnpx skillsauth add langgraph4j/langgraph4j agent-commitInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 17, 2026, 7:01 AM82.5s1 file scanned
SKILL.md
- name:
- agent-commit
- description:
- |
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 <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 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)]
<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.Related Skills
langgraph4j/.agent/skills/make_readme
documentation
VerifiedTrustedCommunity
--- name: make_readme description: create or update a meaningful readme # What is a README README.md files are for humans: * quick starts, * project descriptions * contribution guidelines. # Structure a README.md must be structured in, at least, the following paragraphs * Getting started * Introduction * Core Features & Benefits * Core Concepts Explained * Project Structure * Installation * A Simple Example * References
1,549SKILL.mdUpdated Apr 15, 2026
langgraph4j/alm-processing
development
VerifiedTrustedCommunity
Use this to perform operations on the langgraph4j project. 1) create a new project release 2) move to next dev release
1,549SKILL.mdUpdated Apr 15, 2026
openclaw/taskflow-inbox-triage
data-ai
VerifiedTrustedCommunity
Example TaskFlow authoring pattern for inbox triage. Use when messages need different treatment based on intent, with some routes notifying immediately, some waiting on outside answers, and others rolling into a later summary.
357,764SKILL.mdUpdated Apr 10, 2026
steipete/taskflow-inbox-triage
data-ai
VerifiedTrustedCommunity
Example TaskFlow authoring pattern for inbox triage. Use when messages need different treatment based on intent, with some routes notifying immediately, some waiting on outside answers, and others rolling into a later summary.
356,423SKILL.mdUpdated Apr 13, 2026