- Home
- Skills
- Technical Documentation
- blaryx Changelog Generator
blaryx Changelog Generator
Turn real Git history into concise, evidence-based release notes and changelogs.
Free
Works with the AI Agents you already use
blaryx Changelog Generator
Example session with this skill installed
Generate maintainer-facing release notes for the public Blaryxoff/agentic-devkit repository, range 74e17f1~3..74e17f1. Read the diffs, summarize actual behavior changes, and state whether any migration is needed.
- Read your context and instructions
- Compiled the blaryx changelog generator
Changelog: 74e17f1~3..74e17f1
Summary
QA follow-up comments now distinguish completed source fixes from confirmed production deployments more clearly. Comments can retain the rollout and verification details required by the project.
Changed
- When the evidence confirms that QA fixes reached production, the follow-up explicitly says they were deployed to production. Staging evidence alone does not support that statement.
- QA workflows pass deployment identifiers, rollout times, checked scenarios, observed results and actual roles to the commenting workflow when the project requires those details.
- Required artifact or version identifiers are preserved even when they contain a branch-like prefix. Ordinary branch names remain excluded from task comments.
- Missing deployment or verification evidence is reported to the operator rather than invented.
Migration notes
No application migration or configuration change appears in this range: the changes affect two workflow documents.
Evidence
Reviewed 3 commits and 2 changed files: 18 insertions and 5 deletions. This example was produced from the actual repository diffs; it does not claim a production deployment took place.
Connects securely to your tools. The creator never sees your data.
About this skill
A free skill by blaryx, from the agentic-devkit toolkit.
Turn real repository history into release notes that explain what changed and why it matters. The workflow resolves a tag, date or branch range, checks commits against actual diffs, groups meaningful features and fixes, filters noise, and highlights breaking changes, migrations and deployment risks.
Requires Git and an agent with read access to the repository and a terminal. No agentic-devkit installation, scripts, paid services or API keys are required. The separate Russian release-post workflow mentioned in the skill routing is outside this standalone listing.
Explore agentic-devkit and follow blaryx: https://github.com/Blaryxoff/agentic-devkit GitHub profile: https://github.com/Blaryxoff
Requires Git, repository read access and an agent with terminal access. Use a focused range that fits the agent’s context. Ambiguous history may need human clarification. Output requires review before publication; the package includes no runtime or special large-history feature.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 18 days ago
- Free with an Agensi account
Requires
Permissions
Reads Git history and relevant diffs to substantiate release notes. Does not require writing files, network access or credentials.