New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Prisma Contributor PR

by prisma in prisma/orm

Guides an outside contributor through opening a prisma/orm pull request from a fork that follows CONTRIBUTING.md and passes review on the first round.

OfficialApache-2.0Auto-check passedDevelopment

Install Prisma Contributor PR

skills CLI
$ npx skills add prisma/orm --skill contrib-pr -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install prisma/orm contrib-pr --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/prisma/orm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills-contrib/contrib-pr .claude/skills/contrib-pr && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
contrib-pr
GitHub stars
48k
Token cost
~2.3k tokens
SKILL.md length
1,251 words
Files
1
Skills in repo
20
Repo updated
First seen
Licence
Apache-2.0

At a glance

Guides an outside contributor through opening a prisma/orm pull request from a fork that follows CONTRIBUTING.md and passes review on the first round.

  • Works in 6 steps: Read the contribution contract → Confirm the change is in the right shape → Run the right test suites → …
  • Submitting a change to prisma/orm as a pull request from a fork
  • SKILL.md covers When to use, Operating principle, Workflow and Don'ts
  • Calls pnpm, git and gh

What it does

The skill is for external contributors using an agent to finish a PR against prisma/orm, separate from the maintainer-facing create-pr skill and free of any dependence on Linear tickets or internal specs. It treats CONTRIBUTING.md as the source of truth and starts by reading it along with the code of conduct and security policy; a security fix must go through private vulnerability reporting rather than a public PR.

The guiding principle is to verify the result, not the authorship: the change should cover one logical concern, run the right test suite green, explain why it exists rather than listing files, have every commit signed off under the DCO, and carry a conventional-commit title. Before opening the PR the agent checks that the diff is a single change and asks whether unrelated cleanups should become separate PRs. If you have already followed the flow, it can jump straight to the gh pr create step.

When your agent uses it

  • Submitting a change to prisma/orm as a pull request from a fork
  • Getting a contribution ready for review on the first round
  • Checking that commits are signed off and the PR title follows conventional commits
  • Deciding whether a mixed diff should be split into separate PRs

Example prompts

  • “Open a PR for this contribution to prisma/orm from my fork.”
  • “Help me get this PR ready for review; check the sign-offs and the title format.”
  • “My diff includes an unrelated cleanup. Should it be a separate PR?”

Requirements

  • A fork of prisma/orm
  • The gh CLI for creating the PR

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Read the contribution contract
  2. Confirm the change is in the right shape
  3. Run the right test suites
  4. Sign off the commits (DCO)
  5. Compose the PR title and body
  6. Confirm with the user, then push and open

What it can do on your machine

Read from SKILL.md and the folder at commit 095af7a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pnpm
    • git
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pnpm, git and gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Prisma Contributor PR loads about 2.3k tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 1,251 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~77
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from prisma/orm at commit 095af7a, republished under its Apache-2.0 licence (© prisma). 1,251 words, ~2,334 tokens.

