Menú
Generate a very concise PR title and description for the current branch
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Create a single self-contained HTML artifact instead of a long markdown reply
Propose changes to Plain's docs based on changes on the current branch
Create a single HTML page to explain the given subject
Compact the current conversation into a handoff document for another agent to pick up
Surface weekly LinkedIn post ideas from my recent work
Investigate a problem and create a plan as a HTML document
| name | pr |
| description | Generate a very concise PR title and description for the current branch |
Write a very concise title and description for a GitHub pull request for the current branch. Open the output as a temporary editable HTML tab in Safari on completion. The UI design can be light mode, with a single line input for the title, and a multiline input for the description expanded so that you can see the entire description without scrolling, and two buttons to copy each to the clipboard, and the title of the HTML page should be the PR number and ticket number if available.
Title format:
[TICKET_NUMBER] <area> → <short_description>
[ARI-1884] Knowledge Sources → Remove search queries from logs
Description must be in markdown, and include the following sections:
Talk at a high level, don't go in to implementation details, that is what the code is for. Bias towards brevity, and use bullet points where appropriate. Do not use emojis. Bullet points should only ever be a single sentence, feel free to lean on commas and semicolons to make them longer, and do not use full stops at the end of each bullet point. Do not include ticket numbers in the description. The first word of each bullet point should be capitalised. Make use of inline code blocks to highlight parts of a bullet point where appropriate. Avoid using hyphenated compound modifiers (write "production grade" not "production-grade", "real time" not "real-time" etc).
Before the start of the "Problem" section of the description, there should be a line that reads "Resolves TICKET_NUMBER", with a link to the Linear ticket, and a newline under it.