mit einem Klick
config
config enthält 11 gesammelte Skills von lettertwo, mit Repository-Berufsabdeckung und Skill-Detailseiten auf SkillsMP.
Skills in diesem Repository
Review the changes since a fixed point (commit, branch, tag, or merge-base) along up to three axes — Correctness (real runtime defects), Standards (does the code follow this repo's documented coding standards?), and Spec (does the code match what the originating issue/PRD asked for?). Runs the axes as parallel, adversarially-verified sub-agents via the Workflow tool and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
Scaffold a new JavaScript/TypeScript project with the preferred pnpm setup (worktree-agnostic store, symlinked executables). Use when creating a greenfield JS/TS project.
Configure this repo with its issue tracker and domain doc layout. Run once before first use of the other skills.
A relentless interview to sharpen a plan or design.
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
Parallel code review (and optional autofix) of the current branch and every branch stacked upstack of it, each scoped to its own parent diff. Runs /code-review's shared workflow once per branch over a Graphite stack. Use when you want to review (and optionally fix) the current branch and its stack. Pass --upstack to skip the current branch and review only descendants.
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.