---
name: amend-knowledge
description: Make small, well-titled changes to the team knowledge base with kb_amend. Use when asked to add, correct or update a page, or when you found an error and the person agreed to fix it. Every amendment is committed and published to the whole team.
---

# Amending the knowledge base

`kb_amend` writes one markdown page under `content/`, commits it with your message as the commit title and pushes it to the tracked branch. A pushed amendment is published: every agent and person using this knowledge base sees it on their next update. Write accordingly.

## Before you change anything

1. Be sure the change is wanted. Amend when you were asked to, or after the person agreed to a fix you proposed.
2. Search first with `kb_search`. Extend the page that already covers the topic instead of creating a near-duplicate.
3. Read the exact lines you will change with `kb_read`.

## Making the change

- Prefer `edit` with `find` and `replace`. `find` must match exactly once, so copy it from `kb_read` output and include enough surrounding text to be unique.
- Use `content` only for new pages or when asked to rewrite a page. Always send the complete page.
- One topic per amendment. Two unrelated fixes are two calls with two messages.
- Match the page's existing style: headings, list style, units and tone.
- New pages go in the folder that fits (`policies/`, `product/`, ...), use lowercase-hyphenated file names ending in `.md`, and start with a `# Title` heading.

## Writing the message

The message is the commit title people read in the history. Name the page area and the change, in under 72 characters:

- `Expenses: raise travel meal limit to 45 EUR`
- `Product FAQ: add EU data residency answer`

Not: `update`, `fix typo`, `changes from chat`.

## Never

- Never delete a page or empty it unless someone explicitly asked for that page to be removed. `kb_amend` refuses empty content; do not work around it.
- Never remove information you cannot verify is wrong. Add a correction or a note instead.
- Never put secrets, credentials or personal data in the knowledge base.

## After the change

Report the result `kb_amend` returns. If it says the change was not published (no remote, no tracked branch, push rejected or failed), tell the person the commit exists only on this checkout and why.