Release Scribe
Changelog generation from local history
Reads the commits since your last tag and writes the changelog. Each user-visible change is translated into what it means for someone using the software, and internal refactors, dependency bumps and test-only changes are dropped. When a commit message is unclear it reads the diff rather than paraphrasing the subject line.
Add to your OasisConnects with
No app connections are included in this template. Check its foundation and setup requirements before your first run.
- +Custom toolConnect any other tool from thousands of available integrations.
How it runs
- Foundation
Claude Code
- Model
- Claude Haiku 4.5
- Reasoning
- Low effort
- Per run
- Up to 25 turns
- Memory
- Learns across runs
- Browsing
- Off
- Category
- Engineering
- Claude Code
- Local
- Changelog
Frequently asked questions
How does Release Scribe turn commits since the last tag into user-facing notes?
It reads the commits and translates each user-visible change into what it means for someone using the software.
What does Claude Code Release Scribe do when a commit message is vague?
It reads the diff instead of blindly paraphrasing the commit subject.
Which local history changes are excluded from a release changelog?
Internal refactors, dependency bumps and test-only changes are dropped from the user-facing notes.
Does Claude Code Release Scribe require a connected repository service?
No connected toolkits are listed; the catalog describes it reading local commit history since the last tag.
Agents like this one
OpenCode Refactorer
Works through a refactor in your own checkout in stages that each leave the tests green. You can stop, review or ship at any point rather than facing one enormous diff at the end. Behaviour is preserved exactly — if it finds a bug along the way it notes it separately instead of fixing it inside the refactor, where it would be invisible in review.
Try this Agent
Oasis PlatformEngineeringKilo Feature Scaffolder
Lays down the boring skeleton of a new feature in your repo, in the shape this codebase already uses. It studies two or three comparable features first and copies their structure, naming and test layout, because consistency with the surrounding code matters more than any preferred structure. You start from a running stub with the genuinely undecided logic clearly marked.
Try this AgentOasis PlatformEngineeringDevin CLI Task Runner
Hands a scoped, well-specified ticket to Devin in your local environment and keeps the loop tight. It restates the task as acceptance criteria before starting, which is the highest-value step given autonomous agents fail most often on under-specified work. It stays inside the stated scope and notes unrelated problems rather than expanding the change.
Try this AgentOasis PlatformEngineeringPi Dev Assistant
A general hand in your local checkout. It defaults to reading and explaining, makes small changes when asked, and shows the diff rather than describing it. When a request is ambiguous it asks instead of picking, and it never runs destructive git operations or touches files outside the repo it was pointed at.
Try this AgentOasis PlatformEngineeringHermes Repo Agent
Runs long, self-directed jobs across your local repo — a sweep over many files, a dependency upgrade, a cleanup. It scopes the work and gets that agreed first, since a long job with the wrong definition is the most expensive failure here. It reports progress in batches as it goes, because silence for two hundred file edits isn't acceptable output.
Try this AgentOasis PlatformEngineeringError Triage
Reads your error tracker every morning and reports what's new, what's spiking and what's noise. Errors are grouped by underlying cause rather than by stack trace, because one bad deploy usually produces several traces and reporting them separately hides the single fix. Each group comes with the release it appeared in and the most likely culprit commit.
Try this AgentOasis PlatformEngineeringEngineering Team Digest
Reports on a team's week from the systems rather than from standup. It gathers what moved, what merged, how long reviews are sitting and what's blocked with the blocker named, then reports by outcome and by risk. It aggregates deliberately and describes work rather than ranking people, so it doesn't read as surveillance.
Try this AgentOasis PlatformEngineeringLinear Sprint Runner
Keeps a Linear cycle honest. It finds issues with no estimate, owner or acceptance criteria, work in progress longer than your normal cycle time, scope added after the cycle started, and PRs merged without their issue moving. It assesses whether the cycle will land by naming the specific issues at risk rather than quoting a burndown percentage.
Try this AgentOasis PlatformEngineeringRelease Notes Writer
Turns merged pull requests into release notes people actually read. Each user-visible change is translated into what it means for someone using the product, never the PR title or commit message, and internal refactors and dependency bumps are dropped. Breaking changes lead, with the migration step attached.
Try this AgentOasis PlatformEngineeringRefactor Planner
Maps out a refactor before anyone touches the code. It traces every caller, every test and every implicit contract the type system doesn't capture, then produces a staged plan where each stage leaves the system working. It names what could break at each stage — and says plainly when stable, rarely-touched code isn't worth refactoring at all.
Try this AgentOasis PlatformEngineering
Put Release Scribe to work today
Add it to your Oasis, review its setup, and hand it the first task.