Skip to content
SkillCheatSheet Sign in

ce-retro

An AI agent skill from EveryInc/compound-engineering-plugin, scored 65 out of 100 by code.

65/ 100C

Code score by group

  • Spec20/20
  • Description5/20
  • Procedure15/15
  • Done criteria4/15
  • Resources6/10
  • Scripts5/8
  • Safety7/7
  • Upkeep3/5

It loses the most points in Description (15), the group that checks whether the description says what the skill does and when to use it.

What the author says it does

Look back over an agent session in this repo, the current one by default or any scope the user names across harnesses, and find what in the repo's environment keeps costing agents effort or leading them into mistakes, keeping only fixes the evidence shows are worth it. Lands the approved environment fixes and hands the rest to their owners. Use for a retro, postmortem, or papercut sweep of how agents worked in this repo. Use ce-compound to keep the lesson of one solved problem, and ce-debug for a bug in product code.

This is the description in the skill's own SKILL.md, written by its author, not by SkillCheatSheet.

Repository
EveryInc/compound-engineering-plugin
Folder
skills/ce-retro
License
MIT
GitHub stars
26,039
SKILL.md lines
49
Other files
12

Add ce-retro to your agent

npx skills add EveryInc/compound-engineering-plugin --skill ce-retro

The command uses the open skills CLI. A skill is instructions and scripts your agent will follow, so read it first: open the folder on GitHub at the commit that was scored.

More skills from EveryInc/compound-engineering-plugin

  1. ce-code-review

    Review a named diff or PR for bugs, regressions, tests, and standards. Use when asked to review code or when a shipping skill needs a review receipt. Use when asked to apply this…

    70B
  2. ce-handoff

    Create a session handoff for another agent, or resume, find, and read any user-selected continuity source. Use when work or conversation must continue without access to the curren…

    70B
  3. ce-optimize

    Optimize a named target with a measured loop: attribute a workload's cost, or score variants and keep winners. Use when a working system's metric should move and the winning chang…

    70B
  4. ce-simplify-code

    Simplify code for clarity, reuse, quality, and efficiency while preserving behavior, and prune tests and comments that carry no value. Use after implementation and before review,…

    70B
  5. ce-test-browser

    Run browser tests for pages affected by the current branch or PR. Use when asked to run or check browser tests for the current change.

    70B
  6. ce-worktree

    Set up isolated git worktrees — create a new branch for fresh work, or attach a worktree to an existing branch, PR, or commit. Use when starting isolated work or isolating an exis…

    70B
  7. ce-debug

    Diagnosis loop for bugs and failing behavior. Use when asked to debug or fix failing or slow behavior.

    69C
  8. ce-commit-push-pr

    Commit, push, and open a PR. Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.

    68C

All skills in EveryInc/compound-engineering-plugin

Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.