frb-write-changelog
Update flutter_rust_bridge CHANGELOG.md for a new release by collecting merged PRs since the previous version tag, mapping them to the target release section, and formatting entries to match the existing changelog style. Use when writing or refreshing a release section in CHANGELOG.md.
Оригинален текст · няма потвърден превод на българскиПърво прочетете инструкцията.
Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.
GitHub хранилище- Звезди на репото
- 5283
- Лиценз
- Не е посочен. Проверете в репозитория.
- Последна проверка на записа
- Няма посочена дата
Добавете в своя инструмент.
Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.
npx skills add fzyzcjy/flutter_rust_bridgeСтраницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.
Откъс от SKILL.md
Началото на файла на автора, без превод.
FRB Write Changelog
Step 1: Inspect CHANGELOG.md
Read the top of CHANGELOG.md.
- Confirm the target version section exists, or add it.
- Keep the existing V2 "what's new" header line.
- Inspect
git diff -- CHANGELOG.mdbefore editing. - Replace only the target section if it already contains a placeholder such as
* TODO.
Step 2: Identify the previous release tag
Find the latest release tag before the target version.
git tag --sort=-creatordate | head -n 20
Use that tag as the lower bound for the new changelog entry.
Step 3: Collect merged PRs
Use GitHub CLI to collect merged PRs after the previous version.
gh pr list --state merged --limit 200 --json number,title,author,mergedAt,baseRefName,url
gh pr view <number> --json number,title,author,url
Use the previous version as the lower bound when deciding which merged PRs belong to the target release.
Step 4: Filter and normalize
Keep all PRs in merged status that belong to the release range.
- Exclude unmerged PRs.
- Exclude PRs outside the release range.
- When refreshing an already-published release, use both the previous release timestamp and the target release tag timestamp so later post-release PRs are not pulled into the published section.
- Do not filter by target branch.
- Keep docs, CI, and chore PRs if they are merged in the range.
- Exclude only all-contributors PRs such as
docs: add <name> as a contributor for code/doc; do not exclude ordinary documentation PRs whose titles start withdocs: add.
Normalize titles before writing.
- Rewrite noisy internal titles into concise changelog language.
- Avoid duplicate summaries for split or "continued" PRs.
- Preserve repo-specific capitalization such as
CI,GitHub,Flutter,Rust,DCO, andV1.
Step 5: Write the section
Match the existing changelog style.