gcore:changelog
Generate a curated changelog from the most important commits in the current PR
What this skill does
GENERATE PR CHANGELOG ===================== You generate a curated changelog entry from the current PR's commits. NOT a git log dump — a compiled summary of notable user-facing changes. STEPS ----- 1. Get the current PR's base branch and metadata: ```bash gh pr view --json number,title,body,baseRefName -q '"\(.number) \(.title) [base: \(.baseRefName)]"' ``` 2. Get all commits in this PR (current branch vs base): ```bash BASE=$(gh pr view --json baseRefName -q '.baseRefName') && git log --oneline --no-merges "$(git merge-base HEAD "origin/$BASE")..HEAD" ``` 3. Get the combined diff stat for context on what actually changed: ```bash BASE=$(gh pr view --json baseRefName -q '.baseRefName') && git diff --stat "$(git merge-base HEAD "origin/$BASE")..HEAD" ``` 4. If needed, read specific changed files to understand the nature of changes better. FILTERING RULES --------------- Skip these commits — they are NOT changelog-worthy: - `chore:` commits (deps, CI, gitignore, symlinks, formatting) - `docs:` commits that only fix typos or formatting - merge commits - commits that only change lockfiles, `.gitignore`, or CI configs - refactors with no user-visible behavior change KEEP these commits — they ARE changelog-worthy: - `feat:` — new features - `fix:` — bug fixes - commits with `!` in header or `BREAKING CHANGE` footer — always include - `security:` — vulnerability fixes - `docs:` that add new documentation for new features - any commit that changes public API, config format, or user-visible behavior OUTPUT FORMAT ------------- Follow the format defined in `rules/docs/changelog.md`. Use today's date. Group by change type. ```markdown YYYY-MM-DD ---------- ### Added - Description from user's perspective (#PR) ### Fixed - Description from user's perspective (#PR) ``` Rules: - One line per change, start with `-` - Describe from user's perspective, NOT implementation details - Merge related commits into a single entry (e.g., 3 commits about OAuth → one "Added OAuth 2.0 support" line) - Reference the PR number at the end: `(#123)` - Only include categories that have entries (Added, Changed, Deprecated, Removed, Fixed, Security) - If ALL commits are chore/non-notable, say so explicitly — don't fabricate entries AFTER GENERATING ---------------- Ask the user (numbered list): 1. Insert into CHANGELOG.md and push — find existing CHANGELOG.md, add entry under the header before older dates, commit and push 2. Just show the output — do nothing else
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.