changelog

Files (1)

• SKILL.md

SKILL.md (first lines)

# Generating changelog

Call shell_command tool with "git --no-pager log --reverse main..HEAD" argument.
Based on the output write changelog in org-mode list format. Use org quoting
(~quoted-text~) instead of markdown quoting (`quoted-text`). Every changelog
element should be ended with full stop. Changelog shouldn't be too short or too
long, use detailed description for major changes and concise description for
minor changes. Humanize it before writing using **humanize-writing** skill.

Call shell_command tools with "git --no-pager tag -l --points-at=main" argument
to see previously released version. Based on this information and
minority/majority of the changes you can fill version variable. If you are not
sure, ask the user using ask_user tool with your variants of the version.

Write it to ./NEWS.org using **prepend_file** tool
with header:

* Version {version}

After header should be changelog content. Content MUST ends with single
newline.
Example:
 ```text
* Version {version}
- Some change description. Some additional information.
- Major change detailed description. This change improves ~ellama-something~.
  Some additional information.
- Third change description.
- Some fix in ~ellama-example-command~ description.
```

After generating the changelog, update the version in ellama.el, commit the
generated release changes with the exact commit message "Bump version", and
push.

From s-kostyaev/ellama, GPL-3.0.

More from s-kostyaev/ellama