New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Retro

by apmantza in apmantza/pi-lens

Run the pi-lens retrospective — turn a session, an incident, or a merged bug fix into environment changes (checks, hooks, contract lines, deletions), classified mechanical-vs-judgement, each with…

MITAuto-check passedDevelopment

Install Retro

skills CLI
$ npx skills add apmantza/pi-lens --skill retro -a claude-code

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

GitHub CLI
$ gh skill install apmantza/pi-lens 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/apmantza/pi-lens.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/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
465
Token cost
~531 tokens
SKILL.md length
252 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

Run the pi-lens retrospective — turn a session, an incident, or a merged bug fix into environment changes (checks, hooks, contract lines, deletions), classified mechanical-vs-judgement, each with…

  • Works in 7 steps: Read docs/pi-lens-retro.md in full, then… → Collect candidates by category; skip… → Classify each candidate mechanical or… → …
  • Tasks that involve Retrospectives
  • SKILL.md covers Invoke, Steps and Do not
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Retro is an agent skill from apmantza/pi-lens. Run the pi-lens retrospective — turn a session, an incident, or a merged bug fix into environment changes (checks, hooks, contract lines, deletions), classified mechanical-vs-judgement, each with its red transcript or an issue naming the recurrence. Use at every regroup, after any merged bug fix, on the second round on one defect shape, or when asked "what should we change so this does not recur".

Its SKILL.md is about 530 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 Development, covering Retrospectives and Debugging. The repository describes itself as: Real-time code feedback for pi — LSP, linters, formatters, structural analysis. The licence is MIT.

When your agent uses it

  • Tasks that involve Retrospectives
  • Tasks that involve Debugging

