MediaMetz/gemini-cli
1
0
Fork 0
mirror of https://github.com/google-gemini/gemini-cli.git synced 2026-05-12 21:03:05 -07:00
Code Issues Packages Projects Releases Wiki Activity

Update SKILL.md

Browse Source
This commit is contained in:
g-samroberts
2026-02-05 12:32:07 -08:00
parent 12501c3e20
commit b828186779
1 changed files with 17 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gemini/skills/docs-changelog/SKILL.md
+17 -5
View File
@@ -23,6 +23,8 @@ This skill covers two types of releases:
* **Preview Releases:** Pre-release versions for testing and feedback. These * **Preview Releases:** Pre-release versions for testing and feedback. These
updates only modify `docs/changelogs/preview.md`. updates only modify `docs/changelogs/preview.md`.
Ignore all other releases, such as nightly releases.
### Expected Inputs ### Expected Inputs
Regardless of the type of release, the following information is expected: Regardless of the type of release, the following information is expected:
@@ -50,7 +52,10 @@ Regardless of the type of release, the following information is expected:
### Analyze Raw Changelog Data ### Analyze Raw Changelog Data
1. Review the complete list of changes. 1. Review the complete list of changes. If it is a patch or a bug fix with few
changes, skip to the "Update `docs/changelogs/latest.md` or
`docs/changelogs/preview.md`" section.
2. Group related changes into high-level categories such as 2. Group related changes into high-level categories such as
important features, "UI/UX Improvements", and "Bug Fixes". Use the existing important features, "UI/UX Improvements", and "Bug Fixes". Use the existing
announcements in `docs/changelogs/index.md` as an example. announcements in `docs/changelogs/index.md` as an example.
@@ -77,8 +82,11 @@ Write concise summaries including the primary PR and author
### Update `docs/changelogs/latest.md` or `docs/changelogs/preview.md` ### Update `docs/changelogs/latest.md` or `docs/changelogs/preview.md`
1. Read current content and use `write_file` to replace it with the new 1. Read current content and use `write_file` to replace it with the new
version number, date, comprehensive highlights, and the full version number, and date.
"What's Changed" list.
If it is a patch or bug fix with few changes, simply add these
changes to the "What's Changed" list. Otherwise, replace comprehensive
highlights, and the full "What's Changed" list.
2. For each item in the "What's Changed" list, keep usernames in plaintext, and 2. For each item in the "What's Changed" list, keep usernames in plaintext, and
add github links for each issue number. Example: add github links for each issue number. Example:
@@ -90,11 +98,15 @@ Write concise summaries including the primary PR and author
4. Do not add the "New Contributors" section. 4. Do not add the "New Contributors" section.
5. Ensure lines are wrapped to 80 characters. 5. Update the "Full changelog:" link with the previous version and the new
vesion, unless it is a patch or a bug fix, in which case simply update the
link's new version and keep the previous version the same.
6. Ensure lines are wrapped to 80 characters.
### Update `docs/changelogs/index.md` ### Update `docs/changelogs/index.md`
Skip this step for preview releases. Skip this step for patches, bug fixes, or preview releases.
Insert a new "Announcements" section for the new version directly Insert a new "Announcements" section for the new version directly
above the previous version's section. Ensure lines are wrapped to above the previous version's section. Ensure lines are wrapped to