pr
Create a pull request for the current branch against the repo's trunk branch.
What this skill does
# Create Pull Request Create a pull request for the current branch against the repo's trunk branch (auto-detected). Run `/finstreet-dev:commit` first if you have uncommitted changes. ## Workflow Execute these steps in order. ### 1. Pre-flight Checks ```bash git status gh pr view --json url,title 2>/dev/null ``` - If `git status` shows **uncommitted changes**, tell the user to run `/finstreet-dev:commit` first and stop. - If `gh pr view` returns a JSON object (not an error), a **PR already exists** — show the URL and stop. ### 2. Detect the Base Branch Different repos use different trunk branches (`dev`, `main`, `master`). Detect which one this repo uses: ```bash git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null | sed 's|^origin/||' ``` If that returns nothing, fall back by checking which trunk branch exists, in priority order: `dev`, `main`, `master`: ```bash for b in dev main master; do git show-ref --verify --quiet "refs/heads/$b" && echo "$b" && break done ``` Use the detected value as `<base>` in the following steps. ### 3. Ensure the Branch Is Pushed `gh pr create` requires the branch to exist on the remote. If it's never been pushed, push first: ```bash git push -u origin "$(git branch --show-current)" ``` ### 4. Gather Context ```bash git log <base>..HEAD --oneline git diff <base>...HEAD --stat ``` Read every commit — the PR description should reflect the whole branch, not just the latest commit. ### 5. Build Title and Body **Title:** - If the branch name contains a ticket (e.g. `feature/eb-1250-...`), prefix it: `EB-1250: <summary>`. - Otherwise, use a plain imperative summary derived from the commits. - Keep it ≤ 70 characters. **Body template:** ```markdown ## Summary <One or two sentences on what this PR accomplishes and why> ## Changes - <Key change derived from the commit history> - <...> ## Testing - <How was this tested, or what should the reviewer check> ``` Drop a section if it's not meaningful (e.g. no separate testing notes needed for a docs-only change). If there's a ticket, add a `## Ticket` section with a link when you have one — otherwise omit. ### 6. Create the Pull Request Use a HEREDOC for the body so multi-line content and special characters don't break quoting: ```bash gh pr create --base <base> --title "<title>" --body "$(cat <<'EOF' ## Summary <...> ## Changes - <...> ## Testing - <...> EOF )" ``` Pass `--draft` if the user asked for a draft PR. ### 7. Confirm Report to the user: - The PR URL - The target branch (`<base>`) - Whether it's a draft
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.