AL

alm-processing

Automates release management tasks for the langgraph4j project.

Install

mkdir -p .claude/skills/alm-processing && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/6580" && unzip -o skill.zip -d .claude/skills/alm-processing && rm skill.zip

Installs to .claude/skills/alm-processing

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Use this to perform operations on the langgraph4j project. 1) create a new project release 2) move to next dev release
118 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Create ad-hoc release branches
  • Update Java project versions
  • Close release branches
  • Generate and update CHANGELOG.md

How it works

The skill automates the git flow release process by creating branches, updating Maven versions, committing changes, and generating changelogs.

Inputs & outputs

You give it
Version number for release
You get back
Updated project version and changelog

When to use alm-processing

  • Create a new project release
  • Increment development version
  • Manage release cycle transitions

About this skill

create a new project release

In this project we follow the "git flow" branching strategy. To create a new release we need to start from develop branch and accomplish the workflow outlined below:

1. Create a ad-hoc release branch.

Starting from develop branch and runs the command git flow release start "<version>" that will create a branch from develop named release\<version>.

2. Update project release

After created successfully the release branch we must update the java project release runs the command mvn versions:set -DnewVersion=<version>. After the command successfully completed we must to confirm changes in pom.xml files runs command mvn version:commit

3. commit the release update

After update java project release we must commit to git runs commands

git add . ; git commit -m'build: bump to next version <version>'

4. wait for confirmation

At this point pause execution and ask to the user when ready to close the release, When he confirms proceed to next steps

5. close release

To close the release runs git flow release finish "<version>" -m"new release <version>" that will merge the branch release/<version> to both main and develop ones

6. update change log

To update change log follow the steps below :

6.1 create an hotfix branch to work on changelog

exec command git flow hotfix start changelog

6.2 generate CHANGELOG.md

exec command git-changelog-command-line -of CHANGELOG.md

6.3 commit changes

exec command git commit -m'docs: update changelog' -a

6.4 finish the hotfix without create tag

exec command git flow hotfix finish changelog -n -m"changelog hotfix merge"

When not to use it

  • When not working on the langgraph4j project
  • When the current branch is not develop

Prerequisites

Git flow

Limitations

  • Specific to the langgraph4j project
  • Requires git flow and maven

How it compares

It standardizes the release workflow for the langgraph4j project, reducing manual steps in versioning and changelog maintenance.

Compared to similar skills

alm-processing side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
alm-processing (this skill)15moNo flagsIntermediate
workflow-orchestration-patterns102moNo flagsAdvanced
review-pr22moNo flagsAdvanced
ignite-cluster-setup17moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry