advisor
Advisor mode. Consult a stronger (or different) model at key checkpoints: before major decisions, when stuck on an error, andโฆ
Review one or more PRs in Dylan's style: up to 7 copy-pasteable asks and one ๐ข/๐ก/๐ด call. Quick by default; "deep" adds thermos and Bugbot. Use for /dyl-review, "review this PR like me", or terse design/correctness comments. Never posts to the PR.
Claude Code
$ npx -y skills add cursor/plugins --skill dyl-review --agent claude-code
Codex
$ npx skills add cursor/plugins --skill dyl-review -a codex -y
Cursor
$ npx skills add cursor/plugins --skill dyl-review -a cursor -y
Gemini CLI
$ npx skills add cursor/plugins --skill dyl-review -a gemini-cli -y
GitHub Copilot
$ npx skills add cursor/plugins --skill dyl-review -a github-copilot -y
OpenCode
$ npx skills add cursor/plugins --skill dyl-review -a opencode -y
Windsurf
$ npx skills add cursor/plugins --skill dyl-review -a windsurf -y
name: dyl-review description: >- Review one or more PRs in Dylan's style: up to 7 copy-pasteable asks and one ๐ข/๐ก/๐ด call. Quick by default; "deep" adds thermos and Bugbot. Use for /dyl-review, "review this PR like me", or terse design/correctness comments. Never posts to the PR. disable-model-invocation: true icon: search color: blue
Produce a draft PR review the human can paste. This is the one review: thermos and Bugbot run inside it at deep depth, never as separate steps.
Input: one or more PR links or numbers. Multiple PRs get one review block each.
**Requires** `pstack`, plus `thermos` at deep depth. Check first with [../dyl-mode/references/requirements.md](../dyl-mode/references/requirements.md). Missing โ stop and tell the user to run `/add-plugin <name>`.
**Forge.** Use `origin pr` when the repo lives on Origin, `gh pr` otherwise. Commands below show both.
Deep when the invoking skill or the human asks for it (deep / thorough / thermo). Otherwise quick.
1. Resolve PR URLs/numbers. `<base>` below is the PR's base branch (`gh pr view <n> --json baseRefName`, or `origin pr view <n> --json baseRef`), not assumed `main`. For deep, the PR head must be checked out locally: the current branch, or a throwaway worktree (`git fetch origin <base> <branch>`, then `git worktree add /tmp/dyl-review-<pr> origin/<branch>`, removed when done). Thermos and Bugbot audit a checkout. 2. Gather once, then fan out. The main thread writes the PR diff to a file (`git diff origin/<base>...HEAD` from the checkout when there is one, with `origin/<base>` freshly fetched, else `gh pr diff <n>` / `origin pr diff <n>`), then launches every worker the depth calls for in one message, pointing each at that file and at the checkout when there is one:
Analysis happens in the workers, not on the main thread. 3. Every worker uses auto / inherit intelligence (`Task` `model: inherit`, or omit `model`). Do not pin a cheap/fast model for the review judgment pass. 4. Keep the main thread thin: launch, wait, synthesize. Nothing user-facing until every worker finishes. 5. On a re-review (same PR, new tip), tell the Dylan-lens worker and the thermos subagents what changed since the last pass and which earlier asks were deliberately skipped, with the reason, so they re-judge instead of repeating. Bugbot takes a fixed prompt and gets no such context.
Use `generalPurpose`, not `dyl-agent`: `dyl-agent` routes review asks back into this skill. Scope it to this section (steps 1 to 3): the worker does not spawn workers or synthesize. It must:
Read the diff file the main thread wrote. Open surrounding files from the checkout when one exists. Pull title and body read-only via `gh pr view` / `origin pr view`. Focus on the priority list below.
Up to 7 candidates for the shortlist below, each anchored to file:line when known.
Inputs: the Dylan-lens candidates, plus in deep both thermos reports and the Bugbot report.
Prefer high-signal issues you can anchor to a file/line. Every bullet is an ask or a concern. No praise, "nice catch", or other compliments as bullets (tagged nit or otherwise). Zero bullets is fine on a clean PR.
For each finding:
Pick exactly one mark and lead with it on its own line (no "Rec:" label). In that same clause, call out the shape of the asks when it matters:
| Mark | Meaning | Clause habit | |------|---------|--------------| | ๐ข | Ship shape / small nits only | Say "nits only" (or "no as
Official Cursor plugins for popular developer tools, frameworks, and SaaS products. Each plugin is a standalone directory at the repository root with its own .cursor-plugin/plugin.json manifest.
Advisor mode. Consult a stronger (or different) model at key checkpoints: before major decisions, when stuck on an error, andโฆ
Run the full repository compatibility pass: scanner score, startup path, validation loop, and docs reliability.
Designs or reviews CLIs so coding agents can run them reliably: non-interactive flags, layered --help with examples,โฆ
Orchestrate continual learning by delegating transcript mining and AGENTS.md updates to `agents-memory-updater`.
Create a new Cursor plugin scaffold with a valid manifest, component directories, and marketplace wiring. Use when starting a newโฆ
Audit a Cursor plugin for marketplace readiness. Use when validating manifests, component metadata, discovery paths, andโฆ
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, orโฆ
Ask which skill or flow fits your situation. A router over the skills in this repo.