pr-create
Use when the user asks to create a pull request or PR for their work - creates PR using available tools with clear, concise title and description following standard template
What this skill does
# Create Pull Request ## Overview Create brief, focused pull requests. Core principle: **Title + Summary + Flag Issues = Good PR**. Use available tools to create PRs across GitHub, GitLab, Azure DevOps, and other platforms. ## When to Use Use this skill when the user asks to create a PR, make a pull request, open a PR, or submit their work for review. ## User Intent Listen for explicit submission intent. If the user says "Create a PR for this in GitHub" or "Create and submit PR," prepare to submit after showing a preview. If the user simply says "Create a pull request" without specifying submission, show the preview and ask before submitting. **Default behavior:** Show the PR preview first, then ask the user if they want to submit it. ## Process ### 1. Gather Context Check git status, identify base/head branches, and review commit messages. ### 2. Write Title (Continued) **Rules:** Max 8 words, start with verb (Add, Fix, Update, Remove, Refactor), specific but concise. ✓ "Add OAuth to signup form" | ✗ "Made changes" ### 3. Write Description Follow the template in `template.md`. Summary: what changed and why (2-3 sentences). Known Issues: only if trade-offs exist. ### 4. Show Preview & Confirm Always show preview first (title, description, branches, repo). Ask user confirmation before creating. If user said "submit" or "create in GitHub", ask: "Should I create this PR?" Otherwise: "Create this PR?" Only proceed if confirmed. ## Examples ### Simple Feature **Title:** Add email validation to signup form ```markdown ## Summary Adds client-side and server-side email validation to prevent invalid emails. Uses regex pattern matching and DNS verification. ## Known Issues Client-side validation uses regex to avoid dependencies (covers 99% of emails per RFC 5322). ``` ### Bug Fix **Title:** Fix pagination off-by-one error ```markdown ## Summary Fixes pagination logic returning one extra item per page. Changed loop condition from `<=` to `<`. ``` ## Guidelines - **Be brief** — Title: max 8 words. Summary: under 100 words. Omit obvious information. - **Be clear** — State what and why. Use plain language. - **Be honest** — Flag trade-offs upfront. Don't hide issues. - **Be focused** — One logical change per PR. Keep description relevant. ## Quick Reference | Element | Rule | |---------|------| | Title | Max 8 words, verb-first | | Summary | 2-3 sentences, <100 words | | Known Issues | Only if trade-offs exist | | Preview | Always show before creating | | Intent | "Create in GitHub" = submit; "create PR" = ask first |
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce 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).
relationship-science-coach
IncludedUse 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.
building-sf-integrations
IncludedSalesforce 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).
venue-templates
IncludedAccess 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.
let-fate-decide
IncludedDraws 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.
net-ops
IncludedCross-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.