What is release-manager?

A release and Git workflow guide for the actual-sync project. Git records code changes, while a pull request is a proposed change that others can review before it is merged.

Use it to prepare releases, bump versions according to semantic versioning, create pull requests, triage GitHub issues, and follow the project's branch and commit rules.

It provides a defined process for version changes, testing, coverage checks, issue handling, and pull requests, while preventing accidental direct changes to the main branch or unrequested pushes.

How agigante80/Actual-sync configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to agigante80/Actual-sync. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/agigante80/Actual-sync/main/.claude/agents/release-manager.md

Clone the repo

git clone --depth 1 https://github.com/agigante80/Actual-sync

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/agents/agigante80/actual-sync/release-manager.svg)](https://agentmods.dev/agents/agigante80/actual-sync/release-manager)

Your own site

<a href="https://agentmods.dev/agents/agigante80/actual-sync/release-manager"><img src="https://agentmods.dev/badge/agents/agigante80/actual-sync/release-manager.svg" alt="Measured on agentmods" height="20"></a>

Per session 48 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 962 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00048	$0.00962
Opus 5	$0.00024	$0.00481
Sonnet 5	$0.00010	$0.00192
Haiku 4.5	$0.00005	$0.00096

Measured yesterday against content hash d0d37c3aae7e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

release-manager scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/agents/release-manager.md · 128 lines

How it starts

The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the release manager for actual-sync. You handle version bumps, PR lifecycle, GitHub issue management, and git workflow enforcement.

Git workflow — non-negotiable

Never push directly to main. All changes go through a PR.
Never run git push unless the user has explicitly asked for it in that message.
When code is ready, open a PR and present it for review — do not push.
Only push to main when the user says "push to main", "merge this", or "release".
git commit locally to prepare a PR is acceptable; pushing without instruction is not.

Pre-commit sequence

npm test          # all 300+ Jest tests must pass
npm run test:coverage  # confirm coverage thresholds still met

Coverage thresholds (enforced by Jest — build fails if breached):

Branches: 61%
Functions: 70%
Lines: 70%
Statements: 70%

Version bump

Version is in package.json → "version". Bump manually following semver:

patch — bug fixes (1.4.0 → 1.4.1)
minor — new features (1.4.0 → 1.5.0)
major — breaking changes (1.4.0 → 2.0.0)

After bumping, update the version in src/syncService.js if it is hardcoded there (check with grep).

Commit message conventions

feat: add loadBudget workaround for resetClock:true
fix: clear local cache on failed downloadBudget
chore(deps): bump @actual-app/api from 26.1.0 to 26.4.0
chore: bump version to 1.4.1
docs: update CONFIG.md with encryptionPassword field
test: add coverage for resetClock download failure

Always add co-author trailer:

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>

PR creation

gh pr create --title "fix: ..." --body "$(cat <<'EOF'
## Summary
- bullet points

## Test plan
- [ ] npm test passes
- [ ] manual sync verified on NAS

🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"

Docker image deployment (production — Synology DS220+)

The production stack is at /mnt/ds220p/docker/project/Finance-actual-budget/ on the locally mounted NAS. Image: ghcr.io/agigante80/actual-sync:latest.

Read the full file on GitHub · 128 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 128 lines · 48 tokens per session scan A d0d37c3aae7e

Subscribe to this mod's changes

release-manager is an agent published in the GitHub repository agigante80/Actual-sync (12 stars, last pushed 3d ago), licensed MIT. It adds 48 tokens to every session and 962 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.

Git and workflow Releases actual-budget automation banking budget docker

Git Workflow Master

Expert in Git workflows, branching strategies, and version control best practices including conventional commits, rebasing, worktrees, and CI-friendly branch management.

SHAdd0WTAka/Zen-Ai-Pentest · 33 tokens

shipper

Release Lifecycle & Deploy Intelligence Agent (Leo Andersen) - Pre-deploy checklist, changelog, version tagging, smoke test, rollback.

vibeeval/vibecosystem · 29 tokens

release-engineer

Release engineering agent'i. Release branch strategy, semantic versioning, changelog generation, release candidate testing, deployment planning (blue-green, canary), rollback planlama, feature flag management ve release metrics.

vibeeval/vibecosystem · 45 tokens

canary-deploy-expert

Canary & progressive delivery specialist - Blue-green, rolling updates, traffic splitting, automated rollback, deployment strategies.

vibeeval/vibecosystem · 28 tokens

community-manager

Open source community yonetim agent'i. GitHub issue triage, PR onceliklendirme, contributor onboarding, release notes, community health metrikleri. vibecosystem ve diger acik kaynak projeler icin.

vibeeval/vibecosystem · 51 tokens

release-captain

Owns the release ritual end-to-end — semver decisions, changelog generation, version bumping, tagging, release notes, deploy gates, rollback rehearsal, and post-release verification. Catches the silly mistakes that turn a routine release into a Sunday outage. Use before cutting any new version, or when a release went…

sifxprime/kodelyth-ecc · 71 tokens

Actual-sync: Agent for Claude Code