agentsclimarketplace

Add changelog command

Skill datamaker-kr/synapse-claude-marketplace/plugins/platform-dev-team-common/skills/add-changelog-command

시냅스 제품군 개발을 위한 공용 Claude Marketplace 입니다. 용도 및 목적 별 plugins 를 통해 claude plugins, agents, skills, commands 를 제공합니다.

Install
npx -y skills add datamaker-kr/synapse-claude-marketplace --skill add-changelog-command

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Run the `platform-dev-team-common:add-changelog` workflow from the original Claude slash command. Use when the user asks to add a changelog entry to CHANGELOG.md in the Unreleased section following Keep a Changelog format with CalVer versioning.

SKILL.md

3.0 KB, as published. Nobody here has run it

<!-- Generated by tools/generate-agent-marketplaces.py; edit the source command or agent-plugin.yaml instead. -->

platform-dev-team-common:add-changelog Command Workflow

Codex Adaptation

  • Treat the user request or explicitly supplied text as the command arguments.
  • Use the available Codex file, search, terminal, and clarification capabilities that match the workflow.
  • Do not depend on Claude-only slash command variables or tool names.

Add Changelog Command

You will help the user add a changelog entry to the CHANGELOG.md file in the Unreleased section.

Versioning Strategy

This project follows the guidelines from Keep a Changelog.

This plugin uses Calendar Versioning with the format YYYY.Minor.Patch.

  • Example: 2026.1.0, 2026.1.1, 2026.2.0

Available Options

  • --type <category>: Changelog category (added/changed/fixed, default: added)
  • --lang <language>: Description language (korean/english, default: korean)
  • --ticket <id>: Ticket ID (optional, will try to extract from branch name if not provided)

Examples

  • /add-changelog --type added --lang ko: Add entry to "Added" section in Korean
  • /add-changelog --type fixed --lang eng: Add entry to "Fixed" section in English
  • /add-changelog --ticket SYN-1234 --type changed: Add entry with specific ticket ID
  • /add-changelog: Add entry to "Added" section in Korean (default)

Implementation

  1. Extract ticket ID from branch name or use provided ticket
  2. Analyze current changes and commits to understand the scope
  3. Generate appropriate changelog description in specified language
  4. Add entry to the correct section in CHANGELOG.md under [Unreleased]
  5. Follow existing changelog format and conventions

Changelog Categories

Based on Keep a Changelog:

  • Added: New features, endpoints, functionality
  • Changed: Changes in existing functionality, improvements, updates
  • Fixed: Bug fixes, error corrections, issue resolutions
  • Deprecated: Soon-to-be removed features (if applicable)
  • Removed: Removed features (if applicable)
  • Security: Security fixes (if applicable)

Format Guidelines

  • Follow existing format: - [TICKET-ID](JIRA-URL) Description
  • Keep descriptions concise but informative
  • Use appropriate language (Korean/English)
  • Maintain chronological order (newest first in each section)
  • Ensure proper JIRA ticket linking
  • Follow Keep a Changelog principles

Unreleased Section Format

## [Unreleased] - yyyy-mm-dd

### Added

### Changed

### Fixed

Please provide the changelog type and language, or use defaults for "added" and Korean.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.