메뉴
Update version in pyproject.toml, plugin.json, and add changelog entry. This skill should be used when the user wants to bump the version number and update CHANGELOG.md. Triggered by /release or /version commands.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | release |
| license | MIT |
| description | Update version in pyproject.toml, plugin.json, and add changelog entry. This skill should be used when the user wants to bump the version number and update CHANGELOG.md. Triggered by /release or /version commands. |
This skill updates the project version, plugin version, and changelog.
/release [version-type-or-number] [description]
patch - Increment patch version (e.g., 0.2.12 → 0.2.13)minor - Increment minor version (e.g., 0.2.12 → 0.3.0)major - Increment major version (e.g., 0.2.12 → 1.0.0)X.Y.Z - Set specific version (e.g., 1.0.0)If the version type is omitted, auto-detect the bump level from commits since the latest tag using the standard Semantic Versioning + Conventional Commits mapping:
BREAKING CHANGE: in the body or ! before the
colon in the subject (e.g. feat!:, refactor(core)!:).feat: (or feat(scope):) commit.Procedure:
git describe --tags --abbrev=0 → latest tag. If this command exits non-zero
because the repository has no tags yet, fall back to the full history:
git log HEAD --pretty=%H%x00%s%x00%b (initial commit → HEAD) and treat
every commit as "unreleased".git log <tag>..HEAD --pretty=%H%x00%s%x00%b → commits to
classify. (NUL-separated fields keep multi-line bodies parseable.)No commits since <tag>; nothing to release.post-impl-codex unblocked.Explicit argument always wins. If the user passes patch/minor/major/X.Y.Z,
skip auto-detection entirely.
If provided, use as the changelog entry description. Otherwise, analyze recent commits to generate the changelog.
Read pyproject.toml and extract current version:
# Look for: version = "X.Y.Z"
Based on the version type:
major.minor.patch → major.minor.(patch+1)major.minor.patch → major.(minor+1).0major.minor.patch → (major+1).0.0Validate the new version is greater than current (unless forced).
Edit pyproject.toml:
version = "NEW_VERSION"
Edit plugins/synapse-a2a/.claude-plugin/plugin.json:
"version": "NEW_VERSION",
Important: Keep plugin version in sync with pyproject.toml version.
Update hardcoded version strings in GitHub Pages documentation:
site-docs/getting-started/installation.md — version example in verification section:
You should see the version number (e.g., `NEW_VERSION`).
site-docs/concepts/a2a-protocol.md — Agent Card JSON example:
"version": "NEW_VERSION",
site-docs/changelog.md — add new version entry at the top of "Recent Highlights" (only if CHANGELOG.md was updated in Step 4-5).
mkdocs.yml — repo_name includes version displayed in GitHub Pages header:
repo_name: s-hiraoku/synapse-a2a vNEW_VERSION
Important: Keep site-docs version in sync with pyproject.toml version.
Use git-cliff to automatically generate the changelog entry from Conventional Commits:
# Preview the generated changelog
python scripts/generate_changelog.py --unreleased --tag vNEW_VERSION --dry-run
# Write to CHANGELOG.md
python scripts/generate_changelog.py --unreleased --tag vNEW_VERSION
Review the generated entry and make manual adjustments if needed:
## [NEW_VERSION] - YYYY-MM-DDIf no git-cliff is available, or for a manual override, write the entry directly using Keep a Changelog format (see below).
Display:
/release patch
/release minor "Add new authentication system"
/release major
/release 1.0.0
/version patch # Same as /release patch
pyproject.toml (line with version = "...")plugins/synapse-a2a/.claude-plugin/plugin.json (line with "version": "...")site-docs/getting-started/installation.md, site-docs/concepts/a2a-protocol.mdmkdocs.yml (repo_name field)CHANGELOG.mdsite-docs/changelog.mdFollow Keep a Changelog format:
## [X.Y.Z] - YYYY-MM-DD
### Added
- New features
### Changed
- Changes in existing functionality
### Fixed
- Bug fixes
### Removed
- Removed features
### Documentation
- Documentation updates
### Tests
- Test updates
Only include sections that have entries. Order sections as shown above.
Synapse A2A agent communication -- sending messages, spawning agents, delegating tasks, sharing memory, managing the LLM wiki, and coordinating file edits. Use this skill when: running synapse send/reply/broadcast/interrupt, spawning agents with synapse spawn or synapse team start, sharing knowledge with synapse memory, managing wiki pages with synapse wiki, locking files with synapse file-safety, checking agent status with synapse list/status, or orchestrating any multi-agent workflow. For AI/programmatic use, prefer synapse list --json, synapse status <target> --json, or the MCP list_agents tool instead of interactive synapse list.
Multi-agent management workflow — task delegation, progress monitoring, quality verification with regression testing, feedback delivery, and cross-review orchestration. Use this skill when coordinating multiple agents on a shared task, monitoring delegated work, ensuring quality across agent outputs, or implementing a multi-phase plan (3+ phases or 10+ file changes).
Bootstrap a new GitHub issue implementation in one command: fetch the issue body, gather cross-references and code hotspots, infer a branch prefix and slug, generate a structured task brief, create a fresh branch from latest main, and (by default) spawn a codex agent to implement it. Triggered by /dev-issue <number>. Use this skill when starting work on a new issue that follows the standard issue → codex spawn → review → PR pipeline.
Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include "fetch source for", "read the source of", "how does X work internally", "get the implementation of", "opensrc path", or any task requiring access to dependency source code beyond types and docs.
Design, review, and improve Claude/Codex skills based on Anthropic's "The Complete Guide to Building Skills for Claude". Use when creating a new skill, rewriting SKILL.md frontmatter and workflows, fixing under-triggering or over-triggering, designing scripts/references/assets, building test cases, or preparing a skill for upload/distribution.
Guide API design for REST, GraphQL, gRPC, and CLI interfaces. Use this skill when designing new APIs, reviewing existing API contracts, or establishing API conventions for a project. Produces consistent, well-documented API specifications.