EveryInc/compound-engineering-plugin

Agent skills in the GitHub repository EveryInc/compound-engineering-plugin, each with its code score out of 100.

Official Compound Engineering plugin for Claude Code, Codex, Cursor, and more

Repository score

67 / 100 C

Skills

39

Verified

0

Average skill score

62

GitHub stars

26,039

License

MIT

Open EveryInc/compound-engineering-plugin on GitHub

39 skills in this repository

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
9. ce-explain

   Explain how and why something has its current shape, or what happened over a window of work, grounded in evidence. Use when the user asks for an explanation. Use ce-pov for a judg…

   68C
10. ce-plan

    Create structured plans for multi-step work, including software and non-software tasks. Use when asked to plan, break down implementation, plan from requirements, or deepen an exi…

    68C
11. ce-setup

    Check Compound Engineering's tools and repo config and fix what it finds, scaffold a Compound Pack with `pack:<id>`, or draft and refresh coding standards and review docs from pul…

    68C
12. ce-strategy

    Create or update STRATEGY.md. Use when starting a product, adding a strategy doc, or changing direction or roadmap.

    68C
13. ce-commit

    Create a git commit with a clear, value-communicating message. Use when the user asks to commit/save staged or unstaged changes with a repo-appropriate message.

    67C
14. ce-work

    Execute a plan or concrete work prompt end-to-end. Use when implementing from a plan document, a spec path, or a clear build request; use ce-debug for open-ended bugs. Use when an…

    67C
15. ce-proof

    Publish, read, comment on, or edit markdown in Proof. Use for Proof links, sharing specs/plans/drafts, or publish handoffs from planning workflows; avoid proofread, math, evidence…

    66C
16. ce-product-pulse

    Generate time-windowed product pulse reports from configured signals.

    65C
17. ce-prototype

    Build a throwaway prototype to answer how something should work, feel, or read. Use when committing the wrong answer would be expensive to unravel and a cheap sketch cannot settle…

    65C
18. ce-retro

    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…

    65C
19. ce-ideate

    Generate and evaluate grounded ideas. Use when the user wants ideas, improvements, or surprising directions before choosing one to develop. Not for refining an idea they already h…

    64C
20. ce-noslop

    Rewrite, check, or draft prose so it carries no AI writing tells, reads plainly on the first read, and keeps every source fact. Use when asked to make writing plainer or free of t…

    64C
21. ce-pov

    Judge a supplied subject against the project's evidence and constraints. Use when assessing an external-adoption question, a holistic take on a document, or a supplied approach se…

    63C
22. ce-doc-review

    Review requirements, plans, or specs with role-specific lenses. Use when the user wants to improve an existing planning document.

    62C
23. ce-babysit-pr

    Babysits an open GitHub PR until merge-ready, first judging whether an old PR still belongs. Use when asked to watch a PR over time or update an old one — not for one-shot comment…

    61C
24. ce-brainstorm

    Explore vague or ambitious ideas into a right-sized requirements-only unified plan. Use when the user wants to brainstorm or scope what to build. Not for executing already-specifi…

    60C
25. ce-skill-work

    Applies this repository's skill-authoring standard as a procedure. Use for any change to, or judgment about, a file under skills/** — a SKILL.md, a reference, a persona prompt, a…

    60C
26. ce-test-xcode

    Test iOS apps in a simulator with XcodeBuildMCP. Use when iOS changes need simulator evidence before handoff.

    60C
27. lfg

    Take a request all the way to done, hands-off, through the right Compound Engineering skills. A code change ends as an open pull request, pushed without stopping. Use only when th…

    59C
28. wtf

    Explain the last message, or a supplied file, link, or passage, in plain language a person follows on the first read. Use when the user invokes wtf because they did not follow som…

    59C
29. ce-polish

    Polish a working feature through user-directed live browser feedback. Use when a functional feature needs focused UX refinement before shipping.

    58C
30. ce-sweep

    Sweep configured feedback sources (Slack, GitHub Issues; email experimental) for new items: acknowledge at source, analyze recordings, verify fixes merged to main, and emit an `lf…

    58C
31. ce-compound

    Capture a solved problem's lesson in its cheapest durable form, a test or lint rule, a coding standard, or a repo learning, or refresh existing learnings against the codebase. Use…

    57C
32. ce-bakeoff

    Develop independent competing solutions to a defined brief, compare them, and synthesize a winning approach. Use when choosing well requires developing alternatives beyond their c…

    56C
33. ce-promote

    Draft launch or promotion copy for a shipped feature.

    56C
34. ce-riffrec-feedback-analysis

    Analyze recorded product feedback into evidence for bugs and requirements. Use when a Riffrec capture or other screen, voice, or notes artifact needs interpretation. Use for Riffr…

    56C
35. ce-resolve-pr-feedback

    Judge PR feedback centrally, apply valid fixes, and complete review conversations with publication verified. Use when addressing feedback already left on a PR, preparing local fix…

    53D
36. ce-help

    Help and orientation for Compound Engineering: place the user's work on the compounding loop and recommend the next command, without running it. Use when the user invokes ce-help…

    52D
37. ce-retune

    Retune a skill corpus for a new model, measurement-first: mine the run archive for a baseline, establish a noise floor, audit the corpus adversarially, then cut in measured passes…

    52D
38. ce-compound-refresh

    Old name for refreshing learnings, which now lives in `ce-compound`. Use only when a prompt or standing instruction names `ce-compound-refresh`; use `ce-compound` for every other…

    51D
39. ce-dogfood

    Hands-off, diff-scoped browser QA of the active branch: maps user flows, drives a real browser, autonomously fixes small breakages with regression tests and commits, judges experi…

    48D

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.