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 asks to create, open, make, or submit it, including an explicit request for a draft PR on GitHub.
• Output copyable content for requests limited to PR text. A request to draft PR content without a GitHub target uses this chat-only mode.
• If the intended action remains unclear after reading the request and context, ask a specific question before the affected action. Explicit defaults and earlier authorization are settled answers.
• A PR creation request includes the necessary task commits and push without separate confirmations. Later changes need a new publication request or a standing publication instruction.