Analyze git repository release state and backlog for standup recaps.
npx skills add https://github.com/friedbotstudio/baseline --skill standup-friedbotstudio
Please help me install this Agent Skill. Skill: standup Source: https://github.com/friedbotstudio/baseline/tree/main/.claude/skills/standup Command: npx skills add https://github.com/friedbotstudio/baseline --skill standup-friedbotstudio
This Skill gives you a fast, read-only snapshot of where a repository stands so you can plan a release or choose the next thing to build without digging through git history, backlog notes, and memory files by hand.
Ask the standup skill to summarize the repository’s last release, unreleased commits, backlog, and open questions.
High-intent search queries and answers about installing and using this skill.
To get a read-only summary for release planning, analyze the repository's last shipped version, conventional commits since the latest tag, and nested backlog items. This produces a compact standup recap showing what shipped, what is staged, and the semver bump those commits imply.
Conventional commit classification determines the semver bump by reading release rules from .releaserc.json and categorizing commits since the latest tag. It analyzes commit types like features or fixes to imply the correct semantic versioning increment for the next release.
Yes, you can generate a release recap with missing git tags or metadata. The analysis degrades gracefully when repository memory or git data is missing, still providing a read-only snapshot of backlog items and open questions for planning.
The best way to track upstream divergence is to analyze whether your branch is ahead, behind, or aligned with upstream. This read-only repository state awareness shows pending changes and helps you decide what should be tackled next during release planning.
To organize nested backlog items into a compact planning view, bucket work items into open, picked up, and dropped categories. Nest epic children under their parent epics and condense pending questions to quickly understand what should be tackled next.
cristoslcAutomate software releases by bumping versions, generating changelogs, and creating Git tags.
AAbdulghanyDiff dev and main branches to determine SemVer bumps and generate CHANGELOG entries.
nicolasdaoIdentify session changes with git status and commit them using conventional messages.
wildbitcaAutomate Terraform semver releases by inspecting uncommitted .tf changes and existing tags.
