Prepare and submit external pull requests for the Prisma Next repository.
npx skills add https://github.com/prisma/prisma --skill contrib-pr
Please help me install this Agent Skill. Skill: contrib-pr Source: https://github.com/prisma/prisma/tree/main/skills-contrib/contrib-pr Command: npx skills add https://github.com/prisma/prisma --skill contrib-pr
This skill removes the friction and uncertainty for external contributors by automating the adherence to project-specific contribution standards, ensuring pull requests are formatted and tested correctly for immediate maintainer review.
Use the contrib-pr skill to finalize and open a pull request for the current branch after verifying all tests pass.
High-intent search queries and answers about installing and using this skill.
To submit a pull request to Prisma Next, you must sign off your commits for DCO compliance and use conventional commit formatting. This workflow automates those preparation steps and runs validation checks to ensure your PR meets maintainer expectations.
The standardized external contribution workflow for Prisma Next requires applying DCO sign-off, adhering to conventional commit formatting, and running necessary test suites. This process ensures code changes align with project-specific documentation and are ready for review.
Yes, you need the GitHub CLI installed to automate pull request preparation for Prisma Next. The local environment configuration uses the CLI to execute validation checks and perform the git operations required for submission.
To run integration tests before opening a pull request, you must execute the necessary test suites and linting checks locally. This automated validation guides you through the required checks to verify your code changes are ready for submission.
The best way to format an external code contribution for immediate review is to enforce DCO sign-off, conventional commit formatting, and automated test validation. This removes friction by ensuring the pull request body and code changes meet project standards.
Your external pull request fails validation if it lacks DCO sign-off, conventional commit formatting, or passing test suites. Automating the contribution preparation ensures these project-specific testing and linting requirements are met before submission.
ayazhankadessovaDraft GitHub pull request titles and bodies from conversation context and code changes.
manastalukdarSquash Git commits, run tests, and clean up branches.
streaming-video-technology-allianceCreate GitHub pull requests with validated code, tests, and conventional commits.
breakingcircuits1337Standardizes skill creation, validation, and canonicalization processes.
