pr-writer
Write pull request titles and descriptions in Tom's house style. Use when the user asks to create a PR, open a pull request, or write a PR description. Trigger phrases include "make a PR", "create a PR", "write a PR description", "open a pull request".
What this skill does
# PR Writer Writes pull request descriptions in the project's established style: short background prose, one paragraph per commit, a reference section. No bullet lists in the body. No em dashes. No AI-sounding filler. ## Thinking Process ### Step 1: Gather context Before writing anything: 1. Run `git log --oneline <base>..<HEAD>` to list commits in this PR. 2. Run `git show <hash>` for each commit to understand what changed and why. 3. Check the base branch (ask the user if unclear). 4. Look up the Jira ticket or design doc URL if the user mentions one. ### Step 2: Draft the title Format: `[base-branch] type: short description` - `base-branch` is the target branch in square brackets, e.g. `[dev]` - `type` follows conventional commits: `feat`, `fix`, `refactor`, `chore`, `docs` - Description is lowercase, imperative, under 60 characters - Include a Jira ticket if provided: `[dev] (CTCS-1234) feat: add AU retry logic` ### Step 3: Write the body The body has three parts: **## Background** One or two sentences explaining why this PR exists. State the context or problem being solved. Do not describe what the code does line by line. Write in plain English. No bullet points. No em dashes. **Per-commit paragraphs** For each meaningful commit, write one paragraph: - Start with the short commit hash as a hyperlink: `[abc1234](full-github-url-to-commit)` - Follow with a plain sentence describing what the commit does and why. - Skip pure chore commits (vendor updates, gitignore) unless they need explanation. - Keep each paragraph to 1-3 sentences. Format for the commit URL: `https://github.com/<org>/<repo>/commit/<full-hash>` **### Reference** List relevant links: design doc, Jira ticket, related PRs. One item per line, as a markdown link. Omit this section if there are no references. ### Step 4: Check style Before finalizing, verify: - No em dashes (`—`). Replace with a comma, period, or rewrite the sentence. - No phrases like "This PR introduces", "This commit implements", "In this PR we". Start sentences with the subject directly. - No summary bullets at the top. - No "Test plan" section unless the user asks for one. - Language is direct and concise. If a sentence can be cut, cut it. ## Example Output ``` Title: [dev] (CTCS-4259) refactor: init go project and remove C++ code ## Background This is the first PR about refactoring of the mail scan service. In this PR, we remove the legacy C++ code and init the go project with external dependency like `go-tmase`. Then we run `go mod vendor` to check in the package. [0b5aa00](https://github.com/trend-ctcs/app-tlx-mail-scan-server/pull/9/commits/0b5aa00): We migrated the proto definitions from Library-MailScanService into this repository to centralize ownership. In the future we'll setup cicd or check in the client code in the codebase. ### Reference [Design doc](https://trendmicro.atlassian.net/wiki/spaces/CTCS/pages/...) ``` ## Rules Summary | Rule | Detail | |------|--------| | Title format | `[base-branch] (ticket) type: description` | | Body opener | `## Background` | | Commit format | `[short-hash](url): one sentence why` | | References | `### Reference` with markdown links | | No em dashes | Use comma or period instead | | No bullet lists | Prose only in Background and commit paragraphs | | No AI filler | No "This PR introduces", no "In summary", no "Overall" | | Length | Short. If it needs more than 3 commit paragraphs, the PR is probably too large |
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.