@cursor
Internal workflows used by Cursor developers for CI, code review, shipping, control-cli, control-ui, verify-this, test reliability, code cleanup, and work summaries. Designed to work without requiring third-party service integrations.
Run compile and type-check commands and report failures
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.
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.
Remove AI-generated code slop and clean up code style
Find failing PR checks, inspect logs or external check links, and apply focused fixes
Resolve merge conflicts non-interactively, validate build and tests, and finalize conflict resolution
Fetch and summarize review comments from the active pull request
Monitor PR checks and fix failures until green. Uses gh pr checks as the source of truth for PR-attached checks.
Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for "make this easy to review", "tidy this PR", "clean up commits", or "annotate the diff".
Create a fresh branch, complete work, and open a pull request
Generate an interactive PR review walkthrough as an HTML page. Fetches PR data via gh API, categorizes files into core vs mechanical changes, adds reviewer annotations, and renders diffs with moved-code detection. Use when the user pastes a GitHub PR URL and asks for a review, walkthrough, or summary, or says "review this PR".
Review the current branch for bugs, intent fit, and test coverage; run or write tests; commit focused work; open or update a PR.
Run Playwright smoke tests, debug failures, and verify fixes
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.
Verify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED, NOT VERIFIED, or INCONCLUSIVE.
Produce a weekly synthesis of authored commits with highlights by bugfix, tech debt, and net-new work
Summarize authored commits over a user-specified time period into a concise update
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.