PR Open Skill

Open a PR for the current branch on GitHub, against the main branch, with a description aimed first and foremost to humans - easy to read, with a clear outline, succinct.

Analyze the changes made in the current branch, take into account the context of the current conversation, and use MCP servers to read the Jira ticket. If the user did not provide a Jira ticket, ask them to provide one, and explain that it is crucial to help you write a better description for the PR.

Title

The title should follow the format of "feat: T40NOA-1234 add new feature X", "fix: resolve issue Y", "refactor: improve code structure for Z", etc. This helps reviewers quickly understand the nature of the changes being proposed. The title should be concise, ideally under 50 characters, sacrifice grammar, caveman style, and should clearly convey the main purpose of the PR. Do not use symbols in the title.

Description

The description should start with an explanation of WHY this was done - what is the use case and the problem it solves. The descriptions starts non-technical and becomes more technical and complex as it goes deeper into the details.

Start the body with links to Jira and Figma. Then, follow these steps to structure the description: