Agent skill · writing content · aiskillstore
create-pr
Create a PR for this branch. ALWAYS links related issues and uses closing keywords to auto-close them on merge.
Why this skill is useful
Provides a structured process for creating PRs with mandatory issue linking and closing keywords, which the AI may not generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Create a PR ⚠️ MANDATORY: Issue Linking Every PR MUST link to related issues and use closing keywords. PRs without issue links are incomplete Use Closes #X or Fixes #X to auto-close issues on merge Reference ALL related issues, even if not closing them Instructions Step 1: Identify Related Issues Find ALL issues this PR addresses: Issues explicitly being fixed Issues partially addressed Related issues for context Step 2: Gather Context Step 3: Create PR with Issue Links Use the writing-clearly-and-concisely skill for clear writing, then follow prguide. Issue Linking Keywords GitHub recognizes these keywords to auto-close issues on merge: Keyword Example Effect --------- --------- -------- Closes Closes #123 Closes issue when PR merges Fixes Fixes #123 Closes issue when PR merges Resolves Resolves #123 Closes issue when PR merges Use format: Closes #X - brief description Step 4: Verify Issue Links After creating PR: --- PR Description Template --- Anti-Patterns --- Mermaid Diagrams in PRs Use Mermaid diagrams to visualize changes, flows, and architectural impacts. GitHub renders Mermaid natively. Include diagrams when: Showing before/after state changes Illustrating new data flows Explaining component interactions Depicting architectural changes When to Include Diagrams PR Type Diagram Use --------- ------------- Bug fix Before/after flow showing fix New feature User journey or data flow Refactor Component dependency changes API changes Request/response sequence Example: PR with Diagram mermaid sequenceDiagram participant C as Client participant A as Auth Service participant D as Database C->>A: Request with expired token A-->>C: 401 Token Expired C->>A: POST /refresh with refreshtoken A->>D: Validate refresh token D-->>A: Token valid A-->>C: New access token C->>A: Retry original request A-->>C: 200 Success Diagram Types for PRs Tips: Keep diagrams focused (5-10 nodes) Show the change, not entire system Before/after pairs are powerful Embed in PR body, not as links …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/create-pr--92317c