GitHub PR
Create high-quality Pull Requests with conventional commits and proper descriptions. Trigger: When creating PRs, writing PR descriptions, or using gh CLI for pull requests.
MCP get_skill({ skillId: "github-pr-f21ddb6f" })Use this skill with your agent
Create a free account and connect via MCP
## When to Use - Creating a new Pull Request - Writing PR titles and descriptions - Preparing commits for review - Using `gh pr create` command --- ## Critical Patterns ### PR Title = Conventional Commit ``` <type>(<scope>): <short description> feat New feature fix Bug fix docs Documentation refactor Code refactoring test Adding tests chore Maintenance ``` ### PR Description Structure ```markdown ## Summary - 1-3 bullet points explaining WHAT and WHY ## Changes - List main changes ## Testing - [ ] Tests added/updated - [ ] Manual testing done Closes #123 ``` ### Atomic Commits ```bash # Good: One thing per commit git commit -m "feat(user): add User model" git commit -m "feat(user): add UserService" git commit -m "test(user): add UserService tests" # Bad: Everything in one commit git commit -m "add user feature" ``` --- ## Code Examples ### Basic PR Creation ```bash gh pr create \ --title "feat(auth): add OAuth2 login" \ --body "## Summary - Add Google OAuth2 authentication ## Changes - Added AuthProvider component - Created useAuth hook Closes #42" ``` ### PR with HEREDOC (Complex Description) ```bash gh pr create --title "feat(dashboard): add analytics" --body "$(cat <<'EOF' ## Summary - Add real-time analytics dashboard ## Changes - Created AnalyticsProvider - Added LineChart, BarChart components ## Testing - [x] Unit tests for components - [x] Manual testing complete ## Screenshots  Closes #123 EOF )" ``` ### Draft PR ```bash gh pr create --draft \ --title "wip: refactor auth" \ --body "Work in progress" ``` ### PR with Reviewers and Labels ```bash gh pr create \ --title "feat(api): add rate limiting" \ --body "Adds rate limiting to API" \ --reviewer "user1,user2" \ --label "enhancement,api" ``` --- ## Commands ```bash # Create PR gh pr create --title "type(scope): desc" --body "..." # Create with web editor gh pr create --web # View PR status gh pr status # View diff gh pr diff # Check CI status gh pr checks # Merge with squash gh pr merge --squash # Add reviewer gh pr edit --add-reviewer username ``` --- ## Anti-Patterns ### Don't: Vague Titles ```bash # Bad gh pr create --title "fix bug" gh pr create --title "update" # Good gh pr create --title "fix(auth): prevent session timeout" ``` ### Don't: Giant PRs ```bash # Bad: 50 files, 2000+ lines in one PR # Good: Split into logical PRs # PR 1: feat(models): add User model # PR 2: feat(api): add user endpoints # PR 3: feat(ui): add user pages ``` ### Don't: Empty Descriptions ```bash # Bad --body "Added feature" # Good --body "## Summary - What you did and why ## Changes - Specific changes Closes #123" ``` --- ## Quick Reference | Task | Command | |------|---------| | Create PR | `gh pr create -t "type: desc" -b "body"` | | Draft PR | `gh pr create --draft` | | Web editor | `gh pr create --web` | | Add reviewer | `--reviewer user1,user2` | | Add label | `--label bug,high-priority` | | Link issue | `Closes #123` in body | | View status | `gh pr status` | | Merge squash | `gh pr merge --squash` | ## Resources - [Conventional Commits](https://www.conventionalcommits.org/) - [GitHub CLI Manual](https://cli.github.com/manual/gh_pr_create)
Related Skills
More skills in Software Engineering
Accessibility Standards
Comprehensive web accessibility standards based on WCAG 2.2 AA, with 38+ anti-patterns, legal enforcement context (EAA, ADA Title II), WAI-ARIA patterns, and framework-specific fixes for modern web frameworks and libraries.
Accord
Authoring unified specification packages across Business/Development/Design teams via staged elaboration (L0 Vision → L1 Requirements → L2 Team Detail → L3 Acceptance Criteria). No code. Use when authoring cross-team specs, building L0-L3 packages, or aligning Biz/Dev/Design on a single source of truth.
Acquire Codebase Knowledge
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
Acreadiness Assess
Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc readiness` and hands off rendering to the @ai-readiness-reporter custom agent. Supports policies (--policy) for org-specific scoring. Use when asked to assess, audit, or score the AI readiness of a repo.
Acreadiness Generate Instructions
Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running /acreadiness-assess to close gaps in the AI Tooling pillar.
Acreadiness Policy
Help the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks, overriding impact/level, setting pass-rate thresholds, or chaining org baselines with team overrides. Use when the user asks about strict mode, AI-only scoring, custom weights, CI gating, or wants org-wide standardisation.
Explore Other Categories
Skills from other categories with shared topics
AI SDK 5
Vercel AI SDK 5 patterns. Trigger: When building AI chat features - breaking changes from v4.
Playwright
Playwright E2E testing patterns. Trigger: When writing E2E tests - Page Objects, selectors, MCP workflow.
React Native
React Native patterns for mobile app development with Expo and bare workflow. Trigger: When building mobile apps, working with React Native components, using Expo, React Navigation, or NativeWind.