code-review
Multi-agent code review with deep analysis. Orchestrates codebase research, optional web research, parallel Rust engineers, codex second opinion, and general-purpose reviewers into a synthesized report. Use when the user asks to review code, review a PR, review changes, audit code quality, or says "review", "/review", "code review", "check my changes", "review this PR", "review diff". Trigger for ANY code review request, even partial — e.g., "look over this", "anything wrong with these changes", "sanity check".
modiqo · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add modiqo/skillspec --skill code-review技能说明
name: rote-shell
description: "Use for CLI and shell work through rote: running local commands with rote exec, capturing stdout/stderr/files, following logs and background processes, checking dependency manifests, mixing adapters/browser/process steps, and crystallizing CLI work into TypeScript flows. Prefer rote shell primitives over raw shell when the command result should be remembered, queried, replayed, or shared."
rote-shell
Use rote for shell and CLI work when the result should become workspace memory: commands, outputs, files, logs, process lifecycle, dependencies, and flow replay. Raw shell is still fine for tiny inspection commands, but work that matters should pass through rote so it can be queried, audited, and crystallized.
Load the shell guidance when you need the complete command model:
rote guidance shell essential
First Decision
Choose the narrowest rote primitive that preserves evidence:
- one-shot command:
rote exec -- <program> [args...] - stdin from a file:
rote exec --stdin-file input.txt -- <program> - declared output file:
rote exec --capture-file label:path -- <program> - moving file/log:
rote stream follow --file logs/server.log --until READY - long-running process:
rote exec --background --ready-log READY -- <program> - process stream:
rote stream follow-process proc-1 --stream stdout --until READY - terminal-sensitive command:
rote pty run -- <program> [args...] - dependency preflight:
rote deps check deps.toml - crystallized replay:
rote deno run --allow-all ~/.rote/flows/<name>/main.ts
Do not replace these with ad hoc command > file, tail -f, or ps | grep
when the evidence should be durable. Rote already stores typed responses,
artifacts, hashes, offsets, process leases, and command-log provenance.
Browser Intent Router
If the user says "browse", "open this site", "attach to my browser", "use the
page", "click", "type", "snapshot", "extract from the page", "extract social
profiles", "Gmail in browser", or otherwise asks for live web UI state, stop
shell routing and invoke /rote-browse.
Do not satisfy browser intent with rote exec, raw Playwright, native web
search, WebFetch, open, curl, or a saved non-browser flow unless the user
explicitly switches substrate. Native search may help discover a URL only when
the user asked for search/discovery or the browser route cannot identify a URL;
it is not a substitute for browsing and extracting the page with rote.
Browse intent has precedence over the domain noun. For example, "browse my
calendar", "browse Gmail", "browse HubSpot", or "browse Salesforce" means the
user wants browser-state access even though those domains may also have APIs.
You may still run rote flow search "<intent>" first, but only use an
adapter/flow if it is installed, healthy, and completes the request. If the
adapter/flow is missing, stale, unauthenticated, or fails setup, do not ask the
user to build an adapter before trying the browser route. Hand off to
/rote-browse and use an existing headed browser when the task depends on the
user's logged-in profile.
For public profile extraction, such as "browse each committer's social
profile", use GitHub/CLI/API data to collect candidate URLs and identities,
then use /rote-browse to visit and extract the public pages. Do not replace
that browse step with native web search summaries.
Default browser decision:
- Existing login, Gmail, SSO, MFA, extensions, active tabs, or profile state: ask to attach to an existing headed browser.
- Public read-only page, CI, or replay-like work: ask whether headless new-session is acceptable.
- The user says "browse" without choosing mode: ask headed vs headless; if headed, ask attach-existing vs new rote-managed headed browser.
For active browser attach, hand off to /rote-browse and use its sequence:
rote browser attach setup --method extension --browser chrome
rote browse <url> --headed --attach-existing --new-tab --no-prompt --no-snapshot
rote browse wait --selector '<ready-selector>' --timeout 30 --quiet-ms 750
rote browse snapshot
For browser plus shell work, keep both in the same workspace. Use
/rote-browse for page leases, snapshots, slices, refs, auth state, and
readiness. Use /rote-shell only after browser state has been materialized as
a saved response, snapshot, slice, or file that a local CLI should process.
Current Capability Map
Use only shipped commands. Do not invent aliases from the roadmap.
| Need | Shipped command | Notes |
|---|---|---|
| One-shot process capture | rote exec -- <program> [args...] | Direct argv by default. |
| File stdin | rote exec --stdin-file input.txt -- <program> | Records stdin provenance. |
| Declared output file | rote exec --capture-file label:path -- <program> | Captures file metadata and artifact pointer. |
| Saved stdout/stderr files | rote exec --stdout-file out.txt --stderr-file err.txt -- <program> | Use for durable stream files. |
| Dependency preflight | rote deps check deps.toml | No install side effects. |
| Moving file/log stream | rote stream follow --file app.log --until READY | Supports offsets, chunks, hashes, and pattern stop. |
| Background start | rote exec --background --ready-log READY -- <program> | Creates a tracked lease such as proc-1. |
| Background status | rote exec status proc-1 | Query lease state before acting. |
| Background wait | rote exec wait proc-1 --timeout-ms 300000 --poll-ms 500 | Blocks until a tracked finite job exits or times out; records exit plus stdout/stderr observations. |
| Background stdout/stderr follow | rote stream follow-process proc-1 --stream stdout --until READY | Reads from background log artifacts. |
| Background stop and cleanup | rote exec stop proc-1 | On Unix, stops the process group and records cleanup facts. |
| One-shot terminal transcript | rote pty run -- <program> [args...] | Use when the command must see a ter |