// Show commits since the last tag in a formatted table. Use when user asks "what changed since last release", "commits since last tag", "last-tag", "what's new", or wants to see recent unreleased changes.
| name | last-tag |
| description | Show commits since the last tag in a formatted table. Use when user asks "what changed since last release", "commits since last tag", "last-tag", "what's new", or wants to see recent unreleased changes. |
| allowed-tools | Bash, AskUserQuestion |
Show commits since the last tag in a formatted table with optional details.
Important: Avoid $() command substitution in Bash tool - use sequential steps.
git fetch origin --tags
Then get the last tag:
git describe --tags --abbrev=0
Store this value (e.g., v1.2.3) for use in subsequent commands.
date|author|hash|subject (substitute TAG with actual value):git log TAG..HEAD --format="%ad|%an|%h|%s" --date=short
Check if all commits have the same author - extract unique authors from step 2 output. If only one unique author name appears in all rows, it's a single author.
Format output:
If single author (count = 1):
Last tag: v1.2.3
Author: John Doe
| Date | Commit | Description |
|------------|---------|--------------------------------|
| 2025-12-20 | abc1234 | fix: resolve null pointer |
| 2025-12-19 | def5678 | feat: add user authentication |
If multiple authors (count > 1):
Last tag: v1.2.3
| Date | Author | Commit | Description |
|------------|----------|---------|--------------------------------|
| 2025-12-20 | John Doe | abc1234 | fix: resolve null pointer |
| 2025-12-19 | Jane Doe | def5678 | feat: add user authentication |
If no tag exists:
No tags found in repository
If no commits since tag:
Last tag: v1.2.3
No commits since this tag
After displaying the table, use AskUserQuestion:
question: "Show commit details?"
header: "Details"
options:
- label: "All commits"
description: "Show full details for each commit"
- label: "None"
description: "Skip details"
- label: "Specific commit"
description: "Enter commit hash to inspect"
If "All commits": For each commit, run:
git show --stat --format="Commit: %h%nAuthor: %an <%ae>%nDate: %ad%n%n%s%n%n%b" --date=short HASH
This shows: commit hash, author with email, date, subject, body, and file change stats.
If "None": End.
If "Specific commit" or user enters hash via "Other": Run the same git show command for that commit only.
Execute plan tasks sequentially using subagents. Use when user says 'exec', 'execute plan', 'run plan', or wants to implement a plan file task by task with isolated subagents.
Update project CLAUDE.md with strategic knowledge discovered during this session — or CLAUDE.local.md when the discovery is per-developer/per-checkout and that file already exists. Defers to any project-defined memory-placement guidance instead of overriding it. Use when user says "learn", "save knowledge", "update claude.md", "capture learnings", or at end of significant work sessions. Also used by commit skill for pre-commit knowledge capture.
Consult OpenAI Codex for investigation, debugging, or code review. Use when user explicitly asks to "ask codex", "check with codex", "codex review", or as a last resort when stuck after 4+ failed attempts at debugging, investigation, or bug fix and completely out of ideas. Codex is slow (2-5 min), so only escalate when truly stuck. Codex runs in read-only mode with full project access — it analyzes, we implement.
Use before any creative work or significant changes. Activates on "brainstorm", "let's brainstorm", "deep analysis", "analyze this feature", "think through", "help me design", "explore options for", or when user asks for thorough analysis of changes, features, or architectural decisions. Guides collaborative dialogue to turn ideas into designs through one-at-a-time questions, approach exploration, and incremental validation.
Interactive git diff annotation review. Generates a cleaned-up diff, opens in editor for user annotations, and addresses feedback in a loop. Activates on "git review", "review changes", "review my changes", "annotate changes", "interactive review".
Use when user asks to create a release, cut a release, or publish a version. Auto-detects GitHub vs GitLab vs Gitea, calculates semantic version, generates release notes from PRs/MRs or commits, shows preview for confirmation before publishing.