chore: point skills-contrib repo references at prisma/prisma - #29837
chore: point skills-contrib repo references at prisma/prisma#29837ankur-arch wants to merge 1 commit into
Conversation
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>
📝 WalkthroughWalkthroughUpdated skill documentation to replace ChangesRepository reference retargeting
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
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
📒 Files selected for processing (3)
skills-contrib/contrib-pr/SKILL.mdskills-contrib/draft-release-notes/SKILL.mdskills-contrib/record-upgrade-instructions/SKILL.md
| - `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.). |
There was a problem hiding this comment.
🗄️ 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.
Follow-up to the repo migration: the codebase now lives at
prisma/prisma, and PRs on the oldprisma/prisma-nextwere 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, thegh apicommit-to-PR lookup, and the worked example now use the new repo slug.skills-contrib/contrib-pr: the contributor audience line and theghauth note now nameprisma/prisma.skills-contrib/record-upgrade-instructions: theskills addinstall paths for the upgrade and extension-author skill trees now pull fromprisma/prisma.No behavior changes beyond the slug. The ignite
.pilotmirror has a matching update in prisma/ignite#179 so mirror and canonical stay in sync.🤖 Generated with Claude Code
Summary by CodeRabbit