Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Generate clear, formatted release notes from git commits, PR titles, or change descriptions, grouped by change type and suitable for different audiences and...
Generate clear, formatted release notes from git commits, PR titles, or change descriptions, grouped by change type and suitable for different audiences and...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Generate clear, professional release notes from git commits, PRs, or a plain list of changes. Outputs formatted changelogs your users actually want to read.
Tell the agent what changed โ paste commits, PR titles, or describe features in plain language. It produces structured release notes.
Git diff/log โ paste git log --oneline v1.2.0..v1.3.0 output PR list โ paste merged PR titles Plain description โ "We added dark mode, fixed the login bug, and dropped Python 3.7 support"
Group changes by type: Added, Changed, Fixed, Deprecated, Removed, Security, Breaking Changes Follow Keep a Changelog conventions Include migration guides for breaking changes Write for end users, not engineers (unless told otherwise) Strip internal/refactor commits unless asked to include them Add PR/issue numbers when available Keep it scannable โ bullet points, not paragraphs
Say "internal" for eng-focused notes or "external" for customer-facing notes. Default is external.
Ask for: Changelog โ append-friendly CHANGELOG.md format Email โ ready to paste into a release email Slack โ compact format for #releases channel GitHub Release โ markdown for GitHub release page Tweet thread โ highlight reel for social
Run after every sprint or before every deploy Pair with a CI step that dumps git log into a file Keep a running CHANGELOG.md and append each release Built by AfrexAI โ AI context packs for business teams ($47/pack). See our AI Revenue Calculator to find what automation is costing you.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.