changelog
Skill1k starsChanged 28 days agoBSD-3-ClauseView on GitHub
Polish the automated CHANGELOG on develop before the next stable build. Removes GUS refs, categorizes under-the-cover changes, improves customer-facing descriptions. Use when preparing/reviewing the changelog after a weekly prerelease promotion, or when user mentions changelog quality.
- Commits and pushes
165 other projects use a version of this.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- raphaeltm/simple-agent-managertheir own version, first seen Nov 15, 2026
- lengrufeng2008/dsh-skill-librarytheir own version, first seen Nov 15, 2026
- Kuan-AI-com/agent-skillstheir own version, first seen Nov 15, 2026
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
- rust-works/omni-devtheir own version, first seen Nov 15, 2026
- 5uck1ess/devkittheir own version, first seen Nov 15, 2026
Who's talking about forcedotcom/salesforcedx-vscode
- prettier/prettier-vscode“Couldn't resolve parser "json-stringify"”GitHub · Jun 5, 2018 · 23 reactions
- Stack Overflow“VSCode / Salesforce - Deploy Source to Org very slow to complete, although actual deployment is fast?”Stack Overflow · Jun 26, 2023 · 4 votes
- xixiaofinland/sf.nvim“Debugging functionality”GitHub · Oct 1, 2024 · 3 reactions
- EclipseFdn/open-vsx.org“Claiming namespace salesforce”GitHub · May 3, 2023 · 2 reactions
- forcedotcom/salesforcedx-apex“fix: set correct exit codes on failure”GitHub · Apr 23, 2021 · 2 reactions
The biggest 5 of 52 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 52
Talked about on GitHub and Stack Overflow (52 times).
On GitHub · 50
- Jun 5, 2018Couldn't resolve parser "json-stringify" — prettier/prettier-vscode23 reactions · 6 comments
- Oct 1, 2024Debugging functionality — xixiaofinland/sf.nvim3 reactions · 14 comments
- May 3, 2023Claiming namespace salesforce — EclipseFdn/open-vsx.org2 reactions · 21 comments
- Apr 23, 2021fix: set correct exit codes on failure — forcedotcom/salesforcedx-apex2 reactions
- Sep 11, 2024E2E tests fail in VSCode version 1.93.0 with "target window already closed" when running "Developer: Reload Window" — webdriverio-community/wdio-vscode-service1 reaction · 11 comments
45 more on GitHub
- Sep 30, 2020Trigger completions on specific characters — forcedotcom/lightning-language-server1 reaction · 2 comments
- Jun 25, 2019Source commands do not display error information — forcedotcom/cli1 reaction · 34 comments
- Aug 27, 2018Inform extensions that call 'vscode.openFolder' with file URIs created with URI.parse — microsoft/vscode1 reaction
- Aug 3, 2017Show externalised strings in extension editor contributions tab — microsoft/vscode1 reaction · 8 comments
- Nov 13, 2026build(deps-dev): bump the development-dependencies group across 1 directory with 8 updates — certinia/debug-log-analyzer0 reactions
- Nov 11, 2026agent-skills.github.forcedotcom.salesforcedx-vscode: 68.10.0 → 68.12.0 — sudosubin/agents.nix0 reactions
- Nov 11, 2026claude-code-plugins.github.forcedotcom.salesforcedx-vscode: 68.10.0 → 68.12.0 — sudosubin/agents.nix0 reactions
- Nov 9, 2026build(deps-dev): bump the development-dependencies group across 1 directory with 6 updates — certinia/debug-log-analyzer0 reactions · 1 comment
- Nov 6, 2026build(deps-dev): bump the development-dependencies group across 1 directory with 5 updates — certinia/debug-log-analyzer0 reactions · 1 comment
- Nov 5, 2026claude-code-plugins.github.forcedotcom.salesforcedx-vscode: 68.8.0 → 68.10.0 — sudosubin/agents.nix0 reactions
- Nov 5, 2026build(deps-dev): bump the development-dependencies group across 1 directory with 4 updates — certinia/debug-log-analyzer0 reactions · 1 comment
- Nov 4, 2026agent-skills.github.forcedotcom.salesforcedx-vscode: 68.8.0 → 68.10.0 — sudosubin/agents.nix0 reactions
- Nov 4, 2026build(deps-dev): bump the development-dependencies group across 1 directory with 2 updates — certinia/debug-log-analyzer0 reactions · 1 comment
- Oct 29, 2026claude-code-plugins.github.forcedotcom.salesforcedx-vscode: 68.6.1 → 68.8.0 — sudosubin/agents.nix0 reactions
- Oct 29, 2026agent-skills.github.forcedotcom.salesforcedx-vscode: 68.6.1 → 68.8.0 — sudosubin/agents.nix0 reactions
- Oct 27, 2026agent-skills.github.forcedotcom.salesforcedx-vscode: 68.6.0 → 68.6.1 — sudosubin/agents.nix0 reactions
- Oct 27, 2026claude-code-plugins.github.forcedotcom.salesforcedx-vscode: 68.6.0 → 68.6.1 — sudosubin/agents.nix0 reactions
- Oct 27, 2026build(deps-dev): bump @salesforce/playwright-vscode-ext from 1.7.0 to 1.7.1 in the development-dependencies group across 1 directory — certinia/debug-log-analyzer0 reactions · 1 comment
- Oct 26, 2026build(deps-dev): bump @salesforce/playwright-vscode-ext from 1.7.0 to 1.7.1 in the development-dependencies group across 1 directory — certinia/debug-log-analyzer0 reactions · 2 comments
- Oct 22, 2026build(deps-dev): bump the development-dependencies group across 1 directory with 10 updates — certinia/debug-log-analyzer0 reactions · 1 comment
- Oct 21, 2026claude-code-plugins.github.forcedotcom.salesforcedx-vscode: 68.4.0 → 68.6.0 — sudosubin/agents.nix0 reactions
- Oct 21, 2026agent-skills.github.forcedotcom.salesforcedx-vscode: 68.4.0 → 68.6.0 — sudosubin/agents.nix0 reactions
- Oct 21, 2026build(deps-dev): bump the development-dependencies group across 1 directory with 8 updates — certinia/debug-log-analyzer0 reactions · 1 comment
- Oct 19, 2026build(deps-dev): bump the development-dependencies group across 1 directory with 7 updates — certinia/debug-log-analyzer0 reactions · 1 comment
- Oct 16, 2026claude-code-plugins.github.forcedotcom.salesforcedx-vscode: 68.2.0 → 68.4.0 — sudosubin/agents.nix0 reactions
- Oct 16, 2026agent-skills.github.forcedotcom.salesforcedx-vscode: 68.2.0 → 68.4.0 — sudosubin/agents.nix0 reactions
- Oct 16, 2026build(deps-dev): bump @salesforce/vscode-services from 67.20.0 to 67.27.5 — forcedotcom/apex-language-support0 reactions · 2 comments
- Oct 16, 2026feat(git): replace isomorphic-git with Effect Git - W-22711959 — forcedotcom/source-tracking0 reactions · 3 comments
- Oct 16, 2026build(deps-dev): bump the development-dependencies group across 1 directory with 4 updates — certinia/debug-log-analyzer0 reactions · 1 comment
- Oct 14, 2026build(deps-dev): bump the development-dependencies group across 1 directory with 2 updates — certinia/debug-log-analyzer0 reactions · 1 comment
- Oct 14, 2026claude-code-plugins.github.forcedotcom.salesforcedx-vscode: 67.26.0 → 68.2.0 — sudosubin/agents.nix0 reactions
- Oct 13, 2026agent-skills.github.forcedotcom.salesforcedx-vscode: 67.26.0 → 68.2.0 — sudosubin/agents.nix0 reactions
- Oct 12, 2026build(deps-dev): bump @salesforce/vscode-services from 67.26.0 to 67.27.1 in the development-dependencies group — certinia/debug-log-analyzer0 reactions · 1 comment
- Oct 4, 2026claude-code-plugins.github.forcedotcom.salesforcedx-vscode: init at 67.26.0 — sudosubin/agents.nix0 reactions
- Oct 3, 2026agent-skills.github.forcedotcom.salesforcedx-vscode: 67.20.0 → 67.26.0 — sudosubin/agents.nix0 reactions
- Sep 27, 2026agent-skills.github.forcedotcom.salesforcedx-vscode: init at 67.20.0 — sudosubin/agents.nix0 reactions
- Sep 25, 2026build(deps-dev): bump @salesforce/vscode-services from 67.17.18 to 67.20.0 — forcedotcom/apex-language-support0 reactions · 1 comment
- Sep 18, 2026build(deps-dev): bump @salesforce/vscode-services from 67.15.0 to 67.17.4 — forcedotcom/apex-language-support0 reactions · 1 comment
- Aug 28, 2026build(deps-dev): bump @salesforce/vscode-services from 67.10.0 to 67.13.3 — forcedotcom/apex-language-support0 reactions
- Aug 24, 2026Use Org Metadata Catalog for find-missing-artifact org lookups - W-23971749 — forcedotcom/apex-language-support0 reactions · 3 comments
- Aug 21, 2026build(deps-dev): bump @salesforce/vscode-services from 67.7.1 to 67.10.0 — forcedotcom/apex-language-support0 reactions
- Aug 19, 2026feat: export stdValueSetRegistry.json from main index.ts to be called properly outside this repo - W-23802414 — forcedotcom/source-deploy-retrieve0 reactions
- Jul 24, 2026build(deps): bump @salesforce/vscode-i18n from 66.7.1 to 66.8.0 — forcedotcom/apex-language-support0 reactions
- Jul 8, 2026Support new SFDX: Create OpenAPI Document from This Class (Beta) — RoseSilverSoftware/IlluminatedCloud0 reactions
- Jul 8, 2026Agentforce for Developers inline autocompletion not working (temporary Salesforce API regression) — RoseSilverSoftware/IlluminatedCloud0 reactions
On Stack Overflow · 2
Used with
Projects with it also use playtest-report, soak-test and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CoralGameSkillplaytest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
Also in 12 projects that use this
lilangMaxSkillsoak-test
Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.
Also in 9 projects that use this
lilangMaxSkillteam-live-ops
Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.
Also in 9 projects that use this
CoralGameSkillteam-polish
Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.
Also in 14 projects that use this
- +5 more from lilangMax
- +3 more from CoralGame
Other versions165 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 165
- meteor/meteor★ 45ksame name
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- MaaAssistantArknights/MaaAssistantArknights★ 25ksame name
- pipecat-ai/pipecat★ 17ksame name
- elie222/inbox-zero★ 13ksame name
- hashicorp/terraform-provider-aws★ 11ksame name
- JetBrains/ideavim★ 10ksame name
- BuilderIO/agent-native★ 7.7ksame name
- UnigramDev/Unigram★ 5.5ksame name
- entireio/cli★ 5.3ksame name
155 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository46 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/doc-maintenance.mdcCursor rule
- .cursor/rules/verification.mdcCursor rule
- .cursor/rules/wireit.mdcCursor rule
- vscode-extension-launchSkill
- announce-prereleaseSkill
- backlog-groomingSkill
- command-uiSkill
- conciseSkill
- core-extension-apiSkill
- dependabot-alertsSkill
- drivable-vscodeSkill
- effect-best-practicesSkill
- external-consumersSkill
- feature-branchSkill
- grill-meSkill
- gus-cliSkill
- i18n-messagesSkill
- icons-srcSkill
- lit-componentsSkill
- lit-webview-architectureSkill
- lit-webview-testingSkill
- lsp-custom-requestsSkill
- merge-conflictsSkill
- packageJsonSkill
- patch-releaseSkill
- pathsSkill
- playwright-e2eSkill
- pr-draftSkill
- query-app-insightsSkill
- releaseSkill
- services-extension-consumptionSkill
- shipped-issuesSkill
- span-file-exportSkill
- thermo-nuclear-code-quality-reviewSkill
- ts1261-filename-casingSkill
- ts4023-effect-errorsSkill
- typescriptSkill
- verificationSkill
- vscode-elements-webviewsSkill
- vscode-window-messagesSkill
- web-console-local-tracesSkill
- wireitSkill
- work-item-sequencingSkill
- changelog-judgmentSkill
- manual-test-plan-judgmentSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. 0 are common, 9 are distinctive, and 9 are very specific to this project.
0
Common
Most of the 154 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 43
Test infrastructure (E2E suites, unit tests, test utilities)
- Very specific: line 56
Use PR commits, title, body, and labels to decide.
- Distinctive: line 67
Write from the user's perspective: "We added...", "We fixed...", "You can now..."
- Very specific: line 69
Start with We added…, We fixed a bug where…, We improved…, We reverted…, or The <X> now….
- Distinctive: line 72
Keep entries to 1-2 sentences max
- Very specific: line 77
Prefer VS Code over VSCode.
- Distinctive: line 78
After the PR link(s), append issue and discussion links found in the "What issues does this PR fix or reference?" section of the PR body:
- Distinctive: line 82
Only include issues/discussions explicitly listed in that section.
- Distinctive: line 90
Remove empty package sections (header with no entries)
- Distinctive: line 124
After user approves the polished changelog:
- Very specific: line 126
Make sure you're on develop and up to date: git checkout develop && git pull
- Very specific: line 128
Verify no other files are staged: git diff --cached --name-only must show only packages/salesforcedx-vscode/CHANGELOG.md.
- Distinctive: line 132
Never include other file changes in this commit.
- Very specific: line 134
Use these chore: subjects for polish commits on develop:
- Very specific: line 200
If salesforcedx-vscode-core is touched, all other touched packages (except docs) are dropped for that commit
- Very specific: line 201
If salesforcedx-vscode-services is touched alongside exactly one other (non-docs) package, salesforcedx-vscode-services is dropped and the …
- Very specific: line 202
Only packages starting with salesforce or docs count.
- Distinctive: line 209
No dedupe against the existing changelog file — the range is disjoint by construction (see Commit details above)
“Common” is measured: kept by at least 6 in 10 of the 154 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Changelog Polish
Improve the automated changelog delta committed to develop by promote-to-prerelease.yml.
Scope: polish at packages/salesforcedx-vscode/CHANGELOG.md (per-package CHANGELOG.md files scoped to their own packages, out of scope). Root CHANGELOG.md is auto-maintained: promote-to-prerelease.yml prepends each week's delta, then stable builds later fold those sections into one stable release section via fold-stable-changelog.js — do not edit root manually.
When to use
- User invokes
/changelogor asks to prepare/review the changelog - On
develop, after achore: changelog for prerelease vX.Y.Zcommit lands - Timing matters: polish it before
build-github-release.yml(Wednesdays, 7 AM UTC). Stable builds fold develop's root CHANGELOG.md and overlay polish from package CHANGELOG.md into the shipped release version, then bake into the VSIX. Once that's run, content is frozen in the artifact — fixing afterward requires manually re-injecting into the release's VSIX asset.
File location
packages/salesforcedx-vscode/CHANGELOG.md on develop
Workflow
- Checkout/pull
developand read the current changelog file - Identify the automated commit:
git log --oneline -- packages/salesforcedx-vscode/CHANGELOG.md | grep "changelog for prerelease" - For each entry, fetch PR context:
gh pr view <number> --json title,body,commits,labels. In the body, look for a "What issues does this PR fix or reference?" section and extract any issue or discussion numbers linked there. - Apply the rules below to produce a polished draft
- Present the revised changelog to the user for approval before writing
Rules
1. Remove GUS work item references
Strip any W-NNNNNNN or - W-NNNNNNN text from entries. These are internal tracking IDs not meaningful to customers.
Before: - Add a Max Rows input to SOQL Builder UI - W-22199672 ([PR #7261](...
After: - We added a **Max Rows** input to SOQL Builder UI so you can limit the number of rows retrieved. ([PR #7261](...
2. Classify entries as customer-facing or under-the-cover
Under-the-cover (not visible to users):
- Test infrastructure (E2E suites, unit tests, test utilities)
- Internal telemetry/observability (span attributes, logging)
- Refactoring with no behavior change
- CI/CD pipeline changes
- Dependency bumps with no user-visible effect
- Internal API changes between packages
Customer-facing (visible to users):
- New commands, UI elements, or features
- Bug fixes that affected user workflows
- Performance improvements users would notice
- Behavior changes in existing features
Use PR commits, title, body, and labels to decide. When uncertain, check the diff: gh pr diff <number> --name-only to see which files changed.
Under-the-cover entries go under a dedicated ## Under the Hood section (no package sub-headers needed). Consolidate all under-the-cover PRs into one or a few lines:
- We made some under the hood changes. ([PR #NNNN](...), [PR #MMMM](...)).
3. Deduplicate multi-package entries
The automation lists the same PR under every package it touched. Consolidate to the most relevant user-facing package. If a change touched salesforcedx-vscode-services plus a feature extension, list it under the feature extension only.
4. Improve customer-facing descriptions
- Write from the user's perspective: "We added...", "We fixed...", "You can now..."
- Describe what the user can do or what changed for them, not the implementation
- Start with
We added…,We fixed a bug where…,We improved…,We reverted…, orThe <X> now…. Full sentences ending in. - Bold user-facing names: extensions (Salesforce Metadata Visualizer), commands (SFDX: Create Project), UI elements (Run button, Org Differences view, Ready for Review)
- Backticks for code identifiers, file names, config keys:
jsconfig.json,sourceApiVersion,MetadataRegistryService,.soql - Keep entries to 1-2 sentences max
- For opaque/internal fixes where customer impact is unclear:
We made some changes under the hood. - For reverts:
We reverted <X> because <reason>. - For setting/option additions: name the setting in bold, describe default behavior
- For extension-pack additions: include extension id in parens, e.g.
**Salesforce Live Preview** (salesforce.salesforcedx-vscode-ui-preview) - Prefer
VS CodeoverVSCode;on Windowsnotin Windows - After the PR link(s), append issue and discussion links found in the "What issues does this PR fix or reference?" section of the PR body:
- Issues:
[ISSUE #NNNN](https://github.com/forcedotcom/salesforcedx-vscode/issues/NNNN) - Discussions:
[DISCUSSION #NNNN](https://github.com/forcedotcom/salesforcedx-vscode/discussions/NNNN) - Format:
([PR #7517](...), [ISSUE #4065](...)) - Only include issues/discussions explicitly listed in that section; do not infer from commit messages or other body text
- Issues:
5. Verify categories
## Added— new features, new commands, new UI## Fixed— bug fixes## Changed— behavior changes to existing features (add section if needed)## Under the Hood— internal changes not visible to users (CI, telemetry, refactoring, dep bumps). No package sub-headers needed.- Remove empty package sections (header with no entries)
Example transformation
Automated:
## Added
#### salesforcedx-vscode-metadata
- Filter packageDirs to those containing target folder - W-22049669 ([PR #7225](...))
#### salesforcedx-vscode-services
- Filter packageDirs to those containing target folder - W-22049669 ([PR #7225](...))
- Replace static activationEvents with programmatic activation W-21956120 ([PR #7154](...))Polished:
## Added
#### salesforcedx-vscode-metadata
- When creating an Apex class or LWC component, the output directory picker now lists only package directories that contain the relevant folder. ([PR #7225](...))
## Under the Hood
- We made some under the hood changes. ([PR #7154](...))Commit and push
After user approves the polished changelog:
- Make sure you're on
developand up to date:git checkout develop && git pull - Stage only the changelog file:
git add packages/salesforcedx-vscode/CHANGELOG.md - Verify no other files are staged:
git diff --cached --name-onlymust show onlypackages/salesforcedx-vscode/CHANGELOG.md. If other files appear, unstage them before committing. - Commit:
git commit -m "chore: polish changelog [skip ci]" - Push:
git push origin develop
Never include other file changes in this commit.
Use these chore: subjects for polish commits on develop:
chore: polish changelogchore: write into sentenceschore: changelog improvementschore: update changelogchore: missing changelog entrychore: clean up duplicate entrieschore: merge vX.Y.A and vX.Y.B changelogs(when prior patch's entries need to roll into current)
Reference: changelog lifecycle
promote-to-prerelease.yml runs 3-stage pipeline to generate & polish changelog before commit to develop. Background context; typically not interacted with during manual polish.
Compute → Polish (AI) → Commit → Review (human)
- compute-changelog-range (promote-to-prerelease.yml): Outputs
fromRef= newestmarketplace-prerelease-*tag (set by last week's promote run) or latest stablev*tag (correct fallback before any tracking tag exists). EmptyfromRef(identical to this week's nightly commit — a manual re-run or hotfix) skips changelog-body instead of feeding it an identical range. - changelog-body (reusable workflow
.github/workflows/changelog-body.yml): Calls Cursor-backed AI (guided by.cursor/skills/changelog-judgment/SKILL.md) to produce polished, customer-facing markdown body from commits in range(fromRef, toRef]. Already removes GUS refs, rewrites sentences ("We added/fixed/improved..."), dedupes multi-package PRs, consolidates Under-the-Hood. Returnsbodyoutput. - write-changelog (promote-to-prerelease.yml): Writes header
# <version> - <date>+ body topackages/salesforcedx-vscode/CHANGELOG.md. Runsscripts/prepend-release-changelog.jsto prepend same content to rootCHANGELOG.md. Both labeled with prerelease version (e.g.67.17.9). Committed todevelop. - Polish (optional) (
develop, this skill): Human review/touch-up before nextbuild-github-release.ymlrun. Model-generated body is typically ready, but catch edge cases/errors using Rules 1–5 as checklist. Note: polish edits to package CHANGELOG.md are picked up by the stable build (via --overlay); edits to root are not auto-synced (folding process replaces root sections). - Fold to stable (
build-github-release.yml, Wednesday 7 AM UTC): For stable builds (skips emergency pre-releases): pulls develop's root CHANGELOG.md, overlays package CHANGELOG.md polish from step 4, folds every prerelease section it contains into one stable section (fold-stable-changelog.js), bakes into stable VSIX (package CHANGELOG.md). - Fold history (
publishVSCode.yml, on final stable publish): For stable releases (skips pre-release tags): folds develop's root CHANGELOG.md, so history matches shipped stable version; commits only root CHANGELOG.md to develop (no longer touches package changelog).
prepend-release-changelog.js validates structure (version format, file existence, non-empty), runs idempotent (skips if already in root), reports errors (ENOSPC, EACCES, missing files). fold-stable-changelog.js (run by build-github-release.yml and publishVSCode.yml) is also idempotent: no-op if root already starts with the stable version (pre-prepared branches), or if no prerelease sections fold into it (hotfixes of stable releases).
Commit details
- Commit:
chore: changelog for prerelease vXX.YY.ZZ [skip ci] - Range: previous week's promoted prerelease to nightly SHA (disjoint by construction — changelog-body doesn't read the existing file, so there's nothing to dedupe against)
- Skipped if changelog-body returns an empty body (no
feat/fix/perfcommits in range)
Format
# XX.YY.ZZ - Month DD, YYYY
## Added
#### <package-name>
- <message> ([PR #<num>](https://github.com/forcedotcom/salesforcedx-vscode/pull/<num>))
## Fixed
#### <package-name>
- <message> ([PR #<num>](...))
## Under the Hood
- We made some under the hood changes. ([PR #<num>](...), [PR #<num>](...))- Top header:
# <version> - <release date>; date is+7 daysfrom this Wednesday's prerelease (next Wednesday's stable release), written by thewrite-changelogjob, not changelog-body - Sections, in order:
Added,Fixed,Changed,Under the Hood. Section is an AI judgment call per.cursor/skills/changelog-judgment/SKILL.md(Added= new capability,Fixed= bugfix,Changed= behavior change,Under the Hood= invisible to users), not a fixed commit-type mapping — seescripts/changelogBody/changelogBody.mts - Kept commit types:
feat,fix,perf(everything else, e.g.chore/refactor/test/ci, is dropped before the AI step ever sees it) Under the Hoodentries are consolidated into one bullet with all their PR links, no package sub-header- Package sections:
#### <package-name>, alphabetical within a type - Bullet entries:
- <message> ([PR #N](url)); PR url formathttps://github.com/forcedotcom/salesforcedx-vscode/pull/<num> - Multiple PRs for one entry: comma-separate
([PR #A](...), [PR #B](...), [ISSUE #C](...), [DISCUSSION #D](...)) - Include
[ISSUE #N](https://github.com/forcedotcom/salesforcedx-vscode/issues/N)or[DISCUSSION #N](https://github.com/forcedotcom/salesforcedx-vscode/discussions/N)when listed in the PR's "What issues does this PR fix or reference?" section
Package filtering (auto)
- If
salesforcedx-vscode-coreis touched, all other touched packages (exceptdocs) are dropped for that commit - If
salesforcedx-vscode-servicesis touched alongside exactly one other (non-docs) package,salesforcedx-vscode-servicesis dropped and the other package keeps the entry - Only packages starting with
salesforceordocscount; path segments namedimagesortestare ignored when detecting touched packages - A commit whose surviving paths touch no qualifying package has an empty package set and goes to
Under the Hood
Commit parsing (auto)
- Requires conventional
type(scope): message+ trailing(#PR)to appear in the commit subject - Strips
[W-XXXXXXXX]GUS refs from the subject before it reaches the AI step - No dedupe against the existing changelog file — the range is disjoint by construction (see Commit details above)
Dedupe / merge rules (post-generation)
- Same PR listed under multiple packages: keep under the most user-relevant package, delete others (see Rule 3 above)
- Same PR listed twice in a section: collapse to one bullet
- Empty
#### <package>subsections: leave in place if auto-generated (keeps structure obvious), or remove during polish — match surrounding style - Patch release rolling into next: if v66.Y.A shipped but entries were missing, merge into v66.Y.B section and update the header date; see
chore: merge ... changelogs
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

