changelog
Use this skill to generate changelog.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
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.
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:
* 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 all of that call shell_command tool with "make refill-news" argument.
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-03-11
- Index updated
- 2026-03-11
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!