yorch

Mine a repository's recent pull/merge request review history to learn what its reviewers actually ask for, then generate review guidelines, project pattern docs, a do-not-flag suppression list, and a feedback-loop report that help AI agents and humans review future changes the way this team reviews. Analyzes human review threads, the review-to-fix loop, and declined feedback. Use when: analyze past PRs, learn from PR feedback, generate review guidelines, mine code review comments, what do reviewers ask for, team review conventions, PR review patterns, improve AI code review, reduce review noise, codify tribal knowledge, review retrospective. Works with GitHub (gh) and GitLab (glab); reads review history only, never modifies source code.

Delegate work to a different AI coding agent harness — codex, gemini, pi, opencode, crush, or aider — and verify what comes back. Two modes: `review` runs read-only in the live tree for a second opinion from a different model family; `build` runs write-enabled inside a throwaway git worktree so the result arrives as an inspectable diff on its own branch. Use when: delegate to another agent, second opinion from another model, ask Codex, ask Gemini, run this with opencode, cross-check with a different AI, offload work to save Claude quota, run several agents in parallel, compare how different models solve the same task, agent handoff, external agent, other CLI agent. Never merges anything without showing you the diff first.

Catches and fixes the PostgreSQL 18 Docker volume path breaking change. Invoke this skill whenever you see a docker-compose.yml (or Dockerfile, or any container config) that uses a postgres image — especially postgres:18, postgres:18-alpine, or any version ≥ 18 — with a volume or bind mount. Also trigger when a user asks about postgres data persistence, docker compose postgres setup, volume mounts for postgres, migrating from postgres 17 to 18, or "my postgres data disappeared". The wrong mount path causes silent data loss — the skill explains what changed, how to verify the current mount, and how to migrate safely.

Run Prisma 7 migrations inside a multi-stage Docker production image. Use when: (1) `prisma migrate deploy` crashes with "Cannot resolve environment variable: DATABASE_URL" or "cannot find module" at container startup, (2) building a production Docker image that needs to run migrations before starting the server, (3) you copied only node_modules/prisma + node_modules/@prisma but the Prisma 7 CLI still fails with MODULE_NOT_FOUND at runtime, (4) Yarn 4 node-modules linker .bin/prisma symlink breaks after Docker COPY. Covers prisma.config.ts (Prisma 7), full node_modules copy requirement, and symlink recreation pattern.

Fix TypeScript error "Type 'unknown' is not assignable to type ReactNode" when using Record<string, unknown> values directly in JSX && short-circuit expressions. Use when: (1) JSX expression {someObj.field && <Component />} fails with TS2322, (2) Reading from a JSON or untyped object via bracket notation in JSX conditionals, (3) Values typed as unknown appear in JSX even when wrapped in String() or guarded with truthiness checks. Fix: use !! to coerce to boolean before the && operator.

Fix for Rails models where validates :field, presence: true causes ALL creates to fail when the field is set by a before_create callback. Use when: (1) validates :number, presence: true is added to a model that uses before_create to auto-assign a sequence number, (2) model creates silently fail with "number can't be blank", (3) auto-generated fields (number, slug, token) fail presence validation despite being set in callbacks. Root cause: before_create runs AFTER validations. Fix: change before_create to before_validation on: :create.

Conduct a thorough, React-specific code review of an existing React or Next.js application. Identifies opportunities to simplify components, extract reusable primitives and hooks, fix state/effect anti-patterns, improve accessibility, and propose a safe, incremental refactor roadmap without changing user-facing behavior. Produces a single CODE_REVIEW.md report. Use when: review my React app, audit React code, refactor React, React code review, find duplicated components, propose shared components, extract custom hooks, clean up useEffect, improve React structure, Next.js review, App Router review, RSC review. Works with TypeScript or JavaScript, any styling/state library.

ALWAYS invoke this skill before writing any GitHub Actions workflow that builds or pushes Docker images — it contains specific opinionated patterns that produce secure, reliable workflows and that you cannot reliably guess. The conventions it enforces include: (1) datetime+SHA image tags in YYYYMMDDHHMMSS_sha format for unambiguous build traceability, (2) a `workflow_dispatch` boolean `push` input that defaults to `false` (safe dry-run by default — a common mistake is using `type:choice` with `dry_run` inversion instead), (3) a `publish-docker` PR label gate that lets CI validate builds on PRs without pushing, (4) conditional `latest` tag using `enable={{is_default_branch}}` (never hardcoded `enable=true`), (5) GHA layer cache with `mode=max` for maximum rebuild speed, (6) no inline `${{ github.sha }}` in `run:` scripts (security hardening), (7) dual-registry login and push patterns when publishing to both GHCR and a private registry. Use this whenever the user asks to: set up GHCR publishing, add a docker-pu

Perform a comprehensive code review of current uncommitted changes in a git repository. Analyzes for bugs, security vulnerabilities, best practices, DRY violations, code smells, performance issues, and areas of improvement. Use when: review changes, code review, check my code, review diff, pre-commit review, PR review, quality check. Works with any language or framework.

Generate a DeepWiki-style structured wiki for any git repository: an Overview page, one page per detected subsystem, and detail pages for major components, with Mermaid architecture diagrams and commit-pinned source citations. Uses parallel subagents to fan out per-page generation. Output goes to a configurable directory (default ./wiki/) inside the target repo. Use when: generate wiki, document a codebase, auto-generate docs, deepwiki, codebase walkthrough, architecture overview, onboarding documentation, repository documentation, document open-source repo, generate ARCHITECTURE.md, build a code map. Works on any language and any repo size; reads code only, never modifies source.