Install
$ agentstack add skill-cormff-claude-code-playbook-changelog ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Vault Changelog
Keeps "what changed in the vault and why" traceable over time — useful once a vault has enough activity that reconstructing history from memory stops being reliable.
When this runs
After a note is created, edited, or deleted, ask the user once: "log this?" Don't log automatically without asking — not every vault write is worth a changelog entry, and asking keeps the log meaningful instead of noisy.
Format
Append to the current day's changelog entry (create it if it doesn't exist yet):
## YYYY-MM-DD
- **[HH:MM]** — — [[Note_That_Changed]]
Keep it short
One line per change is enough. This is a traceability log, not a narrative — if more detail matters, that detail belongs in the note itself or in [decision-log](../../layer-1-universal/decision-log/SKILL.md), not here.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: cormff
- Source: cormff/claude-code-playbook
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.