Skip to content

chore: point skills-contrib repo references at prisma/prisma - #29837

Open
ankur-arch wants to merge 1 commit into
mainfrom
chore/point-skills-contrib-at-prisma-prisma
Open

chore: point skills-contrib repo references at prisma/prisma#29837
ankur-arch wants to merge 1 commit into
mainfrom
chore/point-skills-contrib-at-prisma-prisma

Conversation

@ankur-arch

@ankur-arch ankur-arch commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Follow-up to the repo migration: the codebase now lives at prisma/prisma, and PRs on the old prisma/prisma-next were not transferred, so links generated from these skills would be dead.

What changed:

  • skills-contrib/draft-release-notes: every PR-link template ([#NNN](https://github.com/prisma/prisma/pull/NNN)), the tag-pinned recipe URLs, the gh api commit-to-PR lookup, and the worked example now use the new repo slug.
  • skills-contrib/contrib-pr: the contributor audience line and the gh auth note now name prisma/prisma.
  • skills-contrib/record-upgrade-instructions: the skills add install paths for the upgrade and extension-author skill trees now pull from prisma/prisma.

No behavior changes beyond the slug. The ignite .pilot mirror has a matching update in prisma/ignite#179 so mirror and canonical stay in sync.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation
    • Updated contributor guidance to use the current Prisma repository and main branch for pull requests.
    • Clarified that contributors must authenticate the GitHub CLI with their own account and submit changes from a fork.
    • Updated draft release note instructions, examples, recipe links, and contributor credits to reference the current repository.
    • Corrected the documented command for distributing the user-facing upgrade skill.

The codebase moved from prisma/prisma-next to prisma/prisma as its
canonical repository, and PRs were not transferred. Update the PR-link
and recipe-URL templates in draft-release-notes, the contributor
audience and gh auth notes in contrib-pr, and the skills add install
paths in record-upgrade-instructions so generated links resolve
against the new repo.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@ankur-arch
ankur-arch requested a review from a team as a code owner July 29, 2026 08:06
@CLAassistant

CLAassistant commented Jul 29, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@coderabbitai

coderabbitai Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

Updated skill documentation to replace prisma/prisma-next references with prisma/prisma across contributor PR workflows, release-note generation, and upgrade skill installation instructions.

Changes

Repository reference retargeting

Layer / File(s) Summary
Contributor PR workflow
skills-contrib/contrib-pr/SKILL.md
Contributor instructions now target prisma/prisma, authenticate the contributor’s GitHub account, and open PRs against prisma:main from a fork.
Release notes repository links
skills-contrib/draft-release-notes/SKILL.md
API lookups, PR links, recipe URLs, and worked examples now reference prisma/prisma.
Upgrade skill distribution command
skills-contrib/record-upgrade-instructions/SKILL.md
The documented upgrade skill installation command now uses prisma/prisma/skills/upgrade.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

Suggested reviewers: aqrln

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly describes the main change: updating skills-contrib references from prisma/prisma-next to prisma/prisma.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/point-skills-contrib-at-prisma-prisma

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@skills-contrib/record-upgrade-instructions/SKILL.md`:
- Around line 22-23: Update the reinstall command in the published upgrade
skill’s SKILL.md to use the current prisma/prisma repository path, matching the
command documented in skills-contrib/record-upgrade-instructions/SKILL.md.
Remove the retired prisma/prisma-next path while preserving the existing upgrade
skill and --all arguments.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro

Run ID: 91afbda5-e51a-4750-af22-15a2411fbc85

📥 Commits

Reviewing files that changed from the base of the PR and between a50a762 and 54b297d.

📒 Files selected for processing (3)
  • skills-contrib/contrib-pr/SKILL.md
  • skills-contrib/draft-release-notes/SKILL.md
  • skills-contrib/record-upgrade-instructions/SKILL.md

Comment on lines +22 to +23
- `skills/upgrade/prisma-next-upgrade/` — distributed via `pnpm dlx skills add prisma/prisma/skills/upgrade --all`. **Audience: users of Prisma Next** (consumers of the public package API: `@prisma-next/postgres`, `@prisma-next/mongo`, the contract files in `prisma/`, on-disk migration shape).
- `skills/extension-author/prisma-next-extension-upgrade/` — distributed via `pnpm dlx skills add prisma/prisma/skills/extension-author --all`. **Audience: authors of Prisma Next extensions** (consumers of the framework SPI: `@prisma-next/contract`, `@prisma-next/framework-components`, `@prisma-next/migration-tools`, etc.).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

Update the published upgrade skill’s reinstall command in the same migration.

skills/upgrade/prisma-next-upgrade/SKILL.md:22 still instructs users to run pnpm dlx skills add prisma/prisma-next/skills/upgrade --all, while this file now documents prisma/prisma. Users following the published skill will still target the retired repository path.

🧰 Tools
🪛 SkillSpector (2.4.4)

[warning] 45: [MP2] Context Window Stuffing: Skill attempts to fill the context window with filler content, displacing legitimate instructions and safety constraints. This can degrade agent performance or bypass safety boundaries.

Remediation: Implement context-window management that detects and rejects padding or stuffing attempts. Prioritize system instructions over user-injected content.

(Memory Poisoning (MP2))

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@skills-contrib/record-upgrade-instructions/SKILL.md` around lines 22 - 23,
Update the reinstall command in the published upgrade skill’s SKILL.md to use
the current prisma/prisma repository path, matching the command documented in
skills-contrib/record-upgrade-instructions/SKILL.md. Remove the retired
prisma/prisma-next path while preserving the existing upgrade skill and --all
arguments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lgtm This PR has been approved by a maintainer

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants