# Contrib PR

Open a high-quality external contributor PR against prisma/orm.

- Repository: https://github.com/prisma/orm (47661 stars)
- Category: Git and review
- License: Apache-2.0
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add prisma/orm --skill contrib-pr -g -a claude-code -y`
Codex: `npx skills add prisma/orm --skill contrib-pr -g -a codex -y`
Cursor: `npx skills add prisma/orm --skill contrib-pr -g -a cursor -y`
Gemini CLI: `npx skills add prisma/orm --skill contrib-pr -g -a gemini-cli -y`

## Description

Open a high-quality external contributor PR against prisma/orm. Use when the user is an outside contributor (not a Prisma maintainer) and wants to submit a change as a pull request from a fork. Encodes the contribution flow from CONTRIBUTING.md so the resulting PR passes review on the first round.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Contributor PR skill (external)

This skill is for **external contributors** to `prisma/orm` who are using an LLM-based agent to author or finalize a PR. It is intentionally separate from the maintainer-facing `create-pr` skill: it does not depend on Linear access, internal plan/spec documents, or any private context. It encodes the expectations laid out in [`CONTRIBUTING.md`](../../CONTRIBUTING.md) as a runnable workflow, so the PR you produce matches the shape maintainers expect on the first review round.

If the user is a maintainer with access to internal Linear tickets, use `create-pr` instead.

## When to use

Trigger this skill when the user says any of:

- "Open a PR for this contribution"
- "Submit this as a PR to prisma/orm"
- "I'm contributing to Prisma 8, finalize my change"
- "Help me get this PR ready for review"

If the user has clearly already followed the contribution flow and just needs the `gh pr create` invocation, you may skip directly to step 5.

## Operating principle

Verify the **result**, not the authorship. The maintainers do not ask whether the change was AI-assisted; they verify that:

1. It is scoped to one logical concern.
2. The right test suite is green.
3. The PR explains *why* the change exists, not file-by-file *what*.
4. Every commit is signed off (DCO).
5. The PR title is in conventional-commit form.

This skill is a pit of success, there is no CI gate that checks you used it. Following it is the cheapest way to land the PR cleanly.

## Workflow

### Step 1, Read the contribution contract

Before doing anything else, read the project's contribution docs:

The rest: https://github.com/prisma/orm/blob/HEAD/skills-contrib/contrib-pr/SKILL.md