memoryproductivity / update change log

Update Change Log

update_change_log

Appends a human-readable entry to the project changelog in agent memory. Use when: completing a feature, fixing a bug, or making a notable architectural change worth recording for collaborators or future agents. Scope: local filesystem (CHANGELOG.md in memory dir). No network access. Not for: session event logging (use memory_log), milestone tracking (use update_milestones).

How to use update_change_log

Provide only the required inputs below. Start with the smallest scope that answers the task, then review the risk properties before an agent executes the call.

Risk and execution properties

Read only: no

Destructive: no

Idempotent: no

Open world: no — operates locally or through configured services

Inputs

descriptionstringrequired

What changed. Be concise but specific.

change_typestringrequired

Type of change: feat (new feature), fix (bug fix), refactor, docs, test, chore, breaking (breaking change).

Allowed: "feat""fix""refactor""docs""test""chore""breaking"

versionstring

Optional version tag. Example: 'v1.2.0'. Groups entries under a version header.

scopestring

Optional scope — what area of the project. Example: 'webapp', 'memory', 'github-tools'.

Example input

{
  "description": "<string>",
  "change_type": "feat",
  "version": "<string>",
  "scope": "<string>"
}

Browse or search the full 74-tool reference to choose the smallest suitable capability.

Browse all tools →