changelog
Render release notes / a changelog from the cladding spec.
Skill by purpleeddy
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/purpleeddy-changelog
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: security, writing, productivity
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/changelog
What's inside
- Skill name
changelog- Description
- Render release notes / a changelog from the cladding spec. Use when the user asks for release notes, a changelog, 릴리즈 노트, 변경 이력, or "what changed (since <ref>)" — run `clad changelog --json` for the deterministic shipped-changes manifest, then write the human-facing notes FROM it, sourcing every claim from a feature title or acceptance sentence. For audit asks, print the --audit table verbatim. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized projects.
- License
- MIT
- Instructions
- 36 lines in SKILL.md · view on GitHub
Agent Skills spec issues
- name: missing
Files (1)
- SKILL.md
SKILL.md (first lines)
# Cladding changelog — release notes from the spec
The spec is the SSoT, so "what shipped?" is *collected*, never recalled. `clad changelog` turns
`<since>..HEAD` into a deterministic manifest: feature shards classified (`added-as-done` /
`flipped-to-done` / `modified-while-done` / `archived`), grouped by capability (plus an
`uncategorized` bucket — itself a drift signal), the spec inventory diff, and conventional
`feat:`/`fix:` commits that name no feature id (work that shipped *outside* the spec — report it
honestly, don't hide it).
## Protocol
1. **Collect.** Run `clad changelog --json --since <ref>` (omit `--since` to use the latest tag;
if the repo has no tags the command says so — ask the user for a ref).
2. **Render EN + KO release notes from the manifest, in the CHANGELOG.md house style:**
- Open with a `**In one line:**` abstract (what a user gains, one breath).
- Group by the manifest's capability groups; use **user-impact verbs** ("the gate now runs
your entry point"), not implementation verbs ("refactored stage runner").
- **No `F-…`/`AC-…` ids in prose** (Soft Shell policy) — ids belong to the audit surface only.
- **Source every claim from the manifest** — a feature `title` or an `acceptance[]` sentence.
Never invent a change, never embellish beyond what an AC states. If the manifest is empty,
say "no shipped changes since <ref>" — that line is the honest deliverable.
- Put `unsharded_commits` under an "Also changed" section, marked as not yet spec-tracked.
3. **Audit asks** ("show verification", "어디까지 검증됐어?") → print
`clad changelog --audit --since <ref>` **verbatim** — that table keeps ids and marks every
verification ref resolved ✓ / unresolved ✗ (a ✗ is spec-annotation drift worth reporting).
4. **Catalog asks** ("what does this project do, in full?") → `clad changelog --catalog` prints
the whole capability → feature → acceptance listing of the living spec.
```
clad changelog # markdown since the latest tag (deterministic fallback)
clad changelog --json --since v0.5.2 # the manifest you render notes from
clad changelog --audit --since v0.5.2
clad changelog --catalog
```From purpleeddy/cladding, MIT.
More from purpleeddy/cladding
- 0.600score
orchestrator
purpleeddy
Cycle-contract coordinator for a cladding-managed project — declares the outcome conditions each feature must satisfy (spec-first, independent verification…
SkillBFreshness: B★ 16Claude Code +9 - 0.600score
blind-author
purpleeddy
Impl-blind test/oracle author — writes conformance tests from a spec-only brief.
SkillBFreshness: B★ 16Claude Code +9 - 0.600score
reviewer
purpleeddy
Philosophical guardrails enforcer — independently audits code, tests, and spec for layered-integrity, Why>What, error-as-data, and the related Ironclad…
SkillBFreshness: B★ 16Claude Code +9 - 0.597score
observability
purpleeddy
Log and metrics analyst — reads .cladding/audit.log.jsonl, perf/baseline.json, and drift reports; surfaces patterns the human can act on.
SkillBFreshness: B★ 16Claude Code +9 - 0.597score
planner
purpleeddy
SSoT custodian — keeps spec.yaml structurally clean.
SkillBFreshness: B★ 16Claude Code +9 - 0.597score
developer
purpleeddy
Implementer — writes production code, tests, and migrations.
SkillBFreshness: B★ 16Claude Code +9 - 0.596score
sync
purpleeddy
Validate the active spec.yaml against the Ironclad schema and refresh the inventory.
SkillBFreshness: B★ 16Claude Code +9 - 0.596score
route
purpleeddy
Classify a natural-language prompt to one of cladding's verbs.
SkillBFreshness: B★ 16Claude Code +9 - 0.596score
oracle
purpleeddy
Author an IMPL-BLIND spec-conformance oracle for an acceptance criterion the policy worklist (`clad oracle --required`) demands — an empty worklist means…
SkillBFreshness: B★ 16Claude Code +9 - 0.596score
rollback
purpleeddy
Record a rollback event and print the maintainer-runnable git command for the most recent checkpoint of a feature.
SkillBFreshness: B★ 16Claude Code +9 - 0.596score
checkpoint
purpleeddy
Record a feature checkpoint event pinning the current git HEAD plus a spec digest, so a later rollback can restore the exact pre-change state.
SkillBFreshness: B★ 16Claude Code +9 - 0.596score
doctor
purpleeddy
Diagnose Cladding runtime health — Claude Code hook liveness and version, CI package pinning, lifecycle governance, and sentinel-miss frequency by phase ×…
SkillBFreshness: B★ 16Claude Code +9
Signals
- Stars
- 16
- Forks
- 4
- Open issues
- 0
- Last commit (this folder)
- Jul 14, 2026 (3 months ago)
- Last release
- Sep 11, 2026 (1 month ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/purpleeddy/cladding
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
Same skill elsewhere
Copies of this SKILL.md published by others; search shows only one of them.
More from purpleeddy
- 0.600score
orchestrator
purpleeddy
Cycle-contract coordinator for a cladding-managed project — declares the outcome conditions each feature must satisfy (spec-first, independent verification…
SkillBFreshness: B★ 16Claude Code +9 - 0.600score
reviewer
purpleeddy
Philosophical guardrails enforcer — independently audits code, tests, and spec for layered-integrity, Why>What, error-as-data, and the related Ironclad…
SkillBFreshness: B★ 16Claude Code +9 - 0.600score
blind-author
purpleeddy
Impl-blind test/oracle author — writes conformance tests from a spec-only brief.
SkillBFreshness: B★ 16Claude Code +9 - 0.597score
planner
purpleeddy
SSoT custodian — keeps spec.yaml structurally clean.
SkillBFreshness: B★ 16Claude Code +9 - 0.597score
developer
purpleeddy
Implementer — writes production code, tests, and migrations.
SkillBFreshness: B★ 16Claude Code +9 - 0.597score
observability
purpleeddy
Log and metrics analyst — reads .cladding/audit.log.jsonl, perf/baseline.json, and drift reports; surfaces patterns the human can act on.
SkillBFreshness: B★ 16Claude Code +9
Cite this page
changelog skill. Agent Mart. https://agentmart.dev/skills/purpleeddy-changelog (last updated 2026-10-24)