ll-manage-release

Automate git tagging, changelog generation, and GitHub release publishing.

7|2|Updated Jan 3, 2026

Search Tags:#automation #git #changelog #versioning #github #release

Ready to run

npx skills add https://github.com/BrennonTWilliams/little-loops --skill ll-manage-release

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ll-manage-release
Source: https://github.com/BrennonTWilliams/little-loops/tree/main/skills/ll-manage-release
Command: npx skills add https://github.com/BrennonTWilliams/little-loops --skill ll-manage-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual overhead of coordinating git tags, changelog generation, and GitHub release publishing, ensuring consistent versioning across your software lifecycle.

Core Features & Use Cases

Automated Versioning: Automatically creates git tags and manages GitHub release objects.
Changelog Integration: Aggregates completed issues and tasks into structured release notes.
Use Case: When a sprint is complete, use this skill to automatically bump the project version, generate a summary of all resolved issues, and publish the release to GitHub.

Quick Start

Ask the agent to manage the release by creating a new tag and publishing the latest changes to GitHub.

Frequently Asked Questions about ll-manage-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate GitHub release management and git tagging?▼

Automated changelog generation aggregates completed issues and resolved tasks from integrated issue tracking data into structured release notes, ensuring consistent versioning and summarizing all sprint deliverables for the new release.

What's the best way to generate a changelog from completed GitHub issues?▼

Generating a changelog from GitHub issues is handled by integrating issue tracking data with version control operations, aggregating completed tasks into structured release notes, and publishing the summary directly to a new GitHub release object.

Do I need authenticated access to publish a GitHub release and create git tags?▼

Authenticated access to the repository and issue management systems is required to perform stateful release transitions, create git tags, and manage GitHub release objects successfully during the automated software delivery workflow.

Can I use this approach to bump project versions after a sprint is complete?▼

Bumping project versions after a sprint is a supported use case where the skill automatically increments the version, generates a summary of all resolved issues, and publishes the final release to GitHub.

When should I not use automated release management for version control?▼

Automated release management may not be suitable if your repository lacks integrated issue tracking data or if you cannot provide the authenticated access required to perform stateful release transitions across your version control systems.

gricha

release

Automate Perry project releases by versioning, committing, tagging, and pushing to CI.

Community

Intermediate

OpenLabor

Deploy to Production

Automate production deployments with rollback-ready workflows and guardrails.

Official

Advanced

sunholo-data

AILANG Release Manager

Automates end-to-end AILANG release management including pre-release checks, version bumps, changelog updates, git tagging, CI/CD verification, and release broadcasting.

Official

Intermediate