Files

T

jpmschweitzerandClaude Opus 4.6 7158ae9cf5 feat(meta): add whatsinagame multi-agent team starter kit

Claude-native starter kit that bootstraps multi-agent team
infrastructure for any project. Clone once, install as a global
skill, run /kit-install in any project directory.

Includes:
- 3-tier profile system (minimal/standard/full: 3-12 agents)
- 16 agent archetype templates with personality spectrum
- 18 skill templates using domain-action naming convention
- Stakeholder persona panel for workshops and PR reviews
- SQLite ticketing DB with CLI tools (config-based DB paths)
- Decision tracking, sprint lifecycle, workshop orchestration
- Multi-git-host support (GitHub, Gitea, GitLab)
- /kit-update skill for syncing with source repo evolution
- Naming theme support for agent identity/flavor
- Smoke tests for all three profile tiers

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-02-18 02:22:30 +01:00

2.3 KiB

Raw Blame History

name, description, user-invocable, allowed-tools

name	description	user-invocable	allowed-tools
release-notes	Generate changelog and release notes from conventional commits. Use when the user says "release notes", "changelog", "what shipped", or invokes /release-notes. Parses commits since last tag, groups by type and scope, generates human-friendly summaries.	true	Bash, Read, Grep, Glob, Write, AskUserQuestion

Release Notes Generator

Generate changelog and release notes from conventional commits since the last tagged release.

Workflow

1. Find Range

Determine the commit range to cover:

git tag --sort=-v:refname | head -1

If tags exist, use <last-tag>..HEAD as the range.
If no tags exist, use the initial commit as the starting point.

2. Parse Commits

git log --oneline <last-tag>..HEAD

Extract from each conventional commit:

Type: feat, fix, refactor, chore, docs, test, perf, ci
Scope: the parenthesized scope (e.g., client, server, ui)
Summary: the commit description

3. Group by Type

Organize commits into user-friendly categories:

feat → Added
fix → Fixed
refactor → Changed
chore → Infrastructure
docs → Documentation
perf → Performance
test → Testing

4. Enrich

For each entry, check for references:

Ticket references: #N → link to ticket
Decision references: D-NNN → link to decision file
PR references: associate with merge commits

5. Generate Summaries

Write human-friendly summaries for each entry — not just raw commit messages. Each entry should describe the user-visible change or improvement in plain language.

6. Choose Tone

Ask the user which tone to generate using AskUserQuestion:

Technical: For developers — detailed, references commits, PRs, and specific code changes.
User-facing: For end users — what's new, what's fixed, in plain language with no jargon.
Executive: For stakeholders — high-level themes, business impact, milestone progress.

7. Output

Write the release notes in the chosen format:

Append to CHANGELOG.md under an [Unreleased] section, OR
Write as a standalone file if the user prefers.

Include a header with the version (if tagging) or date, and the total counts per category.

2.3 KiB Raw Blame History