- Home
- Skills
- Technical Documentation
- Release Scribe
Works with the AI Agents you already use
Release Scribe
Turn Git history into changelogs, GitHub releases, App Store updates, and internal release briefs without inventing changes.
$7
Release Scribe
Example session with this skill installed
Use Release Scribe to prepare four artifacts for the changes from v1.3.2 through v1.4.0:
- A GitHub release body for users and integrators.
- A
CHANGELOG.mdentry that matches the repository's existing format. - Traditional Chinese App Store “What's New” notes.
- An internal release brief for support and operations.
Read the actual Git range and existing release conventions. Do not claim tests, performance results, issue closure, deployment state, or rollout state unless the repository evidence supports them. Return each artifact under a clear heading.
- Read your context and instructions
- Compiled the release scribe
GitHub Release — v1.4.0
Highlights
- Interrupted uploads can now continue from the last completed part instead of restarting from zero.
- Search filters remain selected when returning to the results page.
What's changed
Added
- Add resumable multipart uploads for files larger than 100 MB.
Changed
- Preserve search filters in route state so they survive navigation.
- Refresh authentication state before protected pages render.
Fixed
- Address the signed-out flash that could appear while an expired session was being refreshed.
CHANGELOG.md
Added
- Support resuming interrupted uploads from the last completed part.
Changed
- Preserve selected search filters when returning to the results page.
- Refresh authentication state before protected pages render.
Fixed
- Prevent the signed-out interface from appearing during session refresh.
App Store 更新說明
- 上傳中斷後,現在可以從先前進度繼續,不必重新開始。
- 返回搜尋結果時,原本選擇的篩選條件會繼續保留。
- 改善登入狀態更新期間的畫面穩定性。
Internal Release Brief
Summary
Version 1.4.0 adds resumable uploads, preserves search-filter state across navigation, and changes when authentication sessions are refreshed.
Customer impact
Users uploading large files should be able to continue after a network interruption. Search users no longer need to reselect filters after opening and leaving a result.
Rollout and operations
Deployment state and feature-flag availability were not present in the supplied repository evidence and require confirmation before release.
Verification
The release range includes automated test changes, but no CI result or completed manual-verification record was available. Test success is therefore not claimed.
Risks and known limitations
The behavior of resumable uploads across application upgrades was not documented in the supplied evidence and should be confirmed before general availability.
Connects securely to your tools. The creator never sees your data.
About this skill
Release Scribe turns a real Git range into release communication for four different audiences:
- GitHub and GitLab releases for users and integrators
- CHANGELOG entries that preserve the repository's existing format
- App Store, Play Store, and beta-channel “What's New” notes
- Internal release briefs for product, support, and operations
It does not paste a commit list into four templates. It gathers the exact tag or commit range, collapses implementation noise, removes reverted and duplicate work, separates user-visible changes from maintenance, and rewrites each artifact for the people who will read it.
The bundled Git helper is deterministic and performs no network requests or model calls. It reads commits, changed files, contributors, reachable tags, changelog conventions, and release templates from the local repository. The buyer's existing AI agent writes the final copy under strict source-integrity rules.
Release Scribe will not invent passed tests, performance numbers, production fixes, closed issues, completed rollouts, compatibility guarantees, or security claims. Drafting notes also does not silently publish a release, create a tag, push a commit, or edit a changelog.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Technical Documentation.
Requires a Git repository and an identifiable release boundary, such as two tags or commits. If no previous tag can be inferred, the buyer must provide the starting ref.
The bundled helper requires Git and Node.js 23.6 or newer. Older Node.js versions require a TypeScript runner such as tsx.
The helper reads local Git history only. Exact pull-request labels, review state, hosted CI results, and issue state require the buyer's agent to have authenticated access to the relevant Git provider.
Output quality depends on commit, diff, pull-request, changelog, and user-provided evidence. Release Scribe deliberately omits or marks unsupported operational claims instead of filling gaps with guesses.
Publishing a hosted release depends on the buyer's agent tools and authenticated Git-provider access. The skill does not create tags or push commits unless separately requested.
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 buying a skill.
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
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 21 days ago
- Software
Node.js
Git