Cursor
31 skills
thermo-nuclear-code-quality-review
Passed all 3 security checks
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.
·02.5k
deslop
Passed all 3 security checks
Remove AI-generated code slop and clean up code style
·0920
fix-merge-conflicts
Passed all 3 security checks
Resolve merge conflicts non-interactively, validate build and tests, and finalize conflict resolution
·0495
make-pr-easy-to-review
Passed all 3 security checks
·022
fix-ci
Passed all 3 security checks
Find failing PR checks, inspect logs or external check links, and apply focused fixes
·021
loop-on-ci
Passed all 3 security checks
Monitor PR checks and fix failures until green. Uses gh pr checks as the source of truth for PR-attached checks.
·021
what-did-i-get-done
Passed all 3 security checks
Summarize authored commits over a user-specified time period into a concise update
·021
check-compiler-errors
Passed all 3 security checks
Run compile and type-check commands and report failures
·021
verify-this
Passed all 3 security checks
Verify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED, NOT VERIFIED, or INCONCLUSIVE.
·020
get-pr-comments
Passed all 3 security checks
Fetch and summarize review comments from the active pull request
·020
new-branch-and-pr
Passed all 3 security checks
Create a fresh branch, complete work, and open a pull request
·020
workflow-from-chats
Passed all 3 security checks
Extract durable working preferences from recent Cursor chats and convert them into skills, rules, or workflow docs. Use when asked to learn preferences, mine feedback, personalize workflows, or generate team/person-specific agent guidance.
·020
review-and-ship
Passed all 3 security checks
Review the current branch for bugs, intent fit, and test coverage; run or write tests; commit focused work; open or update a PR.
·020
pr-review-canvas
Passed all 3 security checks
·020
control-cli
Passed all 3 security checks
Build or adapt a local harness to drive, inspect, and profile an interactive CLI or TUI without external services. Use for CLI UX checks, startup regressions, memory leaks, hangs, prompt flows, or terminal demos.
·020
weekly-review
Passed all 3 security checks
Produce a weekly synthesis of authored commits with highlights by bugfix, tech debt, and net-new work
·020
control-ui
Passed all 3 security checks
Build or adapt a local browser/CDP harness to drive and inspect a web, IDE, or Electron UI. Use for local UI verification, screenshots, accessibility snapshots, perf profiles, visual diffs, or reproducing UI bugs.
·020
run-smoke-tests
Passed all 3 security checks
Run Playwright smoke tests, debug failures, and verify fixes
·020
architect
Passed all 3 security checks
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.
·010
unslop
Passed all 3 security checks
Cut AI tells from any writing. Must always apply.
·08
principle-subtract-before-you-add
Passed all 3 security checks
Apply when sequencing an addition, refactor, or rewrite. Remove dead weight, redundant validators, and stub references first, then build on the simpler base.
·08
principle-laziness-protocol
Passed all 3 security checks
Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.
·08
typescript-best-practices
Passed all 3 security checks
TypeScript best practices. Use when reading or editing any .ts or .tsx file.
·08
why
Passed all 3 security checks
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
·08
interrogate
Passed all 3 security checks
·08
arena
Passed all 3 security checks
Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.
·08
reflect
Passed all 3 security checks
Spawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.
·08
automate-me
Passed all 3 security checks
·08
thermos
Passed all 3 security checks
Launch both thermo-nuclear review subagents in parallel, then synthesize their findings. Use for thermos, double thermo review, or combined bug/security and code-quality branch audits.
·08
principle-prove-it-works
Passed all 3 security checks
Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'
·07
principle-fix-root-causes
Passed all 3 security checks
Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.
·07