Skills Guide

Creating pull requests

VerifiedSafe

Conventions for PR bodies: reference Linear tickets, GitHub issues, never mention client names.

Download and use
Sby Skills Guide Bot
DevelopmentBeginner
7/25/2026
Claude CodeCursorWindsurfCopilotCodex
#pull-requests#git-workflow#linear#github-issues#redaction

Recommended for

Backend developerClaude CodeCode reviewFrontend developerCursorCopilot

Automated summary

Defines the pull request body conventions for this repository, including mandatory Linear ticket and GitHub issue references and the removal of customer names.

Strengths

  • Gives an explicit footer format for standard PRs and subtickets
  • Enforces a clear rule against exposing customer names and their data
  • Clarifies the ambiguous subticket case: relate, not close, the parent issue
  • Includes a verifiable checklist before opening a PR

Limitations

  • Assumes Linear and GitHub, so it does not transfer directly to other tracking systems
  • Applies only to this repo's PRs and does not cover code review or diff content
  • Requires the agent to ask the developer when no ticket exists, adding a manual step
When to use it

Use it when drafting or opening a pull request via `gh pr create` or `gt submit` so ticket-linking and confidentiality rules are followed.

Security analysis

Safe
Quality score86/100

This skill is pure documentation/process guidance for writing PR titles and descriptions. It declares no tools, executes no commands, touches no network or filesystem, and contains no obfuscated payloads. Its emphasis is on redacting client data, which is a privacy-positive instruction rather than a risk.

No concerns found

How this analysis is made

Examples

Standard PR with ticket and issue
Open a pull request for this branch with gh pr create. The Linear ticket is PROD-7478 and there's a related GitHub issue #22801.
Missing ticket
Write the PR description for my changes and open it — I don't have a ticket number handy.
Subticket PR
Create the PR for this subticket. It closes Linear PROD-7478, and the GitHub issue #22801 belongs to the parent ticket.

name: creating-pull-requests metadata: internal: true description: Use when creating, opening, or writing the title/description of a pull request, or writing PR bodies via gh pr create or gt submit. Covers what must go in the PR description (Linear ticket, GitHub issue) and what must never appear (client/customer names or their data). invocation: user

Creating Pull Requests

Conventions for every PR body in this repo. Applies regardless of whether the PR is opened via gh pr create or gt submit.

Rules

  1. Never mention client/customer names or their data examples anywhere in the PR title, description, or commit messages. Redact to generic terms ("a customer", "an org", "example values") even when a Linear ticket or issue references the customer by name.
  2. Always close or reference a Linear ticket. Every PR links to a Linear ticket — Closes: PROD-XXXX to close it, or Relates: PROD-XXXX if it shouldn't auto-close. If no ticket is provided, do not fabricate one and do not silently omit it — flag it to the developer and ask for the ticket. Only open the PR without a ticket once they explicitly confirm there isn't one.
  3. If a GitHub issue exists, reference or close it. Use Closes: #XXXXX to close, Relates: #XXXXX otherwise.
  4. Subticket → parent's GitHub issue is Relates, not Closes. A subticket's PR should not close the parent's tracking issue; add it as related.

Footer Format

Standard PR (closes both the Linear ticket and its GitHub issue):

Closes: PROD-7478
Closes: #22801

Subticket (closes the Linear subticket; the GitHub issue belongs to the parent, so relate it):

Closes: PROD-7478
Relates: #22801

Checklist Before Opening

  • [ ] No client/customer name or their data anywhere in the title, body, or commits
  • [ ] A Closes:/Relates: line for a Linear ticket is present, OR the developer explicitly confirmed there's no ticket
  • [ ] If a GitHub issue exists, a Closes:/Relates: line for it is present
  • [ ] Subtickets relate (not close) the parent's GitHub issue

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/creating-pull-requests-mrzxurdx/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/creating-pull-requests-mrzxurdx' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/creating-pull-requests-mrzxurdx/download' --output '.skill-downloads/creating-pull-requests-mrzxurdx/SKILL.md.part' && mv '.skill-downloads/creating-pull-requests-mrzxurdx/SKILL.md.part' '.skill-downloads/creating-pull-requests-mrzxurdx/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/creating-pull-requests-mrzxurdx/SKILL.md' && test -s '.skill-downloads/creating-pull-requests-mrzxurdx/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/creating-pull-requests' && cp -R '.skill-downloads/creating-pull-requests-mrzxurdx' '.claude/skills/creating-pull-requests'

Cursor
test -f '.skill-downloads/creating-pull-requests-mrzxurdx/SKILL.md' && test -s '.skill-downloads/creating-pull-requests-mrzxurdx/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/creating-pull-requests' && cp -R '.skill-downloads/creating-pull-requests-mrzxurdx' '.cursor/skills/creating-pull-requests'

Codex
test -f '.skill-downloads/creating-pull-requests-mrzxurdx/SKILL.md' && test -s '.skill-downloads/creating-pull-requests-mrzxurdx/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/creating-pull-requests' && cp -R '.skill-downloads/creating-pull-requests-mrzxurdx' '.agents/skills/creating-pull-requests'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/creating-pull-requests-mrzxurdx'

openskills read 'creating-pull-requests-mrzxurdx'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/creating-pull-requests-mrzxurdx/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623
Skills Guide Bot

Emotion to Mantine Migration

Development

Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.

Claude CodeCursorWindsurf+1intermediateSafe 48,981
Skills Guide Bot

Scope Creep Detector

Development

Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.

Claude CodeCursorCodexintermediateSafe 135,015
Skills Guide Bot