agentleFS
dotnetcoredotnetcore/BootstrapBlazor/.agents/skills/release-notes/SKILL.md

release-notes

Skill5k starsChanged 5 days agoApache-2.0View on GitHub

Create, curate, or translate BootstrapBlazor release notes in English and Chinese from GitHub-generated notes or user-provided change data. Use for versioned release-note tasks in this repository.

187 other projects use a version of this.

Trending

More talk lately.about the whole repository

Dec 2025: 5 mentionsJan 2026: 6 mentionsFeb 2026: 5 mentionsMar 2026: 8 mentionsApr 2026: 6 mentionsMay 2026: 1 mentionJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 1 mentionOct 2026: 1 mentionNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the dotnetcore/BootstrapBlazor repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about dotnetcore/BootstrapBlazor

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

See all 50

Talked about on GitHub (50 times).

On GitHub · 50

45 more on GitHub

Used with

Projects 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

  • About-IntelligenceSkill

    positioning-ideas

    Brainstorm product positioning ideas differentiated from competitors.

    Also in 6 projects that use this

  • About-IntelligenceSkill

    product-name

    Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience.

    Also in 6 projects that use this

  • +7 more from skytiger6724
  • Other versions187 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 187

    1. tw93/Mole★ 75ksame 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

    177 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 repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 172 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create matching English and Chinese release-note drafts for this repository.

    line 8
  2. Distinctive:

    If the user supplies a source file or explicit change list, use that as the scope instead of adding unrelated PRs from elsewhere.

    line 26
  3. Very specific:

    Keep the note concise and user-facing.

    line 30
  4. Distinctive:

    Do not silently drop a change because a later revert or follow-up appears.

    line 32
  5. Distinctive:

    When one component or dependency was upgraded several times during the release range, normally report the final version.

    line 33
  6. Distinctive:

    Do not invent behavior or implementation details beyond the generated notes, linked PR information, or user-confirmed edits.

    line 34
  7. Distinctive:

    Keep dates, versions, section and entry order, authors, PR links, and Full Changelog links aligned in both files.

    line 41
  8. Distinctive:

    Use this entry format:

    line 43
  9. Distinctive:

    Use this document structure:

    line 50
  10. Distinctive:

    Ensure no unrequested PRs were added and no user edits were lost.

    line 70

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

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

BootstrapBlazor Release Notes

Create matching English and Chinese release-note drafts for this repository. Do not publish a GitHub Release or create a tag.

Gather release data

  1. Identify the latest published stable release tag from the repository's releases/tags. Do not use prereleases as the baseline unless requested.
  2. Get the target version from the user's request; if the request says "current version", check the project version. Use the requested release date; if none is given, use the current date.
  3. Compare the target version with the latest stable version. If the target is not newer, stop and tell the user that no release notes are needed until a newer release tag is available; do not generate notes or create/update files. In particular, a project prerelease for a version that is already stable does not count as a newer release.
  4. Use GitHub's generated release notes as the default source; the user does not need to provide a separate raw file. This step requires the gh CLI, an authenticated GitHub account (gh auth status), and network access; cloud or CI agents may not have them. For dotnetcore/BootstrapBlazor, generate notes without creating a release:

    gh api --method POST repos/dotnetcore/BootstrapBlazor/releases/generate-notes \
      -f tag_name=vX.Y.Z \
      -f previous_tag_name=vPREVIOUS \
      -f target_commitish=main \
      --jq .body

    Replace the example tag values with the confirmed target and previous tags. The endpoint returns generated text; it does not publish a release. The GitHub draft page at https://github.com/dotnetcore/BootstrapBlazor/releases/new can also generate the same source. If the gh CLI, authentication, or GitHub access is unavailable, explain the blocker and use raw change data only if the user provides it.

  5. If the user supplies a source file or explicit change list, use that as the scope instead of adding unrelated PRs from elsewhere.

Curate the changes

  • Keep the note concise and user-facing. Organize fix entries under Fixes and feat entries under Features; the Chinese headings are 修复 and 新功能.
  • Exclude documentation-only and internal maintenance changes from these sections unless the user asks to include them.
  • Do not silently drop a change because a later revert or follow-up appears. Inspect the related entries and ask the user when the final shipped behavior is unclear.
  • When one component or dependency was upgraded several times during the release range, normally report the final version. Keep PR references that support the summarized change; follow the user's manually curated English version when it differs.
  • Do not invent behavior or implementation details beyond the generated notes, linked PR information, or user-confirmed edits.

Write the two files

  • Save versioned notes as ChangeLogs/{version}_en.md and ChangeLogs/{version}_zh.md at the repository root. Create ChangeLogs/ if it does not exist.
  • Preserve existing files and manually edited content. In particular, do not overwrite an existing English note without explicit instruction.
  • Draft English first. Translate the final, user-confirmed English note into Chinese; do not reconstruct the Chinese version independently from older raw data.
  • Keep dates, versions, section and entry order, authors, PR links, and Full Changelog links aligned in both files.
  • Translate only prose. Preserve component/scope names, commit prefixes, API and parameter identifiers, package names, version numbers, usernames, and URLs.
  • Use this entry format:

    * fix(Component): concise description by @author in https://github.com/dotnetcore/BootstrapBlazor/pull/123
    * feat(Component): concise description by @author in https://github.com/dotnetcore/BootstrapBlazor/pull/124
  • Use this document structure:

    ## Release YYYY-MM-DD VX.Y.Z
    
    ### Fixes
    ...
    
    ### Features
    ...
    
    **Full Changelog**: https://github.com/dotnetcore/BootstrapBlazor/compare/vPREVIOUS...vCURRENT

    In the Chinese file, translate the section headings and descriptions while retaining the same structure and identifiers.

Final review

  • Confirm the title date, version, previous tag, and Full Changelog comparison.
  • Compare both files for matching PR IDs, authors, entry counts, and ordering.
  • Ensure no unrequested PRs were added and no user edits were lost.
  • Report the paths of both files and any unresolved inclusion or release-range decisions.

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.