Example prompts

  • “what should we change so this does not recur”
  • “/retro”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Read docs/pi-lens-retro.md in full, then the inputs it names for the
  2. Collect candidates by category; skip categories with no evidence.
  3. Classify each candidate mechanical or judgement. Mechanical is the default.
  4. Mechanical: build the check now when it is contained (governance test,
  5. Steering audit: every no-op line names the decision it changed or is
  6. Record one mistake row per distinct mistake in
  7. Report the fixed-shape table (Finding, Evidence, Class, Deliverable,

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    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 531 tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 252 words of instructions outside code blocks.

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

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 passed

The automated check found no risky patterns in SKILL.md.

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 apmantza/pi-lens at commit c934da8, republished under its MIT licence (© apmantza). 252 words, ~531 tokens.

Download SKILL.mdSave it as .claude/skills/retro/SKILL.md (or your agent's skills folder).
name
retro
description
Run the pi-lens retrospective — turn a session, an incident, or a merged bug fix into environment changes (checks, hooks, contract lines, deletions), classified mechanical-vs-judgement, each with its red transcript or an issue naming the recurrence. Use at every regroup, after any merged bug fix, on the second round on one defect shape, or when asked "what should we change so this does not recur".

Retro

Source of truth: docs/pi-lens-retro.md. This file is the invocation procedure; on any conflict the contract wins.

Invoke

/retro with no argument runs over the current session's ledger and transcripts. /retro <PR|issue|run id|"incident: ..."> scopes it to one incident. The retro is read-only on the repo except for the outputs the contract names.

Steps

  1. Read docs/pi-lens-retro.md in full, then the inputs it names for the scope: ledger, transcripts, PR bodies and verdicts, CI logs on the exact head.
  2. Collect candidates by category; skip categories with no evidence.
  3. Classify each candidate mechanical or judgement. Mechanical is the default.
  4. Mechanical: build the check now when it is contained (governance test, hook, CI job, preflight row) and paste its red on the incident's shape and its mutation transcript; otherwise file it with the recurrence named. Judgement: one line in the catalog or the owning role contract.
  5. Steering audit: every no-op line names the decision it changed or is deleted.
  6. Record one mistake row per distinct mistake in docs/pi-lens-merge-policy.md ("Common mistakes").
  7. Report the fixed-shape table (Finding, Evidence, Class, Deliverable, Status) ordered by severity, and the list of changes made or filed. When delegated without Git authority, hand off through RETRO.md at the worktree root.

Do not

  • Ship a check without its red transcript.
  • Write a rule for a mechanical mistake.
  • Create a new home for rules; the catalog, the role contracts, and the merge-policy mistake table are the only three.
  • Mix the retro with implementation or review in one delegation.

© apmantza, 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 .claude/skills/retro of apmantza/pi-lens.

Open the folder on GitHubat commit c934da8

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 skillapmantza/pi-lens465—~531Automated safety check: PassMIT
Experiment CraftEvoScientist/EvoSkills4763 repos~2kAutomated safety check: PassApache-2.0
Retrobitsocialnet/5chan135—~865Automated safety check: PassGPL-3.0
Dough Landterryyin/lizard2.6k—~3.8kAutomated safety check: PassCustom licence
Fixgenkovich/sdd171—~2.5kAutomated safety check: PassMIT
PR Review Cycle RetrovictorGPT/vibeusage130—~1.4kAutomated safety check: PassMIT

Similar skills

  • Experiment Craft

    EvoScientist/EvoSkills

    A skill your agent uses when the user wants to debug, diagnose, or systematically iterate on an experiment that already exists, or when they need a structured experiment log for tracking runs…

    476 GitHub starsUsed in 3 repos~2k tokens
    DevelopmentAuto-check passed

  • Retro

    bitsocialnet/5chan

    Review a coding session, bug fix, or substantive review correction for evidence-backed ways to prevent recurrence, using existing checks and focused guidance.

    135 GitHub stars~865 tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Dough Land

    terryyin/lizard

    Dough Land lands everything in one reviewed checkout on the authorized remote trunk: commits all of its changes, reconciles and publishes them without force, and refreshes a supplied default…

    2.6k GitHub stars~3.8k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Fix

    genkovich/sdd

    A skill your agent uses to fix a reported bug spec-first: reproduce it, trace the symptom to the owning feature's acceptance criteria, pin it with a failing (RED) test, apply the minimal GREEN fix…

    171 GitHub stars~2.5k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • PR Review Cycle Retro

    victorGPT/vibeusage

    A skill your agent uses when a team sees repeated @codex review cycles or Codex Cloud feedback churn and needs root-cause attribution by development stage.

    130 GitHub stars~1.4k tokensUpdated 2 mo ago
    DevelopmentAuto-check passed

  • Change Traceability Review

    QoderAI/better-harness

    A skill your agent uses for change traceability review across specs, commits, PRs, branches, local diffs, and git history, including Spec Preparation, Review Readiness Checks, and Review…

    2.4k GitHub stars~559 tokensUpdated yesterday
    DevelopmentAuto-check passed

More from apmantza/pi-lens

  • Pi Lens Ast Grep

    apmantza/pi-lens

    A skill your agent uses when searching or replacing code patterns - use ast-grep instead of text search for semantic accuracy

    465 GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Pi Lens Write Ast Grep Rule

    apmantza/pi-lens

    A skill your agent uses when writing a new pi-lens ast-grep rule YAML file — covers schema, drop path, gotchas, and NAPI runner constraints

    465 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Pi Lens Write Tree Sitter Rule

    apmantza/pi-lens

    A skill your agent uses when writing a new pi-lens tree-sitter query rule YAML file — covers schema, S-expression syntax, capture names, predicates, and gotchas

    465 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Pi Lens Lsp Navigation

    apmantza/pi-lens

    Navigate code with IDE features and run proactive LSP diagnostics on files/folders/batches.

    465 GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Release QA

    apmantza/pi-lens

    Run the pi-lens release-readiness QA pass — witness the feature × modality matrix against a real pi, count coverage, and issue a ship / ship-with-caveats / don't-ship / blocked line.

    465 GitHub stars~2.6k tokensUpdated today
    Auto-check passed

Categories

Questions about Retro

What does Retro do?

Run the pi-lens retrospective — turn a session, an incident, or a merged bug fix into environment changes (checks, hooks, contract lines, deletions), classified mechanical-vs-judgement, each with…. Retro is an agent skill from apmantza/pi-lens. Run the pi-lens retrospective — turn a session, an incident, or a merged bug fix into environment changes (checks, hooks, contract lines, deletions), classified mechanical-vs-judgement, each with its red transcript or an issue naming the recurrence.

When should I use Retro?

Retro fits situations like: tasks that involve Retrospectives; tasks that involve Debugging.

How do I install Retro in Claude Code?

Run `npx skills add apmantza/pi-lens --skill retro -a claude-code`. Or copy the skill folder (.claude/skills/retro in apmantza/pi-lens) 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 apmantza/pi-lens --skill retro -a codex`. Or copy the skill folder (.claude/skills/retro in apmantza/pi-lens) 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 apmantza/pi-lens --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?

SKILL.md names no scripts, command-line tools or credentials: Retro is instructions for the agent only.

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 no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. 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 531 tokens (SKILL.md is roughly 2.1k 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: Experiment Craft (EvoScientist/EvoSkills, 476 stars), Retro (bitsocialnet/5chan, 135 stars), Dough Land (terryyin/lizard, 2.6k stars) and Fix (genkovich/sdd, 171 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Retro?

apmantza (a GitHub user) maintains it in apmantza/pi-lens, which has 465 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 9, 2026.

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