write_bugfix_summary
Capture bug fixes by documenting root cause, solution, and lesson learned. Creates a time-stamped Markdown file, indexes it in the vector store, and pushes to git for future retrieval.
Instructions
Create a bugfix summary .md file, index it immediately, and auto-push to git.
MANDATORY after every bug fix — these summaries are retrieved during
future debugging sessions to avoid repeating the same mistakes.
Side effects: creates bugfix-log/YYYY-MM-DD-{slug}.md in the knowledge
repo docs path, indexes it into the vector store, and pushes to the
remote git repo if MCP_GIT_REPO_URL is configured. Overwrites an
existing file if the same title is used on the same day.
Use write_architecture_doc() for design decisions,
write_best_practice() for recurring patterns.
Args:
title: Short, descriptive title of the bug (used in filename)
root_cause: What was the actual cause? (be technical)
solution: How was it fixed? (describe code changes made)
lesson_learned: What should be done differently next time?
affected_files: Comma-separated list of changed files (optional)
tags: Comma-separated categories, e.g. "auth,race-condition,critical" (optional)
project: Target project name (optional)
Returns:
Saved filename, chunk count, and whether auto-push succeeded.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | ||
| root_cause | Yes | ||
| solution | Yes | ||
| lesson_learned | Yes | ||
| affected_files | No | ||
| tags | No | ||
| project | No |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |