Agent skill

Retro

by Houseofmvps in Houseofmvps/ultraship

Sprint retrospective — analyzes git velocity, commit patterns, test health, and shipping cadence.

MITAuto-check: notesProduct & Project Management

Install Retro

skills CLI
$ npx skills add Houseofmvps/ultraship --skill retro -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Houseofmvps/ultraship retro --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Houseofmvps/ultraship.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/retro .claude/skills/retro && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
retro
GitHub stars
123
Token cost
~882 tokens
SKILL.md length
308 words
Files
1
Skills in repo
28
Repo updated
First seen
Licence
MIT

At a glance

Sprint retrospective — analyzes git velocity, commit patterns, test health, and shipping cadence.

  • Works in 4 steps: Gather Data → Present the Retrospective → Insights & Recommendations → …
  • Wants to reflect on progress
  • SKILL.md covers Process, Multi-Project Mode and Output
  • Calls node

What it does

Retro is an agent skill from Houseofmvps/ultraship. Sprint retrospective — analyzes git velocity, commit patterns, test health, and shipping cadence. Use after a sprint, at the end of the week, or when the user wants to reflect on progress.

Its SKILL.md is about 880 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering Retrospectives. It works with Git. The repository describes itself as: "ULTRASHIP" Claude Code plugin — 39 skills, 33 tools, 11 agents for ship-ready workflows: planning, review, pentesting, safety guardrails, canary monitoring, SEO/AI-readiness… The licence is MIT.

When your agent uses it

  • Wants to reflect on progress
  • Tasks that involve Retrospectives

Example prompts

  • “/retro”

Requirements

  • Pre-approved tools (allowed-tools): Bash, Read, Grep, Glob

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Gather Data
  2. Present the Retrospective
  3. Insights & Recommendations
  4. Cross-Reference with Learnings (Optional)

What it can do on your machine

Read from SKILL.md and the folder at commit ed232cb. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Read
    • Grep
    • Glob

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Retro loads about 882 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 308 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~49
When it runs · the whole SKILL.md, loaded when a task matches
~882

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Read, Grep, Glob

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Houseofmvps/ultraship at commit ed232cb, republished under its MIT licence (© Houseofmvps). 308 words, ~882 tokens.

Download SKILL.mdSave it as .claude/skills/retro/SKILL.md (or your agent's skills folder).
name
retro
description
Sprint retrospective — analyzes git velocity, commit patterns, test health, and shipping cadence. Use after a sprint, at the end of the week, or when the user wants to reflect on progress.
allowed-tools
Bash, Read, Grep, Glob
argument-hint
<days-back>

Sprint Retrospective

Retrospectives turn shipping data into actionable insights. This skill analyzes your git history, commit patterns, test health, and shipping velocity to surface what's working and what needs attention.

Announce at start: "I'm running a sprint retrospective on this project."

Process

Step 1: Gather Data

Run the retro analyzer:

bash
node ${CLAUDE_PLUGIN_ROOT}/tools/retro-analyzer.mjs <project-directory> --days 7

For custom date ranges:

bash
node ${CLAUDE_PLUGIN_ROOT}/tools/retro-analyzer.mjs <project-directory> --since 2026-03-24
Step 2: Present the Retrospective

Format the data as a clear, actionable report:

Velocity Report Card
+===========================================+
|     S P R I N T   R E T R O              |
+===========================================+
|  Period        Mar 24 – Mar 31           |
|  Commits       47                         |
|  Lines Added   2,341                      |
|  Lines Removed 892                        |
|  Net Change    +1,449                     |
|  Authors       1                          |
+===========================================+
Commit Breakdown

Show the distribution of commit types (features, fixes, refactors, tests, docs, chores) as a visual breakdown. Highlight the feature-to-fix ratio — a healthy project ships more features than fixes.

Hot Files

List the most-changed files. Files with excessive churn may need to be split into smaller modules.

Test Health
  • Number of test files
  • Passing / failing tests
  • Whether a test script exists
  • Recommendation if tests are absent or failing
Shipping Cadence
  • Peak day of week (when do you ship most?)
  • Peak hour (when are you most productive?)
  • Tags/releases in this period
Step 3: Insights & Recommendations

Based on the data, surface:

What went well:

  • High velocity periods
  • Good deletion-to-addition ratio (code hygiene)
  • Consistent shipping cadence
  • Test coverage improvements

What needs attention:

  • Fix-heavy sprints (more fixes than features = quality debt)
  • Hot files that churn excessively
  • Missing or failing tests
  • Uneven shipping cadence (feast-or-famine pattern)

Action items:

  • Concrete, specific recommendations with clear next steps
  • Link to relevant Ultraship skills (e.g., "Use /tdd for the untested module")
Step 4: Cross-Reference with Learnings (Optional)

If the project has learnings (from /learn), search for relevant context:

bash
node ${CLAUDE_PLUGIN_ROOT}/tools/learnings-manager.mjs search --query "sprint"
node ${CLAUDE_PLUGIN_ROOT}/tools/learnings-manager.mjs search --query "debugging"

Incorporate past learnings into recommendations.

Multi-Project Mode

For founders running multiple projects, run retros across all of them:

bash
node ${CLAUDE_PLUGIN_ROOT}/tools/retro-analyzer.mjs ~/project-a --days 7
node ${CLAUDE_PLUGIN_ROOT}/tools/retro-analyzer.mjs ~/project-b --days 7

Compare velocity across projects to understand where time is being spent.

Output

The retrospective should be concise and actionable — not a data dump. Lead with insights, support with data. The goal is to help the user ship better next week.

© Houseofmvps, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/retro of Houseofmvps/ultraship.

Open the folder on GitHubat commit ed232cb

Compare with similar skills

Retro next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Retro compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Retro this skillHouseofmvps/ultraship123—~882Automated safety check: NotesMIT
Weekly Engineering Retrogarrytan/gstack136k—~2.4kAutomated safety check: PassMIT
Dough Story Wrap Upterryyin/lizard2.6k—~4.3kAutomated safety check: PassCustom licence
Gitea Workflowjwynia/agent-skills169—~3.8kAutomated safety check: PassMIT
Retrokoolamusic/claudefiles130—~2.8kAutomated safety check: PassMIT
ObituaryFactory-AI/cursed-plugins106—~1.2kAutomated safety check: NotesApache-2.0

Similar skills

  • Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.

    136k GitHub stars~2.4k tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Dough Story Wrap Up

    terryyin/lizard

    Closes one completed feature story, bounded retrospective correction, or context-only planless execution using available execution context.

    2.6k GitHub stars~4.3k tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed
  • Gitea Workflow

    jwynia/agent-skills

    Orchestrate agile development workflows for Gitea repositories using the tea CLI.

    169 GitHub stars~3.8k tokensUpdated 7 mo ago
    Product & Project ManagementAuto-check passed
  • Retro

    koolamusic/claudefiles

    A skill your agent uses when a user completes a phase, sprint, milestone, or meaningful unit of work and needs a retrospective.

    130 GitHub stars~2.8k tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Obituary

    Factory-AI/cursed-plugins

    Retrospective on deprecated and end-of-life code. An agent skill from Factory-AI/cursed-plugins.

    106 GitHub stars~1.2k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check: notes
  • Collab Proof

    alirezarezvani/claude-skills

    A skill your agent uses when you want to understand what Claude contributed vs what you drove in a session.

    28k GitHub stars~3.6k tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check passed

More from Houseofmvps/ultraship

All 28 skills in this repo
  • Using Ultraship

    Houseofmvps/ultraship

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    123 GitHub stars~2.2k tokensUpdated 3 mo ago
    Auto-check passed
  • A11y

    Houseofmvps/ultraship

    Accessibility audit + auto-fix (WCAG 2.2 A/AA). An agent skill from Houseofmvps/ultraship.

    123 GitHub stars~1.2k tokensUpdated 3 mo ago
    Auto-check: notes
  • Architecture

    Houseofmvps/ultraship

    Living Architecture Map — auto-generate Mermaid diagrams of your codebase.

    123 GitHub stars~708 tokensUpdated 3 mo ago
    Auto-check: notes
  • Clone Patterns

    Houseofmvps/ultraship

    Learn From the Best — analyze patterns from any codebase and apply them to yours.

    123 GitHub stars~682 tokensUpdated 3 mo ago
    Auto-check: notes
  • Code Review

    Houseofmvps/ultraship

    Code review with principal-engineer-level depth. An agent skill from Houseofmvps/ultraship.

    123 GitHub stars~1.5k tokensUpdated 3 mo ago
    Auto-check passed
  • Compete

    Houseofmvps/ultraship

    Competitive X-Ray — analyze any competitor URL vs your site.

    123 GitHub stars~1.1k tokensUpdated 3 mo ago
    Auto-check: notes

Works with

Questions about Retro

What does Retro do?

Sprint retrospective — analyzes git velocity, commit patterns, test health, and shipping cadence. Retro is an agent skill from Houseofmvps/ultraship. Sprint retrospective — analyzes git velocity, commit patterns, test health, and shipping cadence.

When should I use Retro?

Retro fits situations like: wants to reflect on progress; tasks that involve Retrospectives.

How do I install Retro in Claude Code?

Run `npx skills add Houseofmvps/ultraship --skill retro -a claude-code`. Or copy the skill folder (skills/retro in Houseofmvps/ultraship) into .claude/skills/retro in your project. Claude Code loads it when a task matches its description.

How do I install Retro in Codex?

Run `npx skills add Houseofmvps/ultraship --skill retro -a codex`. Or copy the skill folder (skills/retro in Houseofmvps/ultraship) into .agents/skills/retro in your project. Codex loads it when a task matches its description.

Can I use Retro in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Houseofmvps/ultraship --skill retro -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/retro, .gemini/skills/retro, .github/skills/retro and .opencode/skills/retro in your project.

What does Retro need to run?

Going by SKILL.md and its folder, Retro needs the command-line tools its instructions call (node). Its frontmatter pre-approves these tools: Bash, Read, Grep, Glob.

Does Retro access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Retro safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Retro use?

Retro is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Retro use?

About 882 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Retro?

Skills that share tags, products or a category with Retro: Weekly Engineering Retro (garrytan/gstack, 136k stars), Dough Story Wrap Up (terryyin/lizard, 2.6k stars), Gitea Workflow (jwynia/agent-skills, 169 stars) and Retro (koolamusic/claudefiles, 130 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Retro?

Houseofmvps (a GitHub user) maintains it in Houseofmvps/ultraship, which has 123 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on July 8, 2026.

Source: Houseofmvps/ultraship on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.