review-fetch-phase

Fetches canonical PR review state and renders derived state artifacts. Use when the user wants the state acquisition phase only (fetch, render, summarize) for a review-framework PR.

Ir a la instalación

Repositorio: prisma/prisma-next
Última actividad en el origen: 22 de julio de 2026 a las 14:36
Idioma detectado de SKILL.md: inglés
Estrellas: 417
Forks: 17

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/prisma/prisma-next --skill review-fetch-phase

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos

10 archivos

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

name: review-fetch-phase
description: Fetches canonical PR review state and renders derived state artifacts. Use when the user wants the state acquisition phase only (fetch, render, summarize) for a review-framework PR.
argument-hint: [pr-url] [output-dir]

# Review Fetch Phase Run only the state acquisition phase of the review-framework loop: fetch canonical review state JSON (v2), validate it, and render all derived artifacts via scripts. Run commands from this skill directory. All script paths below are relative to it. ## Inputs - Required: - PR URL (for example: `https://github.com/OWNER/REPO/pull/123`) - Optional: - output directory If output directory is omitted, derive: `wip/reviews/<owner>_<repo>_pr-<number>/` ## Behavior 1. Validate and parse PR URL, then compute deterministic paths: - `<output-dir>/review-state.json` - `<output-dir>/review-state.md` - `<output-dir>/summary.txt` - `<output-dir>/review-targets.json` 2. Ensure `<output-dir>` exists. 3. Enforce artifact safety before generation (must be ignored by git): ```bash node ./scripts/guard-review-artifacts-ignored.mjs --dir <output-dir> ``` 4. Run fetch script to produce canonical JSON: ```bash node ./scripts/fetch-review-state.mjs --pr <PR_URL> --out-json <output-dir>/review-state.json ``` 5. Validate canonical JSON before deriving additional files: ```bash node ./scripts/validate-review-state.mjs --in <output-dir>/review-state.json ``` 6. Render markdown from canonical JSON: ```bash node ./scripts/render-review-state.mjs --in <output-dir>/review-state.json --out <output-dir>/review-state.md ``` 7. Generate text summary from canonical JSON: ```bash node ./scripts/summarize-review-state.mjs --in <output-dir>/review-state.json --format text --out <output-dir>/summary.txt ``` 8. Extract deterministic triage targets for downstream bootstrap: ```bash node ./scripts/extract-review-targets.mjs --in <output-dir>/review-state.json --out <output-dir>/review-targets.json ``` Target extraction includes: - unresolved review threads - pull-request reviews with body text - issue comments with body text ## Schema contract - `review-state.json` is canonical and must be schema version `2`. - No backward compatibility is provided for v1 artifacts. - Derived artifacts (`review-state.md`, `summary.txt`, `review-targets.json`) are regenerable from canonical JSON. - Review artifacts are generated files and must remain untracked in git. ## Error handling - Treat fetch failures as operational errors. - If `gh api` fails with TLS/cert errors in sandbox (`x509` / `OSStatus -26276`), fail fast and instruct rerun outside sandbox. - Never disable TLS verification. ## Output to user Return artifact paths: - `review-state.json` - `review-state.md` - `summary.txt` - `review-targets.json` Suggest next step: - `/review-triage-phase <PR_URL> [output-dir]`

Ver en GitHub

Volver a la búsqueda Volver a la instalación

prisma-next-extension-upgrade

Upgrade Prisma Next in your extension. Bumps every `@prisma-next/*` dependency to the requested target (or npm `latest`), runs the per-transition upgrade instructions for the extension SPI (middleware lifecycle, codec / migration-tools / framework-components churn, seed-migration on-disk shape), verifies the pins are correctly exact via `prisma-next-check-pins`, runs the extension's own typecheck and tests, and commits each minor step on its own. Use when the user asks to "upgrade Prisma Next" in an extension package, or to update an extension's `@prisma-next/*` deps to a new minor.

2026-07-27

prisma-next-contract

Edit the Prisma Next data contract — add models, fields, relations, indexes, enums, value objects (composite types), type aliases, namespaces (Postgres schemas), cross-contract foreign keys (cross-space FK), polymorphic types (`@@discriminator` / `@@base`), use extension namespaces (`pgvector.Vector(...)`, `cipherstash.EncryptedString(...)`), wire `prisma-next.config.ts` with `defineConfig` from the `@prisma-next/<target>/config` façade, and run `prisma-next contract emit`. Use for schema, models, fields, attributes, soft delete, paranoid, scopes, validations, callbacks, prisma schema, PSL, contract.prisma, contract.ts, contract.json, contract.d.ts, `@prisma-next/postgres/config`, `@prisma-next/postgres/contract-builder`, `@prisma-next/postgres/control`, `@prisma-next/mongo/config`, `@prisma-next/mongo/contract-builder`, `extensions:`, pgvector, cipherstash, postgis, paradedb, supabase, `@prisma-next/extension-supabase`, `@@control`, control policy, managed, tolerated, external, observed.

2026-07-27

prisma-next-upgrade

Upgrade Prisma Next in your app. Bumps every `@prisma-next/*` dependency from the version pinned in the lockfile to the requested target (or npm `latest`), applies any required code-translation steps from the per-transition upgrade instructions, validates with the project's own typecheck + tests, and commits each minor step on its own. Use when the user asks to "upgrade Prisma Next", "bump Prisma Next", "move to Prisma Next X.Y", or asks an agent to deal with an `@prisma-next/*` minor bump in their app.

2026-07-27

Ver todos los de este repositorio

review-fetch-phase

Datos de origen

Opciones de instalación

Revisa los archivos de origen

Más de este repositorio

Más de este repositorio