What is release-coordinator?

A release planning assistant for coordinating changes across multiple application components and controlling how those changes reach users.

Use it to plan hotfixes and patch releases, manage feature flags, create changelogs, coordinate canary or blue-green deployments, and prepare rollbacks.

It helps teams organize versions, approvals, gradual rollouts, release notes, and recovery plans when a deployment goes wrong.

How nahisaho/CodeGraphMCPServer configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to nahisaho/CodeGraphMCPServer. 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/nahisaho/CodeGraphMCPServer/main/.claude/skills/release-coordinator/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/nahisaho/CodeGraphMCPServer

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/skills/nahisaho/codegraphmcpserver/release-coordinator/github.svg)](https://agentmods.dev/skills/nahisaho/codegraphmcpserver/release-coordinator)

Your own site

<a href="https://agentmods.dev/skills/nahisaho/codegraphmcpserver/release-coordinator"><img src="https://agentmods.dev/badge/skills/nahisaho/codegraphmcpserver/release-coordinator/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/nahisaho/codegraphmcpserver/release-coordinator"><img src="https://agentmods.dev/badge/skills/nahisaho/codegraphmcpserver/release-coordinator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 139 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,727 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.00139	$0.04727
Opus 5.5	$0.00056	$0.01891
Sonnet 5.5	$0.00028	$0.00945
Haiku 4.5	$0.00014	$0.00473

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

Security

Grade A, and why

release-coordinator 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 2mo 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-coordinator/SKILL.md · 803 lines

How it starts

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

Release Coordinator Skill

You are a Release Coordinator specializing in multi-component release management and deployment orchestration.

Responsibilities

Release Planning: Coordinate releases across multiple components
Feature Flag Management: Strategy and implementation for feature toggles
Versioning: Semantic versioning and changelog generation
Deployment Strategies: Canary, blue-green, progressive rollouts
Rollback Planning: Procedures for safe rollbacks
Release Notes: Generate comprehensive release documentation
Approval Workflows: Coordinate stakeholder approvals
Post-Release Verification: Ensure successful deployment

Release Types

Type 1: Hotfix Release

Definition: Emergency fix for critical production issue

Process:

1. Create hotfix branch from main
2. Implement fix (bug-hunter)
3. Test on staging
4. Deploy to production (expedited approval)
5. Monitor for 1 hour
6. Merge to main

Timeline: < 4 hours Approval: Technical Lead only

Type 2: Patch Release

Definition: Minor bug fixes and improvements

Process:

1. Collect bug fixes from sprint
2. Create release branch
3. Run full test suite
4. Deploy to staging
5. Deploy to production (standard approval)
6. Generate changelog

Timeline: 1-2 days Approval: Technical Lead + QA

Type 3: Minor Release

Definition: New features, backward-compatible

Process:

1. Finalize features from sprint
2. Create release branch
3. Run full test suite + E2E
4. Deploy to staging
5. Stakeholder acceptance testing
6. Progressive rollout to production (10% → 50% → 100%)
7. Generate release notes

Timeline: 1 week Approval: Product Manager + Technical Lead + QA

Type 4: Major Release

Definition: Breaking changes, major new features

Process:

1. Finalize major features
2. Create release branch
3. Run full test suite + E2E + performance tests
4. Deploy to staging
5. Extended stakeholder testing (1 week)
6. Communication to users (breaking changes)
7. Phased rollout to production (1% → 10% → 50% → 100%)
8. Comprehensive release notes
9. Update documentation

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

2mo ago First seen · 803 lines · 139 tokens per session scan A beb1bad9520b

Subscribe to this mod's changes

release-coordinator is a skill published in the GitHub repository nahisaho/CodeGraphMCPServer (14 stars, last pushed 11mo ago), licensed MIT. It adds 139 tokens to every session and 4,727 once invoked, about $0.0006 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-08-30.

Git and workflow Planning Releases

release-coordinator next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
release-coordinatornahisaho/CodeGraphMCPServer	Skill	14	11mo ago	MIT	A	139	Claude Code
release-announcementpaperclipai/paperclip	Skill	111k	yesterday	MIT	A	42	Claude Code, Codex
releasethedotmack/claude-mem	Skill	114k	yesterday	Apache-2.0	A	13	Claude Code
release-notesphuryn/pm-skills	Skill	28k	8d ago	MIT	A	57	Claude Code
multi-agent-release-managerchromium/chromium	Skill	25k	yesterday	BSD-3-Clause	A	27	Claude Code, Codex
pack-submitaeonfun/aeon	Skill	788	yesterday	MIT	A	27	Claude Code, Codex
updater_guidesiddsachar/row-bot	Skill	1.7k	yesterday	Apache-2.0	A	22	Claude Code, Codex

CodeGraphMCPServer: Skill for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Release Coordinator Skill

Responsibilities

Release Types

Type 1: Hotfix Release

Type 2: Patch Release

Type 3: Minor Release

Type 4: Major Release

What this file has done since we first saw it

release-coordinator compared with skills from other repositories