ワンクリックで
util-changelog
Append a changelog entry to a note. Called by write skills after modifying files.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Append a changelog entry to a note. Called by write skills after modifying files.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Ada, your Executive Assistant. Runs planning and reflection rituals by coordinating domain assistants.
Calendar assistant. Meeting prep, day shape analysis, and post-meeting reflection.
Projects assistant. Tracks project status, blockers, and next actions.
Relationships assistant. Tracks people touchpoints, connection intentions, and relationship health.
Obsidian CLI for vault search, backlinks, links, tags, and file operations. Use when fetching related content or interacting with Obsidian programmatically. Requires Obsidian v1.12+ with CLI enabled.
Achievements assistant. Captures wins, accomplishments, and evidence of impact.
| name | _util-changelog |
| description | Append a changelog entry to a note. Called by write skills after modifying files. |
| disable-model-invocation | true |
| allowed-tools | Read, Write |
Appends a timestamped changelog entry to a note file. Entries are reverse-chronological (newest first).
Arguments are passed as key-value pairs:
path: Full path to the note fileskill: Name of the skill making the change (e.g., "planning-daily")action: Verb summarizing the action (e.g., "Rewrote", "Added", "Updated")sections: Comma-separated list of section names affected (optional)summary: Additional context (optional)Generate the current timestamp in format YYYY-MM-DD HH:mm (24-hour).
Build the changelog entry in this format: - {timestamp} **{skill}** — {action}{sections_text}{summary_text}, where sections_text includes section names if provided, and summary_text includes additional context if provided.
Read the existing content of the file. If the file doesn't exist, return an error indicating the file must exist before appending changelog entries.
Locate the ## Changelog heading (case-insensitive). If the section exists, insert the entry at the top of the list after the heading, skipping any italicized placeholder text. If the section doesn't exist, append a new Changelog section at the end of the file.
Write the modified content back to the file.
Return structured output in a markdown code block:
Success:
{
"success": true,
"path": "/path/to/note.md",
"entry": "- `2026-02-15 09:32` **planning-daily** — Rewrote Focus section",
"created_section": false
}
Error:
{
"success": false,
"error": "write_failed",
"message": "Failed to write changelog entry"
}