agentleFS
Sign inStart free
forcedotcomforcedotcom/salesforcedx-vscode/.cursor/skills/changelog-judgment/SKILL.md

changelog-judgment

Skill1k starsChanged 26 days agoBSD-3-ClauseView on GitHub

Turn changelog facts into changelog sections JSON. The changelog body script is the only caller.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about forcedotcom/salesforcedx-vscode

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

45 more on GitHub

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every fact pr appears once, in exactly one array.

    line 16
  2. Very specific:

    Start with We added, We fixed a bug where, We improved, We reverted, or The <X> now.

    line 20
  3. Very specific:

    Prefer VS Code. Say on Windows.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Changelog judgment

Reply with one JSON object and no other text. No markdown fences.

Keys, each an array: Added, Fixed, Changed, Under the Hood.

Each element: pr (number), sentence (string), and package (string). Omit package on Under the Hood elements.

Every fact pr appears once, in exactly one array. package is one of that fact's packages. A fact with an empty packages array goes in Under the Hood.

sentence is one or two sentences for a customer:

  • Start with We added, We fixed a bug where, We improved, We reverted, or The <X> now. End with .
  • Bold user-facing names. Backtick code identifiers, file names, and config keys.
  • Describe what the user can do, not the implementation.
  • Added is new capability. Fixed is a bugfix. Changed is a behavior change of something that already existed. Under the Hood is invisible to users (telemetry, refactor, CI, bundle size, internal API). A perf fact is Under the Hood unless a user would notice the speedup.
  • Prefer VS Code. Say on Windows.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free