AGENT SKILL

changelog

暂无简介

License 许可
MIT
最近更新
2026-06-13
Stars
★ 3
Forks
1

02 资源文件 2

03 SKILL.md 正文

Changelog — auto-generate from RFC metadata

Purpose

Every RFC that reaches status: done should produce a corresponding CHANGELOG.md entry. This skill ensures the changelog stays synchronized with shipped work without manual authoring.

When to invoke

Trigger on:

  • "Write a changelog entry for RFC XXXX"
  • "Update the to CHANGELOG.md" after an RFC implementation
  • "Cut a release" / "what changed since last release?"
  • An RFC's status transitions to done

Trigger on user messages like:

  • "changelog" / "write changelog" / "update CHANGELOG.md"
  • "ship RFC 0034" / "release v0.4.0"
  • "what's new since v0.3.0?"

Do not invoke for:

  • Editing the changelog format or structure → edit CHANGELOG.md directly
  • Adding a new RFC → that's part of the RFC-writing workflow, not changelog

Workflow: RFC done → changelog entry

1. Read the RFC frontmatter

Extract from docs/rfcs/NNNN-*.md:

rfc: 0034
title: Ban depends_on; auto-chain tasks alphabetically within levels
status: done
type: refactor          # feat | fix | refactor | chore | breaking
source: human
priority_tier: tier1
backwards_compatible: no
risk: high
breaks_existing: yes

2. Map RFC type to CHANGELOG section

RFC type CHANGELOG section
feat ### Added
fix ### Fixed
refactor ### Changed
chore ### Changed
breaking (or breaks_existing: yes) ### Breaking (always top)

3. Find related commits

git log --oneline --grep="RFC 0034" --grep="0034" --grep="depends_on" --all

Use commits to identify the key changes, but write the changelog entry from the RFC description, not the commit messages.

4. Write the changelog entry

Format:

- **RFC 0034**: Ban `depends_on` from TASK.md frontmatter. Tasks at the same directory level are now auto-chained alphabetically by ID. Migration: `converge migrate --rfc=0034`.

Rules:

  • One bullet per RFC, under the appropriate section
  • Lead with the RFC number and title
  • Describe what changed for the user, not internal implementation details
  • Include migration instructions if breaks_existing: yes
  • Keep to 1-2 sentences max
  • Use backticks for code/field names
  • End with a period

5. Place under [Unreleased]

Insert the entry under the correct section within [Unreleased]. If the section doesn't exist, create it. Sections order:

## [Unreleased]

### Breaking
### Added
### Changed
### Fixed
### Deprecated
### Removed
### Security

6. Update the RFC Progress table

Add a row to the RFC's Progress table:

| Changelog entry | **done** | Added to CHANGELOG.md under [Unreleased] → Changed |

CHANGELOG.md format

The file follows Keep a Changelog:

# Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]

### Breaking

### Added

### Changed

### Fixed

## [0.3.0] - 2026-05-15

### Added
- Initial monorepo structure
...

Release cut workflow

When the user says "cut a release" or "release vX.Y.Z":

  1. Gather done RFCs since last release:

    git log --oneline --since="2026-05-01" -- docs/rfcs/
    

    Check which RFCs have status: done in their frontmatter.

  2. Verify all done RFCs have changelog entries — any missing, run the workflow above.

  3. Replace [Unreleased] with versioned header:

    ## [0.4.0] - 2026-05-22
    
  4. Add new [Unreleased] section above the versioned section.

  5. Commit:

    chore(release): v0.4.0
    
    Changes since v0.3.0:
    - RFC 0034: ...
    - RFC 0033: ...
    

File map

.claude/skills/changelog/
  SKILL.md                    (this file — entry point and workflow)
  reference/
    format.md                 (Keep a Changelog format reference)
  templates/
    release-notes.md          (template for cutting releases)
CHANGELOG.md                  (root — single source of truth)
docs/rfcs/NNNN-*.md           (RFC metadata source)

Key rules

  1. Never invent changelog entries — every entry must map to a done RFC or a verified commit
  2. User-facing language — describe what changed for users, not internal refactors
  3. One entry per RFC — even if an RFC touches multiple files, it's one bullet
  4. Breaking changes go first — under ### Breaking at the top of each version section
  5. Include migration info — if breaks_existing: yes, note how to migrate
  6. Link to RFC — reference the RFC number in the entry
  7. Don't duplicate — check if an entry already exists before adding

04 同仓库更多 Skills

openplaybooks-dev
openplaybooks-dev/converge

hello-checker

Use this skill when asked to "verify", "check", or "validate" a file's existence and content. It provides a reliable workflow for confirming files meet their spec.

Skill与智能体开发
★ 3
openplaybooks-dev
openplaybooks-dev/converge

ask-skill

暂无简介

Skill与智能体开发
★ 3
openplaybooks-dev
openplaybooks-dev/converge

html-review-artifact

Framework-wide guidance for crafting polished human-review artifacts as markdown or HTML

前端开发Skill与智能体开发
★ 3
openplaybooks-dev
openplaybooks-dev/converge

converge-planning

Design a Converge playbook end-to-end. Use when the user says "plan a project", "design a playbook", "decompose into tasks", "scaffold a Converge workflow", "onboard to Converge", or asks how to write TASK.md / playbook.yml. Two entry points: plan a new playbook or update an existing one. Hand off to `/converge-control` after producing the playbook structure.

Skill与智能体开发
★ 3
openplaybooks-dev
openplaybooks-dev/converge

converge-control

Operate a Converge playbook end-to-end — start runs, monitor progress, narrow failures with `--select`, inspect runtime state, validate definitions, surgically reset subtrees, and stop stuck or orphaned runs. Use this skill whenever the user says "run my playbook", "execute this", "monitor the run", "converge failed", "the run is stuck", "retry failures", "babysit this playbook", "what's the status?", "show me the gantt", or asks how to use `converge run` / `--select` / `inspect` / `doctor` / `clean` / `stop`. Also use it for `HTTP 401` / `Invalid API key` failures on the first task — those are environment-not-playbook problems — and for any post-run cleanup work. Hand off to `converge-planning` if the user wants to design or restructure the playbook itself.

开发工程师Skill与智能体开发
★ 3
openplaybooks-dev
openplaybooks-dev/converge

repair-taskts

Fix task.ts definition issues — Seed syntax, missing .build(), empty checks, import errors, TypeScript errors

开发工程师
★ 3