Results for “pr-review”

Build work collaboratively in reviewable pieces, handing each piece back for review before starting the next, so the person stays in the lead and steers while the work happens instead of reviewing a finished result. Use when someone says to pair with them on something, asks to collaborate rather than direct, wants to review as it goes, or wants to guide the work piece by piece — on code, on a design decision, or on writing. For a test-first build it runs tdd, for restructuring it runs refactor, for an interface contract it runs design-an-api, and for plan work it runs iterative-plan-review or plan-implementation, each collaboratively; invoke any of those directly instead to run it straight through without pausing. Does not pace someone through code that already exists and builds nothing — use code-walkthrough. Does not explain, summarize, or research something instead of producing it — use code-overview or research.

Data Processing Agreement reference — GDPR Article 28, processor obligations, sub-processor management, and cross-border transfers. Use when drafting or reviewing DPAs with vendors.

Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.

Prepare PRINCE2 Closing a Project material: product acceptance, end project report, lessons report, benefits review plan, handover, follow-on actions, and closure recommendation.

Opens plans and HTML artifacts in a local browser canvas where the human annotates elements, chats, and approves or requests changes without leaving the page. Use when presenting a plan for review, or when feedback like "move this, change that" is easier pointed at than typed.

`task-agent`/`review-agent`: use when CPU, memory, I/O, database, network, rendering, or cost needs measured bottleneck evidence; skip without a profiling need.

Agent profile for art direction and premium UI/UX review across websites, apps, dashboards, 3D web experiences, and landing pages.

Use for MarketingClaw clawtributors PR/issue triage: Discrawl discovery, live-open rechecks, deep review, topic grouping, and compact @handle/LOC/type/blast/verification summaries.

Audits source code for observability gaps — missing telemetry, poor observability practices, and code structure that resists instrumentation — then emits a ranked, bounded finding list. Invoke when the user says "observablip this", "observablip `pkg/foo`", "audit observability", "review telemetry", "find missing spans", "audit o11y on this PR", "review my logging", or "is this instrumented well enough?". Read-only; never edits files.

EULA drafting reference — license grant, restrictions, termination, IP ownership, and enforceability. Use when drafting or reviewing End User License Agreements for software products.

Review and manage an IP portfolio across trademarks, patents, copyrights, and domains — docketing assets, deadlines, coverage gaps, and prune-vs-maintain decisions.

Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.

Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.

Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.

Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.

Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.

Designing and reviewing APIs: OpenAPI spec generation, versioning strategy, breaking change detection, REST/GraphQL best practices. Use for API design or OpenAPI specs.

Use when implementing or reviewing substantial TypeScript, designing public APIs, modeling domain state, validating runtime data, or refactoring project-scale TypeScript code.

Independent DeepSeek-backed adversarial proof-audit step for existing theorem, lemma, proposition, or proof artifacts in Markdown, LaTeX, or proof logs. Use when asked to check, audit, verify, red-team, or adversarially review a proof; when a completed proof task needs a correctness pass; or when a broader proof workflow dispatches an independent reviewer to find gaps, hidden assumptions, counterexamples, or unjustified steps.

Use Heroku Managed Inference and Agents with the current Heroku AI workflow. Use when the agent needs to install or inspect the Heroku AI CLI plugin, provision Heroku inference access on the current standard plan, review the latest Managed Inference model catalog, attach model resources, make test inference calls, or review Heroku-managed AI model operations.

Guides attorneys through deposition witness preparation using a two-session model with document review, practice examination, and day-of logistics. Covers party witnesses, fact witnesses, 30(b)(6) corporate representatives, and experts. Produces preparation memos, document review lists, topic summaries, and day-of checklists. Enforces ABA Opinion 508 ethical boundaries. Use when preparing any witness for deposition, scheduling prep sessions, or building witness preparation materials.

Design, review, or troubleshoot Salesforce Approval Processes, covering entry criteria, approver routing, record locking, and recall behavior.

PLC programming reference — ladder logic, structured text, function blocks, and IEC 61131-3 standards. Use when writing PLC programs, debugging rungs, or reviewing automation logic.

For analysis/task/review agents using a Professional Skill on models, RAG, agents, evaluation, or safety; not for work without AI decision impact.

`analysis-agent`/`task-agent`/`review-agent`: use when personal-data purpose, retention, deletion, sharing, telemetry, or provider handling changes; skip legal-only work.

`analysis-agent`/`task-agent`/`review-agent`: use when SQL changes affect NULL, cardinality, constraints, locks, precision, or dialect semantics; skip tool-only work.

Render the cited draft as an HTML preview styled like the brand's blog so the writer can review the article in browser before publishing.

Recurring workflow patterns from 904+ Construct-AI development sessions. Covers git operations, debugging, code review, UI component work, and documentation procedures.

>- Analyze KiCad projects and PDF schematics: schematics, PCB layouts, Gerbers, footprints, symbols, netlists, and design rules. Reviews designs for bugs, traces nets, cross-references schematic to PCB, extracts BOM data, checks DRC/ERC, DFM, power trees, and regulator circuits. Every finding carries a confidence label and evidence source with trust_summary rollup. Analyzes PDF schematics from dev boards, reference designs, eval kits, and datasheets. Supports KiCad 5–10. Use whenever the user mentions .kicad_sch, .kicad_pcb, .kicad_pro, PCB design review, schematic analysis, PDF schematics, reference designs, Gerber files, DRC/ERC, netlist issues, BOM extraction, signal tracing, power budget, DFM, or wants to understand, debug, compare, or review any hardware design. Also for "check my board", "review before fab", "what's wrong with my schematic", "is this ready to order", "check my...

Prepare the PRINCE2 Starting Up a Project material: mandate review, project brief, outline business case, project product description, initiation stage plan, lessons, and startup decisions.

`analysis-agent`/`task-agent`/`review-agent`: use for provider-consumer compatibility of APIs, events, schemas, or behavior; skip without independent consumer/version risk.

`analysis-agent`/`review-agent`: use when proven variation needs extension points, plugins, policy hooks, compatibility, or deprecation; skip when no extension decision exists.

`analysis-agent`/`task-agent`/`review-agent`: use for structure, workspace or package bootstrap, config, scripts, or quality gates; skip without an initialization decision.

Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns.

Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.

Summarizes daily development progress into project-local and global diary files, then syncs them to Notion and Obsidian.