creating-pull-requests

Included with Lifetime

$97 forever

Open a pull request on GitHub. Use when the user asks to open or create a pull request on GitHub.

General

What this skill does

## Workflow

1. Inspect the branch diff and target repository context.
2. Determine the PR style: simple change, bug/failure fix, or feature/tooling change.
3. Draft a concise title and body using the style guide below.
4. Confirm the draft PR details (title, description, target branch) with the user.
5. Create the PR with `gh pr create --title "<title>" --body "<body>"`, adding `--base`, `--head`, `--repo`, or `--draft` when needed.

## Style guide

Write PRs in a direct, reviewer-oriented style:

- Use concise imperative titles: `Add ...`, `Fix ...`, `Remove ...`, `Replace ...`, `Update ...`, `Temporarily disable ...`, etc.
- Lead with what changed or what problem is fixed. Prefer openers like `This PR adds ...`, `This PR fixes ...`, `Removes ...`, or `<component> is EOL ...`.
- Explain why the change exists when it is not obvious. Include root cause, links to prior PRs and issues, compatibility constraints, or release context.
- Use short paragraphs. Use bullets for change lists, affected items, related issues, and compatibility notes.
- Include testing or evaluation only when it adds useful reviewer signal. For performance or tooling changes, include before/after numbers or sample output.
- Keep trivial PR bodies to one sentence. Empty bodies are acceptable only for personal or throwaway PRs whose title fully explains the change.
- Use backticks for code identifiers, commands, branch names, package names, file names, and literal settings.
- Do not use checklists unless the PR template requires one.

## Simple change style

Use this for small, self-contained fixes or cleanup.

```markdown
<One sentence describing what changed.>

<Optional second sentence explaining why, linking an issue, or calling out temporary scope.>
```

## Bug or failure fix style

Use this for test failures, CI failures, regressions, or behavior fixes.

```markdown
This PR fixes <issue or failing behavior>.

The root cause is <brief cause>.

This PR contains several changes:
- <Change 1>
- <Change 2>
- <Change 3>

<Optional note about scope, limitations, or the long-term fix.>
```

## Feature or tooling change style

Use this for new tools, docs, scripts, repo settings, or agent/Copilot changes.

````markdown
## Background

<Problem, motivation, or current limitation.>

## Changes

This PR changes the following:
- <Change 1>
- <Change 2>
- <Change 3>

## Evaluation

```console
<Representative output, if useful for reviewers.>
```
````

## Examples

**Simple change**

```markdown
Removes the leftover `Microsoft.Deployment.DotNet.Releases` package reference from ImageBuilder.

This dependency was originally added for EOL annotation data generation. The EOL handling was later removed, leaving the package reference unused.
```

**Bug/failure fix**

```markdown
This PR fixes digest validation test failures.

The root cause is that the previous validation used an unanchored regex, which allowed invalid digest strings and caused multiple tests to fail.

This PR contains several changes:
- Added `AnchoredDigestRegexp` to capture the encoded value and algorithm.
- Moved digest format validation into `DigestUtils`.
- Updated tests to target `DigestUtils` directly.

The long-term fix is to use the ORAS .NET library for registry interaction, but this keeps the current implementation passing and closer to the OCI spec.
```

**Feature or tooling change**

```markdown
## Background

The existing Copilot settings were adding context and tools that are not needed for every task.

## Changes

This PR changes the following:
- Removed automatic plugin installation.
- Added an MOTD explaining how to install the plugin manually.
- Added local settings to `.gitignore` so the behavior can be overridden locally.
```

Files: 1

Size: 3.9 KB

Complexity: 6/100

Category: General

Source: https://github.com/lbussell/agent-skills/tree/main/skills/creating-pull-requests

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts