ork-review-pr
Review a pull request or branch for correctness, regressions, security, operational risk, and missing evidence. Use when a request asks to review a PR, review a diff, find real bugs, assess merge risk, or provide evidence-backed review findings. Do not use for implementation or style-only cleanup.
git clone --depth 1 https://github.com/yonatangross/orchestkit /tmp/ork-review-pr && cp -r /tmp/ork-review-pr/plugins/ork-codex/skills/ork-review-pr ~/.claude/skills/ork-review-prSKILL.md
# Ork Review PR Stay read-only and review the actual diff in its repository context. Read the applicable instructions, trace changed behavior to its callers and tests, and prioritize correctness, security, data loss, race conditions, backwards compatibility, and evidence gaps over style. Verify third-party API and configuration claims against the context7 MCP server (`resolve-library-id`, then `query-docs`) before reporting or dismissing a finding that turns on library behavior. A wrong recalled signature is how a review invents a bug and how it misses one. Use one reviewer for a focused diff. For a broad or high-risk PR, fan out independent read-only passes for code-path mapping, risk review, and documentation/API verification; each must return file and line evidence. Prefer `ork_reviewer` when installed, otherwise use a fresh built-in explorer/reviewer role. Lead with findings ordered by severity. Every finding needs a concrete location, impact, and a reproduction or reasoning path. If there are no findings, say what was checked and what was not. Do not modify files or approve/merge the PR.
Accessibility patterns for WCAG 2.2 compliance, keyboard focus management, React Aria component patterns, cognitive inclusion, native HTML-first philosophy, and user preference honoring. Use when implementing screen reader support, keyboard navigation, ARIA patterns, focus traps, accessible component libraries, reduced motion, or cognitive accessibility.
Agent orchestration patterns for agentic loops, multi-agent coordination, alternative frameworks, and multi-scenario workflows. Use when building autonomous agent loops, coordinating multiple agents, evaluating CrewAI/AutoGen/Swarm, or orchestrating complex multi-step scenarios.
AI-assisted UI generation patterns for json-render, v0.app, Google Stitch, Bolt Cloud, and Cursor workflows. Covers prompt engineering for component and full-stack app generation, review checklists for AI-generated code, design token injection, refactoring for design system conformance, and CI gates for quality assurance. Use when generating UI components with AI tools, rendering multi-surface MCP visual output, reviewing AI-generated code, or integrating AI output into design systems.
Queries local analytics across OrchestKit projects for agent usage, skill frequency, hook timing, team activity, session replay, cost estimation, and model delegation trends. Privacy-safe with hashed project IDs. Supports time-range filtering and comparative analysis. Use when reviewing performance, estimating costs, or understanding usage patterns.
Animation and motion design patterns using Motion library (formerly Framer Motion) and View Transitions API. Use when implementing component animations, page transitions, micro-interactions, gesture-driven UIs, or ensuring motion accessibility with prefers-reduced-motion.
API contract design for REST and GraphQL, covering resource shape, URL and header versioning with deprecation windows, RFC 9457 Problem Details error handling, and OpenAPI specs. Use when specifying the wire contract an endpoint exposes, choosing a versioning scheme, or standardizing error response bodies across services. Framework-agnostic protocol layer, not runtime implementation.
ADR templates in the Nygard format with context, decision, consequences, and alternatives. Use when writing ADRs, recording an architectural decision, or evaluating options.
Architecture validation and patterns for clean architecture, backend structure enforcement, project structure validation, test standards, and context-aware sizing. Use when designing system boundaries, enforcing layered architecture, validating project structure, defining test standards, or choosing the right architecture tier for project scope.