maintain-changelog
- Repo stars 0
- Author updated Live
- Author repo plugins
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @0-xcf · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: maintain-changelog
description: | they're done, append an entry to CHANGELOG.md in the repo root. Also activate when: the diff t…
category: other
runtime: no special runtime
---
# maintain-changelog output preview
## PART A: Task fit
- Use case: | they're done, append an entry to CHANGELOG.md in the repo root. Also activate when: the diff tells that story. The changelog tells the human story. entry even if it touched 3 files. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “When to Activate / Changelog Location / Entry Format” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “| they're done, append an entry to CHANGELOG.md in the repo root. Also activate when: the diff tells that story. The changelog tells the human story. entry even if it touched 3 files. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “When to Activate / Changelog Location / Entry Format” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “When to Activate / Changelog Location / Entry Format”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: maintain-changelog
description: | they're done, append an entry to CHANGELOG.md in the repo root. Also activate when: the diff t…
category: other
source: 0-xcf/plugins
---
# maintain-changelog
## When to use
- | they're done, append an entry to CHANGELOG.md in the repo root. Also activate when: the diff tells that story. The c…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “When to Activate / Changelog Location / Entry Format” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "maintain-changelog" {
input -> user goal + target files + boundaries + acceptance criteria
context -> When to Activate / Changelog Location / Entry Format
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Maintain Changelog
When to Activate
End of every session that modified files. Before wrapping up or when the user signals
they're done, append an entry to CHANGELOG.md in the repo root.
Also activate when:
- The user explicitly asks to update the changelog
- Starting a new session — read the changelog first to understand recent history
Changelog Location
CHANGELOG.md in the repository root. Create it if it doesn't exist.
Entry Format
## YYYY-MM-DD — <brief title>
### What changed
- Bullet points describing each meaningful change
- Group related changes together
- Include file paths for significant additions/modifications
### Why
- One or two sentences explaining the motivation or context
### Files touched
- `path/to/new-file.yaml` (new)
- `path/to/modified-file.yaml` (modified)
- `path/to/deleted-file.yaml` (deleted)Rules
- Be concise. Each entry should be scannable in 10 seconds. No paragraphs.
- Focus on "what" and "why", not "how". Don't describe implementation details — the diff tells that story. The changelog tells the human story.
- Group by logical change, not by file. "Added shared Postgres instance" is one entry even if it touched 3 files.
- Newest entries at the top. Reverse chronological order.
- Don't log trivial changes. Typo fixes, formatting, or changelog-only updates don't need entries.
- Include context that won't be obvious later. Item IDs, IP addresses, design decisions — things that help future sessions understand the state of the world.
- Don't duplicate commit messages. The changelog is higher-level than git log. One changelog entry may span multiple commits.
Example
# Changelog
## 2026-02-09 — Add shared PostgreSQL instance
### What changed
- Created CNPG Cluster `home-1` in `postgres` namespace (single instance, 10Gi on zfs-nfs)
- Added managed roles for `kutt` and `linkding` with ESO-managed passwords (auto-rotation via CNPG)
- Created 4 Vaultwarden login items for postgres credentials (superuser, app, kutt, linkding)
- Added ArgoCD Application for postgres
### Why
Shared Postgres instance for apps migrating off SQLite. Per-app user isolation with
automated password rotation through the ESO → CNPG pipeline.
### Files touched
- `apps/postgres/postgres.yaml` (new)
- `apps/external-secrets/externalsecrets.yaml` (modified — 4 new ExternalSecrets)
- `apps/argocd/apps.yaml` (modified — postgres Application added)
### Next steps
- Create `kutt_db` and `linkding_db` databases manually after cluster is healthy
- Rotate change-me passwords in Vaultwarden
- Migrate Kutt from SQLite to PostgresStarting a New Session
When beginning work, read CHANGELOG.md to understand:
- What was done recently
- What "next steps" were left by the previous session
- The current state of the project
This provides continuity across sessions without relying on memory files alone.
Notes
- The changelog complements (not replaces) git history. Git shows what code changed; the changelog shows what decisions were made and why.
- If the repo doesn't have a CHANGELOG.md yet, create one with a header:
# Changelog - Don't commit the changelog separately — include it in the same commit as the changes it documents.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review