Loading...
Loading...
Found 27 Skills
PR quality checklist for ensuring comprehensive, well-documented pull requests. Use before submitting PRs to improve review efficiency and code quality.
Comprehensive verification workflow before merging changes to production.
Use this skill when asked to create a pull request (PR). It ensures all PRs follow the repository's established templates and standards.
Create a pull request following project conventions
Analyzes git diff and commit history to write PR title and description based on the project's PR template.
This skill should be used when you need to create, open, or edit a pull request (PR), or the user asks to "create a PR", "open a PR", "submit a PR", "raise a PR", "file a PR", "make a PR", "create a pull request", "open a pull request", "new PR", or any variation requesting GitHub pull request creation.
Create a GitHub pull request following project conventions. Use when the user asks to create a PR, submit changes for review, or open a pull request. Handles commit analysis, branch management, and PR creation using the gh CLI tool.
Create pull requests with Conventional Commit-style titles and template-compliant descriptions using GitHub CLI. Use when asked to create, open, draft, or update a PR from the current branch and the team expects consistent semantic titles and structured PR bodies.
Create a pull request for the current feature branch. Generates a PR description from commits, runs pre-submission checks, and optionally activates the Deployment Council for production-impacting changes. Use when your feature branch is ready to merge to main.
Automatically create or update GitHub Pull Requests. When you need to create a PR for Paddle-related repositories, prioritize using this skill.
Implement change management processes. Configure CAB reviews, change windows, and rollback procedures. Use when managing production changes.
Create a pull request following project conventions.