- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add coco-research/coco --skill change-log -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add coco-research/coco --skill change-log -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add coco-research/coco --skill change-log -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add coco-research/coco --skill change-log -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/coco-research/coco/tree/HEAD/skills/change-log게시자 제공
Maintains a chronological, append-only record of all meaningful changes to a product. Unlike CLAUDE.local.md (which is AI context), the change log is a stakeholder-facing document suitable for sharing with leadership, auditors, and team members.
/change-log init — Create new change log, backfill from CLAUDE.local.md/change-log update — Find changes since last entry, propose new entries/change-log release {version} — Create release summary from accumulated entries/change-log (no args) — Same as updateAlways read:
CLAUDE.local.md — Recent Changes section (primary source of truth for what changed)update or release mode)For init mode, also read:
Meeting-Notes/ directory listing — to identify decision-bearing meetingsPRD/ — version history sections.sync-watch.json — project nameFor update mode:
Meeting-Notes/ files dated after thatCLAUDE.local.md Recent Changes entries dated after thatFor each source, extract structured change data:
- Date: YYYY-MM-DD
- Summary: one-line description
- Type: Feature | Enhancement | Bug Fix | Configuration | Process | Security | Documentation
- Impact: High | Medium | Low
- Components: which modules/layers/documents were affected
- Author: who made or requested the change
- Approved By: who approved (if known from meeting notes)
- Details: bullet list of specific changes
- Rationale: why the change was made
- Downstream: what else was updated as a result
Impact classification:
Present proposed entries to user before writing:
## Proposed Change Log Entries
### [2026-03-17] PRD v0.9 — User Journey Sections
**Type:** Enhancement | **Impact:** High
**Components:** ProductB PRD, ProductB PRD Presentation
- Added Current User Journey (6-step timeline)
- Added Future User Journey (3-layer cascading)
- Renumbered all sections (19 total)
Accept? [Y/n] or modify?
File location: Data/Change-Log-{ProjectName}.md
File structure:
# Change Log — {Product Name}
> Running record of all changes. Newest entries first.
> Generated and maintained via `/change-log` skill.
Last updated: {date}
Total entries: {count}
---
## [YYYY-MM-DD] v{X.Y} — {Summary}
**Type:** {type} | **Impact:** {impact}
**Components:** {affected components}
**Author:** {name} | **Approved By:** {name or "—"}
### Changes
- {specific change 1}
- {specific change 2}
### Rationale
- {why this change was made}
### Downstream Effects
- {what else was updated}
---
## [YYYY-MM-DD] ...
For release mode:
Collect all entries since the last release entry (or all entries if first release). Produce a summary:
## Release: v{version} — {date}
### Summary
{2-3 sentence overview of what this release includes}
### Changes Included
| Date | Type | Summary | Impact |
|------|------|---------|--------|
| ... | ... | ... | ... |
### Highlights
- {Most important change}
- {Second most important}
### Known Issues
- {Any caveats}
Create or update a structured change log for a product or platform. Use when someone asks to "create a change log", "log this change", "what changed", "update the change log", "release notes", or "cha
---name: pmstudio-changelogdescription: Create or update a structured change log for a product or platform. Use when someone asks to "create a change…---# skills/change-log/SKILL.md개요
Create or update a structured change log for a product or platform. Use when someone asks to "create a change log", "log this change", "what changed", "update the change log", "release notes", or "changelog". Reads project memory (CLAUDE.local.md Recent Changes) and meeting notes to build chronological change records. Supports init (backfill from memory), update (append new entries), and release (summarize for a version).
FAQ
게시자에게서 skills/change-log/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/coco-research/coco에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.