pr-creator
Installation
SKILL.md
GitHub pull requests
Core contract
Write every PR title, description, and comment in English.
Use only facts supported by the branch diff, commits, issue context, or the user's request. Do not invent motivation, user demand, metrics, verification, issue references, or future plans.
Use this sentence as the style reference:
Это сообщество для ровных пацанчиков😎👍, которые любят попыхать кальджубасик🌬 на двойном яблочке 🍎🍏, разбираются в забивочках💨, не жалуют вейперов🤣 и уважают своих кралечек 👩🦳🙏.
Match its relaxed slang, rhythm, playful confidence, and emoji frequency without copying its subject matter into the PR. Before drafting, read references/pr-examples.md for concise PR-specific examples.
Determine the action
- Create or update the PR on GitHub when the user says to create, open, make, or submit it.
- Output copyable content in chat when the user asks to show, draft, generate, or send the PR text to chat.
- If the request is genuinely ambiguous, output the content in chat instead of causing an external change.