V
Voyteck/claude-skill-retro
no SECURITY.md
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
- Star count
- 10 ★ · Voyteck/claude-skill-retro · read from the repository page · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-10-20 · last seen 2026-11-14 · seen 29× · listed by 2 sources
- Score
- score 200 · 10 ★ · 2 sources · repo
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
Voyteck/claude-skill-retro;first catalogued 2026-10-20;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# retro: retrospectives of working with Claude Code
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
English · Polski
A Claude Code plugin that brings an Agile-style continuous improvement process into working with Claude. Every few
working days (recommended: every 2) the retro:
1. reviews commitments from previous retros: were they kept and did they have an effect;
2. gathers evidence from Claude Code transcripts, git and GitHub (user messages, answers to questions,
blocks, refused and failed tool calls by cause, subagents, PRs, CI, size of rules files, tokens and cost at API
prices: context, share of subagents and Opus, wake-ups of long sessions, cloud sessions, cost per 10% of the
plan) and measures writing efficiency: cost by agent role and
model, fix rounds in merged PRs by author model, returns from review and CI, cost and quality per PR by
implementer model, reasoning effort and PR size, compared with the previous 3 retros, to tune which agent, model
and effort does which task;
3. assesses what worked and what did not, also on the user's side (optional);
4. proposes at most 5 changes, preferring mechanisms (tests, hooks, templates) over text-only rules;
5. implements the accepted changes in rules files (CLAUDE.md, memory, nauki.md) and the commitments
register.
If there has been no retro for 5 working days, a new Claude Code session reminds you (SessionStart hook).
Since 0.5.0 retro also replaces the claude-usage-report
skill: its measurements (tokens and context, cache rebuilds, refused tool calls by cause, cloud session cost, cost
per merged PR and per 10% of the plan, comparison with the previous measurement) are part of every retro.
## Languages
The retro talks and writes in the language chosen on first run (jezyk in konfiguracja.json):
pl and en have their own templates and script reports;
any other language: Claude writes in it, templates and script reports are in English.
Recognition does not depend on the language: an option marked as recommended is recognized in many languages
("(Recommended)", „(rekomendowane)”, "(recomendado)", "(empfohlen)", …), a completed retro is zakończone,
completed, done or closed, a question about a fact starts with [fact] or [fakt].
Identifiers stay Polish in every language: file names in the working directory (zobowiazania.md, nauki.md,
konfiguracja.json), configuration keys, CSV columns, script names and arguments. Code comments are in Polish
too. The glossary is in plugins/retro/skills/retro/references/konfiguracja.md.
## Requirements
Claude Code (CLI or the Code tab of the desktop app), local sessions;
Python ≥ 3.8 in PATH (python3, python or py), standard library only;
git; optionally gh logged in to an account with access to the repositories (PR and CI metrics);
bash for the reminder hook (on Windows: Git Bash, which Claude Code requires anyway).
## Installation from the GitHub repo (recommended)
1. In Claude Code, on every account and computer where it should work:
/plugin marketplace add Voyteck/claude-skill-retro
/plugin install retro@retro
The same from a terminal: claude plugin marketplace add Voyteck/claude-skill-retro and
claude plugin install retro@retro.
2. A new session (or /reload-plugins).
Your own copy (a fork or a new repo from this package) installs the same way, with / instead of
A Claude Code plugin that brings an Agile-style continuous improvement process into working with Claude. Every few
working days (recommended: every 2) the retro:
1. reviews commitments from previous retros: were they kept and did they have an effect;
2. gathers evidence from Claude Code transcripts, git and GitHub (user messages, answers to questions,
blocks, refused and failed tool calls by cause, subagents, PRs, CI, size of rules files, tokens and cost at API
prices: context, share of subagents and Opus, wake-ups of long sessions, cloud sessions, cost per 10% of the
plan) and measures writing efficiency: cost by agent role and
model, fix rounds in merged PRs by author model, returns from review and CI, cost and quality per PR by
implementer model, reasoning effort and PR size, compared with the previous 3 retros, to tune which agent, model
and effort does which task;
3. assesses what worked and what did not, also on the user's side (optional);
4. proposes at most 5 changes, preferring mechanisms (tests, hooks, templates) over text-only rules;
5. implements the accepted changes in rules files (CLAUDE.md, memory, nauki.md) and the commitments
register.
If there has been no retro for 5 working days, a new Claude Code session reminds you (SessionStart hook).
Since 0.5.0 retro also replaces the claude-usage-report
skill: its measurements (tokens and context, cache rebuilds, refused tool calls by cause, cloud session cost, cost
per merged PR and per 10% of the plan, comparison with the previous measurement) are part of every retro.
## Languages
The retro talks and writes in the language chosen on first run (jezyk in konfiguracja.json):
pl and en have their own templates and script reports;
any other language: Claude writes in it, templates and script reports are in English.
Recognition does not depend on the language: an option marked as recommended is recognized in many languages
("(Recommended)", „(rekomendowane)”, "(recomendado)", "(empfohlen)", …), a completed retro is zakończone,
completed, done or closed, a question about a fact starts with [fact] or [fakt].
Identifiers stay Polish in every language: file names in the working directory (zobowiazania.md, nauki.md,
konfiguracja.json), configuration keys, CSV columns, script names and arguments. Code comments are in Polish
too. The glossary is in plugins/retro/skills/retro/references/konfiguracja.md.
## Requirements
Claude Code (CLI or the Code tab of the desktop app), local sessions;
Python ≥ 3.8 in PATH (python3, python or py), standard library only;
git; optionally gh logged in to an account with access to the repositories (PR and CI metrics);
bash for the reminder hook (on Windows: Git Bash, which Claude Code requires anyway).
## Installation from the GitHub repo (recommended)
1. In Claude Code, on every account and computer where it should work:
/plugin marketplace add Voyteck/claude-skill-retro
/plugin install retro@retro
The same from a terminal: claude plugin marketplace add Voyteck/claude-skill-retro and
claude plugin install retro@retro.
2. A new session (or /reload-plugins).
Your own copy (a fork or a new repo from this package) installs the same way, with / instead of
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/voyteck-claude-skill-retro/)
- Source
- github · https://github.com/Voyteck/claude-skill-retro
- Browse by field
- Open source
- Traction
- 10 ★
- Listed by
- 2 independent sources
- added
- today
- Security policy
- no
SECURITY.mdat the repository root (which does not mean it is unsafe)
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.