pr-prepare
Prepare pull request descriptions following project template. Activates on: prepare PR, create PR, pull request, ready for PR, draft PR, write PR
Best use case
pr-prepare is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Prepare pull request descriptions following project template. Activates on: prepare PR, create PR, pull request, ready for PR, draft PR, write PR
Prepare pull request descriptions following project template. Activates on: prepare PR, create PR, pull request, ready for PR, draft PR, write PR
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "pr-prepare" skill to help with this workflow task. Context: Prepare pull request descriptions following project template. Activates on: prepare PR, create PR, pull request, ready for PR, draft PR, write PR
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/pr-prepare/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How pr-prepare Compares
| Feature / Agent | pr-prepare | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Prepare pull request descriptions following project template. Activates on: prepare PR, create PR, pull request, ready for PR, draft PR, write PR
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# PR Preparation Skill Automatically prepare pull request descriptions following project standards. ## Activation This skill activates on keywords: - "prepare PR", "prepare the PR", "prepare a PR" - "create PR", "create pull request" - "PR description", "pull request description" - "ready for PR", "ready to PR" - "draft PR", "write PR" ## Workflow When activated, follow these steps: ### 1. Gather Context Run these commands to understand the changes: ```bash # Current state git status # Branch comparison (adjust 'main' if different base branch) git log $(git merge-base HEAD main)..HEAD --oneline # Files changed git diff $(git merge-base HEAD main)..HEAD --stat # Actual diff (for smaller changes) git diff $(git merge-base HEAD main)..HEAD ``` ### 2. Analyze Changes Identify: - **Components modified**: Which files/modules changed - **Purpose**: Why these changes were made - **Impact**: Benefits, risks, breaking changes - **Testing**: What validation was done or needed ### 3. Generate PR Description Use this template format: ```markdown ## Summary [1-3 sentences: what changed and why] ## Changes - **[Component]**: [What changed and why] - **[Component]**: [What changed and why] ## Impact - ✅ [Key benefit or outcome] - ✅ [Another benefit] - ✅ No breaking changes ## Testing - [ ] Tests pass (`uv run pytest`) - [ ] Linting passes (`uv run ruff check`) ## Notes [Optional: known issues, follow-up work, dependencies] ``` ### 4. Suggest PR Title Follow conventional commits format: | Type | When to Use | |------|-------------| | `feat:` | New feature | | `fix:` | Bug fix | | `docs:` | Documentation only | | `refactor:` | Code restructuring | | `test:` | Adding tests | | `perf:` | Performance improvement | | `chore:` | Maintenance, dependencies | ### 6. Output Present the complete PR description ready to copy-paste into GitHub. Remind the user: - CodeRabbit will auto-fill `@coderabbitai summary` placeholder - They can push and create PR with `gh pr create` ## Example Interaction **User**: "Can you prepare the PR for this branch?" **Claude**: 1. Runs git commands to gather context 2. Analyzes the changes 3. Outputs: --- **Suggested Title**: `feat: add user authentication with OAuth2` **PR Description**: ```markdown ## Summary Add OAuth2 authentication supporting Google and GitHub providers. ## Changes - **auth/oauth.py**: OAuth2 client implementation with token refresh - **api/routes/auth.py**: Login, logout, and callback endpoints - **models/user.py**: User model with OAuth provider fields ## Impact - ✅ Users can sign in with Google or GitHub - ✅ Secure session management with httponly cookies - ✅ No breaking changes to existing API ## Testing - [x] Tests pass (`uv run pytest`) - [x] Linting passes (`uv run ruff check`) ## Notes Follow-up: Add Microsoft provider support ``` --- Ready to copy! Push with: ```bash git push -u origin HEAD gh pr create --fill ```
Related Skills
azure-prepare
Default entry point for Azure application development. Invoke this skill for ANY application work related to Azure: creating apps, building features, adding components, updating code, migrating, or modernizing. Analyzes your project and prepares it for Azure deployment by generating infrastructure code (Bicep/Terraform), azure.yaml configuration, and Dockerfiles. USE FOR: create an app, build a web app, create API, create frontend, create backend, add a feature, build a service, make an application, develop a project, migrate my app, modernize my code, update my application, add database, add authentication, add caching, deploy to Azure, host on Azure, Azure with Terraform (defaults to azd+Terraform), Azure with azd, generate azure.yaml, generate Bicep or Terraform, prepare Azure Functions. DO NOT USE FOR: only validating an already-prepared app (use azure-validate), only running azd up/deploy (use azure-deploy), pure Terraform without azd (prefer azd+Terraform).
commit-prepare
Prepare git commit messages following conventional commits. Activates on: commit, prepare commit, commit this, commit message, ready to commit, stage and commit
azure-quotas
Check/manage Azure quotas and usage across providers. For deployment planning, capacity validation, region selection. WHEN: "check quotas", "service limits", "current usage", "request quota increase", "quota exceeded", "validate capacity", "regional availability", "provisioning limits", "vCPU limit", "how many vCPUs available in my subscription".
raindrop-io
Manage Raindrop.io bookmarks with AI assistance. Save and organize bookmarks, search your collection, manage reading lists, and organize research materials. Use when working with bookmarks, web research, reading lists, or when user mentions Raindrop.io.
zlibrary-to-notebooklm
自动从 Z-Library 下载书籍并上传到 Google NotebookLM。支持 PDF/EPUB 格式，自动转换，一键创建知识库。
discover-skills
当你发现当前可用的技能都不够合适（或用户明确要求你寻找技能）时使用。本技能会基于任务目标和约束，给出一份精简的候选技能清单，帮助你选出最适配当前任务的技能。
web-performance-seo
Fix PageSpeed Insights/Lighthouse accessibility "!" errors caused by contrast audit failures (CSS filters, OKLCH/OKLAB, low opacity, gradient text, image backgrounds). Use for accessibility-driven SEO/performance debugging and remediation.
project-to-obsidian
将代码项目转换为 Obsidian 知识库。当用户提到 obsidian、项目文档、知识库、分析项目、转换项目 时激活。 【激活后必须执行】： 1. 先完整阅读本 SKILL.md 文件 2. 理解 AI 写入规则（默认到 00_Inbox/AI/、追加式、统一 Schema） 3. 执行 STEP 0: 使用 AskUserQuestion 询问用户确认 4. 用户确认后才开始 STEP 1 项目扫描 5. 严格按 STEP 0 → 1 → 2 → 3 → 4 顺序执行 【禁止行为】： - 禁止不读 SKILL.md 就开始分析项目 - 禁止跳过 STEP 0 用户确认 - 禁止直接在 30_Resources 创建（先到 00_Inbox/AI/） - 禁止自作主张决定输出位置
obsidian-helper
Obsidian 智能笔记助手。当用户提到 obsidian、日记、笔记、知识库、capture、review 时激活。 【激活后必须执行】： 1. 先完整阅读本 SKILL.md 文件 2. 理解 AI 写入三条硬规矩（00_Inbox/AI/、追加式、白名单字段） 3. 按 STEP 0 → STEP 1 → ... 顺序执行 4. 不要跳过任何步骤，不要自作主张 【禁止行为】： - 禁止不读 SKILL.md 就开始工作 - 禁止跳过用户确认步骤 - 禁止在非 00_Inbox/AI/ 位置创建新笔记（除非用户明确指定）
internationalizing-websites
Adds multi-language support to Next.js websites with proper SEO configuration including hreflang tags, localized sitemaps, and language-specific content. Use when adding new languages, setting up i18n, optimizing for international SEO, or when user mentions localization, translation, multi-language, or specific languages like Japanese, Korean, Chinese.
google-official-seo-guide
Official Google SEO guide covering search optimization, best practices, Search Console, crawling, indexing, and improving website search visibility based on official Google documentation
github-release-assistant
Generate bilingual GitHub release documentation (README.md + README.zh.md) from repo metadata and user input, and guide release prep with git add/commit/push. Use when the user asks to write or polish README files, create bilingual docs, prepare a GitHub release, or mentions release assistant/README generation.