Run any Skill in Manus with one click

Get Started

changes-since-last-release

Stars76

Forks3

UpdatedApril 24, 2026 at 19:56

Summarize all changes in this repository since the most recent release tag.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

halfline

halfline/git-stage-batch

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	changes-since-last-release
description	Summarize all changes in this repository since the most recent release tag.
whenToUse	Use this when the user wants a release summary, changelog draft, or an overview of commits since the latest tagged release.
allowed-tools	Bash(git tag --sort=-creatordate), Bash(git describe --tags --abbrev=0), Bash(git log), Bash(git diff --stat), Bash(git shortlog), Bash(git status --short), Bash(rg), Read
user-invocable	true

Your task is to summarize everything that changed since the last release in this repository.

Workflow:

Find the most recent release tag with git describe --tags --abbrev=0.
If no tag exists, say that clearly and summarize the full project history instead of failing.
Inspect commits in the range <latest-tag>..HEAD.
Inspect the high-level file delta with git diff --stat <latest-tag>..HEAD.
Group the changes into a concise release-oriented summary:
- user-visible features
- fixes
- docs or packaging changes
- internal or refactor work
Include the exact tag and commit range you used.
Call out if the working tree is dirty, but do not mix uncommitted changes into the release summary unless the user explicitly asks.

Output requirements:

Start with Changes since <tag>.
Include a short bullet list of the most important items.
Include a commit count.
Include a compact file-change summary based on git diff --stat.
If helpful, draft a changelog section in markdown.

Do not create tags, commits, or release artifacts unless the user explicitly asks.

More from this repository

same repository

commit-unstaged-changes

halfline/git-stage-batch

Stage unstaged changes into one or more atomic git commits with project-compliant commit messages

2026-06-2676

commit-unstaged-changes

halfline/git-stage-batch

Stage unstaged working tree changes into one or more atomic commits with git-stage-batch. Use when the user wants Codex to split unstaged edits into a clean commit series with project-compliant commit messages. Do not use for already-staged changes or for generic git help.

2026-06-2676

decompose-and-commit-unstaged-changes

halfline/git-stage-batch

Decompose unstaged working-tree changes into narrow concerns, peel them into git-stage-batch batches, rebuild as a fine-grained atomic commit series, or polish an already-built series

2026-06-1676

decompose-and-commit-unstaged-changes

halfline/git-stage-batch

Decompose unstaged working-tree changes into a clean commit series by identifying narrow product, workflow, or architectural concerns, peeling them into git-stage-batch batches, rebuilding atomic commits, or polishing an already-built series.

2026-06-1676

release-tweet-thread

halfline/git-stage-batch

Draft an algorithm-optimized tweet thread announcing the latest release.

2026-05-2576

commit-staged-changes

halfline/git-stage-batch

Commit the current staged index as one project-compliant git commit. Use when the user has already staged the exact changes they want to commit and wants help inspecting that staged set, drafting a compliant message, and creating the commit. Do not use for splitting or staging unstaged changes.

2026-05-1376

name	changes-since-last-release
description	Summarize all changes in this repository since the most recent release tag.
whenToUse	Use this when the user wants a release summary, changelog draft, or an overview of commits since the latest tagged release.
allowed-tools	Bash(git tag --sort=-creatordate), Bash(git describe --tags --abbrev=0), Bash(git log), Bash(git diff --stat), Bash(git shortlog), Bash(git status --short), Bash(rg), Read
user-invocable	true

Your task is to summarize everything that changed since the last release in this repository.

Workflow:

Find the most recent release tag with git describe --tags --abbrev=0.
If no tag exists, say that clearly and summarize the full project history instead of failing.
Inspect commits in the range <latest-tag>..HEAD.
Inspect the high-level file delta with git diff --stat <latest-tag>..HEAD.
Group the changes into a concise release-oriented summary:
- user-visible features
- fixes
- docs or packaging changes
- internal or refactor work
Include the exact tag and commit range you used.
Call out if the working tree is dirty, but do not mix uncommitted changes into the release summary unless the user explicitly asks.

Output requirements:

Start with Changes since <tag>.
Include a short bullet list of the most important items.
Include a commit count.
Include a compact file-change summary based on git diff --stat.
If helpful, draft a changelog section in markdown.

Do not create tags, commits, or release artifacts unless the user explicitly asks.