agentleFS
Sign inStart free
streetsidesoftwarestreetsidesoftware/vscode-spell-checker/.claude/skills/release-notes/SKILL.md

release-notes

Skill1.7k starsChanged 32 days agoLicence not identifiedView on GitHub

Correct a merged PR''s Release Please changelog entry after its Conventional Commit type or message turned out wrong, for example a PR merged as `fix:`/`feat:` that should have been `chore:`/`refactor:`/`docs:`, a `fix:` that is really a new capability, or a changelog line that users would find confusing. Works by adding a BEGIN_COMMIT_OVERRIDE/END_COMMIT_OVERRIDE block to the merged PR''s description, which Release Please reads on its next run instead of the commit message. Use this whenever the user asks to fix, override, correct, or reclassify a PR''s release notes, changelog entry, or commit message after merge, mentions BEGIN_COMMIT_OVERRIDE, or wants to audit the open release PR (title like "chore(main): release code-spell-checker X.Y.Z") for entries that do not belong in the release notes. Trigger even without the words "release notes": "that PR should not have been a fix", "the changelog has internal stuff in it", "can we reclassify #5482" are all candidates. Does not rewrite git history; only changes what Release Please picks up from now on.

We split this skill into the rules it gives an agent

8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 152 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 152 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.

Trending

Quiet since July.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 1 mentionMay 2026: 0 mentionsJun 2026: 3 mentionsJul 2026: 1 mentionAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the streetsidesoftware/vscode-spell-checker repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about streetsidesoftware/vscode-spell-checker

The biggest 5 of 51 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 51

Talked about on GitHub and Bluesky (51 times).

On GitHub · 50

45 more on GitHub
  • Other versions166 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 2

    1. streetsidesoftware/cspell★ 1.7k17% same
    2. streetsidesoftware/cspell-dicts★ 29420% same

    Wrote their own version · 164

    1. tw93/Mole★ 74ksame name
    2. makeplane/plane★ 62ksame name
    3. tabler/tabler★ 42ksame name
    4. pnpm/pnpm★ 37ksame name
    5. quasarframework/quasar★ 27ksame name
    6. dotnet/core★ 22ksame name
    7. zauberzeug/nicegui★ 16ksame name
    8. adobe/react-spectrum★ 16ksame name
    9. espanso/espanso★ 15ksame name
    10. formbricks/formbricks★ 13ksame name

    154 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.

  • Used alongsideProjects with it also use brainstorm-experiments-existing, brainstorm-ideas-new 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.
    • skytiger6724Skill

      brainstorm-experiments-existing

      Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.

      Also in 6 projects that use this

    • skytiger6724Skill

      brainstorm-ideas-new

      Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.

      Also in 6 projects that use this

    • 45ckSkill

      pestle-analysis

      Also in 6 projects that use this

    • +9 more from skytiger6724
  • In this repository5 other files it gives its agents.

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