agentmods.dev

release-sync

release-sync is a skill for Claude Code from me2resh/apexyard. It costs 35 tokens per session (5,806 once invoked), scanned A, original, MIT.

A Git workflow step that synchronizes the development branch with the main branch after a squash-merge release, where many commits are combined into one.

In plain words
What is it for?
Use it after a release to create a main-to-development pull request and make the release commit part of the development branch history.
Why use it?
It prevents repeated releases from accumulating duplicate history and causing avoidable merge conflicts.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions Claude Code.

not rated 542repo changed 1mo ago A scan SkillSpector: pass 35 tokens original MIT

Good fit Use it after a release to create a main-to-development pull request and make the release commit part of the development branch history.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/me2resh/apexyard/release-sync
View source ↗ me2resh/apexyard apexyard.ai
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add me2resh/apexyard --skill release-sync
Clone the repo
git clone --depth 1 https://github.com/me2resh/apexyard

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.

agentmods badge for release-sync

README.md
[![agentmods](https://agentmods.dev/badge/skills/me2resh/apexyard/release-sync/github.svg)](https://agentmods.dev/skills/me2resh/apexyard/release-sync)
Your own site
<a href="https://agentmods.dev/skills/me2resh/apexyard/release-sync"><img src="https://agentmods.dev/badge/skills/me2resh/apexyard/release-sync/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for release-sync

Your own site · 80×15
<a href="https://agentmods.dev/skills/me2resh/apexyard/release-sync"><img src="https://agentmods.dev/badge/skills/me2resh/apexyard/release-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,806 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00035 $0.05806
Opus 5.5 $0.00014 $0.02322
Sonnet 5.5 $0.00007 $0.01161
Haiku 4.5 $0.00003 $0.00581

Measured 1mo ago against content hash fdd4b3124f29, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

release-sync 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 1mo ago.

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/skills/release-sync/SKILL.md · 384 lines

How it starts

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

/release-sync — Sync main→dev after a release

The sync PR body is a durable, human-facing artefact. Read .claude/rules/writing-standard.md. Use the controlled technical writing profile: lead with the outcome and next action, use plain concise prose, and remove empty sections.

Every squash-merge release (dev → main) creates a SHA divergence: the squash commit on main is absent from dev, so dev still carries the un-squashed equivalents as separate commits. Repeated releases accumulate the divergence until the next dev → main release PR becomes a conflict-heavy nightmare (v2.0.0 suffered 99 conflicts because of this). This skill closes the loop: after each release, file a main→dev sync PR that makes the squash commit an ancestor of dev, so future release PRs only see genuinely-new commits.

This skill is framework-only — only for the me2resh/apexyard framework repo. It has no meaning on managed projects, which are trunk-based and never squash-merge to a separate main.

Usage

/release-sync v2.0.3

Typically invoked as the final step of /release, after the release tag has been pushed.

Process

1. Pre-flight

Verify:

  • Current repo IS the apexyard framework (origin or upstream points at me2resh/apexyard). Refuse otherwise.
  • <version> argument provided and matches v\d+\.\d+\.\d+. Refuse if missing or malformed.
  • upstream/main and upstream/dev exist (git rev-parse --verify). Refuse if either is absent.
  • The tag <version> exists on upstream/main (git tag -l <version>). Warn if absent (the release may not have completed yet).

2. Check for divergence

git fetch upstream main dev --tags
COMMITS_ON_MAIN_NOT_ON_DEV=$(git log upstream/dev..upstream/main --oneline | wc -l | tr -d ' ')
  • If COMMITS_ON_MAIN_NOT_ON_DEV -eq 0: already in sync — print a single-line message and exit 0 (no-op). Do NOT open a PR.
  • If only upstream/dev..upstream/main is empty but upstream/main..upstream/dev is also empty: branches are identical — exit 0.
  • If COMMITS_ON_MAIN_NOT_ON_DEV -gt 0: proceed with the sync.

Read the full file on GitHub · 384 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.

  1. 1mo ago Changed · +115 lines fdd4b3124f29
  2. 1mo ago Changed · +4 lines b4aae287b4b8
  3. 2mo ago First seen · 265 lines · 35 tokens per session scan A 30971570a5ed

Subscribe to this mod's changes

release-sync is a skill published in the GitHub repository me2resh/apexyard (542 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 5,806 once invoked, about $0.0001 per session on Opus 5.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-03.

Claude CodeGit and workflowReleasesagentic-codingai-agentsai-governanceclaude-code-hooksclaude-code-skills
Related

release-sync compared with skills from other repositories

release-sync next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
release-syncme2resh/apexyardSkill542yesterdayMITA35Claude Code
releaseparcadei/Continuous-Claude-v3Skill3.9k9mo agoMITA20Claude Code
releaseYeachan-Heo/oh-my-claudecodeSkill41kyesterdayMITA27Claude Code
changelog-generatordecebals/claude-code-javaSkill7708d agoMITA40Claude Code, Codex
releaseoliver-kriska/claude-elixir-phoenixSkill574yesterdayMITA60Claude Code
ln-62-release-publisherlevnikolaevich/claude-code-skillsSkill587yesterdayMITA24Claude Code
land-and-deployFlorianBruniaux/claude-code-ultimate-guideSkill6.4k2d agoCC-BY-SA-4.0A24Claude Code