Download SKILL.mdSave it as .claude/skills/contrib-pr/SKILL.md (or your agent's skills folder).
name
contrib-pr
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.

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 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:

  1. Read CONTRIBUTING.md. This is the source of truth for setup, the test command set, DCO signoff, and PR expectations.
  2. Read CODE_OF_CONDUCT.md so you understand what's expected in your interactions on the PR thread.
  3. Skim SECURITY.md. If your change is fixing a security issue, stop and use the Private Vulnerability Reporting flow instead — do not open a public PR.

If anything in CONTRIBUTING.md contradicts what this skill says, CONTRIBUTING.md wins.

Step 2 — Confirm the change is in the right shape

Before opening the PR, check:

  • One logical change. If the diff includes unrelated cleanup or "while I was here" fixes, ask the user whether to split them into separate PRs. Mixed-scope PRs almost always trigger a "please split this" review comment.
  • Substantive change? If the change is more than a typo / doc fix / obvious bug fix, ask the user whether they opened a tracking issue first per CONTRIBUTING.md. If not, recommend they do — maintainers will respond within 5 business days, and a half-day issue conversation can prevent a one-week PR rewrite when the design direction differs from what they expect.
  • Tests updated. If the change has any behavioural delta and there are no test changes in the diff, push back on the user before opening the PR. "Why aren't there tests?" is the most common reason a PR gets bounced.
  • No backward-compat shims. Prisma 8 is RC; if the change renames or removes an API, the call sites should be updated, not aliased.
Step 3 — Run the right test suites

Run the suite that matches the scope of the change. From CONTRIBUTING.md:

Change scopeCommand
Type errors onlypnpm typecheck
Lint / formattingpnpm lint
Unit tests in packages/**pnpm test:packages
Examplespnpm test:examples
Postgres / SQLite e2epnpm test:e2e
Database integrationpnpm test:integration
Vite plugin / Cloudflare Workerpnpm test:vite-plugin (needs Docker)
Everythingpnpm test:all

The minimum bar before opening any PR is:

bash
pnpm typecheck && pnpm lint && pnpm test:packages

If any of these fail, fix the failure (or push back on the user about whether the change is actually right) before continuing. Do not open a PR with a known-failing test or lint error. It will be closed for that reason alone.

If the change touches the SQL runtime, also run pnpm test:integration and/or pnpm test:e2e. If you can't tell whether the change touches the SQL runtime, run them anyway — they're self-contained (PGlite + mongodb-memory-server, no external DB needed).

Step 4 — Sign off the commits (DCO)

Every commit on the PR must have a Signed-off-by: trailer matching the commit author's name + email. Without this, the DCO status check blocks the PR from merging.

Check current commits:

bash
git log origin/main..HEAD --format='%h %an <%ae>%n%b%n---'

For each commit, verify the body contains a Signed-off-by: line whose name + email match %an <%ae>.

If any commit is missing the trailer:

  • Last commit only: git commit --amend --signoff --no-edit
  • Multiple commits: git rebase --signoff origin/main

After amending or rebasing, force-push to the contributor's fork: git push --force-with-lease.

Step 5 — Compose the PR title and body
Show full SKILL.md (504 more words)Show less
Title

Conventional commit form, lowercase after the colon, no trailing period, under ~60 chars:

text
type(scope): concise lowercase description

type is one of: feat, fix, chore, docs, refactor, test. Pick the one that best describes the change. scope is the primary affected package or layer (sql-runtime, postgres-adapter, contract, cli, framework, mongo-orm, etc.). If the change spans many packages, pick the one most central to the change.

Examples:

  • feat(sql-orm-client): support computed includes
  • fix(postgres-adapter): handle null in jsonb columns
  • docs(contributing): clarify pnpm install steps

PR titles are the raw material the release-notes author triages when a version ships, so pick a title a downstream user would understand.

Body

Fill in the pull request template sections in order:

  • Linked issue: Fixes #N / Refs #N. If no issue exists because the change is small, write n/a — small change.
  • Summary: one or two sentences focused on why, not file-by-file what. "Adds X because Y was broken" rather than "Adds X function in foo.ts and modifies bar.ts".
  • Testing performed: list the actual pnpm test:* commands you ran. If you ran a manual repro (e.g. against the demo), say so.
  • Skill update: say which agent skill the change teaches. Write n/a — internal only only when the change is purely internal or a refactor with no user-visible delta. A user-facing change that teaches no existing skill still needs a sentence saying why no skill update is required. The checklist below asks you to confirm this section.
  • Checklist: confirm DCO signoff, scope, tests, conventional title.
  • Notes for the reviewer (optional): alternative approaches you considered, follow-ups intentionally deferred, anything you want the reviewer to focus on.

Do not include an "AI-authored" disclosure. Maintainers do not require it; it adds noise.

Step 6 — Confirm with the user, then push and open
  1. Show the user the proposed title + body in full and ask for confirmation.
  2. After confirmation, push to the contributor's fork (git push -u origin HEAD from the contributor's branch in the fork).
  3. Open the PR:
bash
gh pr create --title "the title" --body "$(cat <<'EOF'
the body
EOF
)"

The gh CLI must be authenticated against the contributor's GitHub account, not against prisma/orm directly. The PR will open against prisma:main from the contributor's fork.

  1. Return the PR URL.

  2. Tell the user: a maintainer from @prisma/ORM-TS-Maintain will be auto-assigned via CODEOWNERS and is committed to a 5-business-day response window. If the change is large or controversial, expect a review thread before merge.

Don'ts

  • Don't rename CONTRIBUTING.md rules. If they've changed since this skill was written, follow the file, not the skill.
  • Don't force a maintainer's email into a Signed-off-by: trailer. The DCO sign-off must be the contributor's own name and email matching the commit author.
  • Don't open the PR with a failing local check. If pnpm test:packages is red, fix it before pushing.
  • Don't include AI-disclosure boilerplate in the PR body, an "intent artifact" attachment, or any prompt logs. The project does not ask for these.
  • Don't open public issues or PRs for security vulnerabilities. Use Private Vulnerability Reporting per SECURITY.md.
  • Don't ask the user to share secrets, npm tokens, or anything they wouldn't put in a public commit.

© prisma, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills-contrib/contrib-pr of prisma/orm.

Open the folder on GitHubat commit 095af7a

Compare with similar skills

Prisma Contributor PR next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Prisma Contributor PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Prisma Contributor PR this skillprisma/orm48k—~2.3kAutomated safety check: PassApache-2.0
PR Finalize Reviewmicrosoft/garnet12k—~3.1kAutomated safety check: PassMIT
Git Workflow and Versioningaddyosmani/agent-skills102k2 repos~3.5kAutomated safety check: NotesMIT
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT
Emoji Commit ConventionsbaptisteArno/typebot.io11k—~424Automated safety check: PassCustom licence

Similar skills

  • PR Finalize Review

    microsoft/garnet

    Official

    Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.

    12k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed

  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    102k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes

  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Verdaccio Pull Request Workflow

    verdaccio/verdaccio

    Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

  • Emoji Commit Conventions

    baptisteArno/typebot.io

    Sets the repository's convention for commit messages and pull request titles: one emoji prefix for the main intent, a concise title and clean follow-up commits.

    11k GitHub stars~424 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Commit And PR Messages

    superplanehq/superplane

    Write Git commit messages and pull request titles/descriptions using the Chris Beams / Tim Pope conventions (subject/body split, ~50-char subject, imperative mood, why-not-how body) plus ASD-STE100…

    7.7k GitHub stars~1.6k tokensUpdated today
    DevelopmentAuto-check passed

More from prisma/orm

All 20 skills in this repo

  • GitHub Review Iteration

    prisma/orm

    Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • PR Review State Fetch

    prisma/orm

    Official

    Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.

    48k GitHub stars~767 tokensUpdated today
    Auto-check passed

  • Review Implement Phase

    prisma/orm

    Official

    Implements triaged pull request review actions, commits focused fixes, posts status replies on GitHub and resolves the threads.

    48k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Review Triage Phase

    prisma/orm

    Official

    Runs the triage step of the review-framework loop: reads fetched PR review state, builds `review-actions.json`, validates it and renders `review-actions.md`.

    48k GitHub stars~995 tokensUpdated today
    Auto-check passed

  • AST Visitor Pattern for Unions

    prisma/orm

    Official

    Replaces a plain TypeScript union plus switch statements with frozen subclasses and a visitor interface when several places dispatch on the same variants.

    48k GitHub stars~830 tokensUpdated today
    Auto-check passed

  • Prisma Pull Request Creator

    prisma/orm

    Official

    Creates a GitHub pull request for the Prisma repo with a Linear-ticket-prefixed title and a decision-led narrative description, inferring the ticket from context.

    48k GitHub stars~4.6k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Prisma Contributor PR

What does Prisma Contributor PR do?

Guides an outside contributor through opening a prisma/orm pull request from a fork that follows CONTRIBUTING.md and passes review on the first round. The skill is for external contributors using an agent to finish a PR against prisma/orm, separate from the maintainer-facing create-pr skill and free of any dependence on Linear tickets or internal specs.md as the source of truth and starts by reading it along with the code of conduct and security policy; a security fix must go through private vulnerability reporting rather than a public PR.

When should I use Prisma Contributor PR?

Prisma Contributor PR fits situations like: submitting a change to prisma/orm as a pull request from a fork; getting a contribution ready for review on the first round; checking that commits are signed off and the PR title follows conventional commits; deciding whether a mixed diff should be split into separate PRs.

How do I install Prisma Contributor PR in Claude Code?

Run `npx skills add prisma/orm --skill contrib-pr -a claude-code`. Or copy the skill folder (skills-contrib/contrib-pr in prisma/orm) into .claude/skills/contrib-pr in your project. Claude Code loads it when a task matches its description.

How do I install Prisma Contributor PR in Codex?

Run `npx skills add prisma/orm --skill contrib-pr -a codex`. Or copy the skill folder (skills-contrib/contrib-pr in prisma/orm) into .agents/skills/contrib-pr in your project. Codex loads it when a task matches its description.

Can I use Prisma Contributor PR in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add prisma/orm --skill contrib-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/contrib-pr, .gemini/skills/contrib-pr, .github/skills/contrib-pr and .opencode/skills/contrib-pr in your project.

What does Prisma Contributor PR need to run?

Going by SKILL.md and its folder, Prisma Contributor PR needs the command-line tools its instructions call (pnpm, git and gh). Our summary lists: A fork of prisma/orm; The gh CLI for creating the PR.

Does Prisma Contributor PR access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Prisma Contributor PR safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Prisma Contributor PR use?

Prisma Contributor PR is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Prisma Contributor PR use?

About 2.3k tokens (SKILL.md is roughly 9.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Prisma Contributor PR?

Skills that share tags, products or a category with Prisma Contributor PR: PR Finalize Review (microsoft/garnet, 12k stars), Git Workflow and Versioning (addyosmani/agent-skills, 102k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars) and Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Prisma Contributor PR?

prisma (a GitHub organization, an official publisher) maintains it in prisma/orm, which has 47,701 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 6, 2026.

Source: prisma/orm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.