Menu
Use to create a pull request with detailed summary and description
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create a git worktree for an own or someone else's branch, symlink local-only files (.env, .tmux-sessionizer), optionally install or symlink node_modules, and open it in tmux
How to create and name git branches
Use this when you need to do a full workflow -- create a JIRA ticket, create a branch, create a PR, push changes
Review code changes for quality and best practices. Use when reviewing pull requests, examining code changes, or providing feedback on code quality. Covers security, performance, testing, and design review.
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.
Generate a Playwright test based on a scenario using Playwright CLI
| name | create-PR |
| description | Use to create a pull request with detailed summary and description |
Your job is to create a PR with the current changes.
Ask the user if this is for an existant JIRA ticket, or a new one.
Follow the template on ./pr-template.md for its content
For the ## Change section (<change-description></change-description>), make sure to summarize as much as possible the changes. It doesn't need to be technical, just something that describes the overall changes:
Example: "Parses and validates data on useQuestionQuery hook"
For the ## Problem / Why section (<change-reason></change-reason>), you can get a little bit more technical. Still, it doesn't need to be a huge description, just expanding on what the change is actually like and the reasons behind it.
If the PR is for an existant JIRA ticket, format the PR title as follows: []:
Once the PR is ready:
If the PR is for an existant JIRA ticket, update the ## References section with the JIRA link. For this:
jira cli to look for the ticket and understand what is the correct URLjira cli)If the PR is for a new JIRA ticket:
## References section untouched from the template@peakon-bot create-jira PEAKONLIGHTAt the end, give the PR URL to the user so that they can open it in the browser easily