explaingit

buptwz/holmes-kb

Analysis updated 2026-05-18

32PythonAudience · developerComplexity · 3/5Setup · moderate

TLDR

A git-native knowledge base tool that automatically captures troubleshooting sessions and turns them into structured, searchable Markdown documentation for engineering teams.

Mindmap

mindmap
  root((repo))
    What it does
      Captures debugging sessions
      Builds searchable KB
      Tracks knowledge decay
    Tech stack
      Python
      Markdown
      Git
    Use cases
      Team troubleshooting
      Onboarding engineers
      Reducing repeat debugging
    Audience
      Engineering teams
      DevOps
      Support engineers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Automatically document the resolution of a production incident right after it's fixed.

USE CASE 2

Search past troubleshooting sessions before starting a new debugging effort.

USE CASE 3

Track which pieces of team knowledge are stale and need re-verification.

USE CASE 4

Import existing runbooks or wiki pages into a structured knowledge base.

What is it built with?

PythonMarkdownGitCLI

How does it compare?

buptwz/holmes-kbautolearnmem/automembilly-ellis/exr-imageio-poc
Stars323232
LanguagePythonPythonPython
Setup difficultymoderatehardmoderate
Complexity3/55/53/5
Audiencedeveloperresearcherresearcher

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Requires pairing with the separate holmes-agent repo and an LLM API key for full functionality.

License not stated in the README.

In plain English

Holmes is a knowledge base tool for engineering teams that tries to solve a common problem: when someone spends hours debugging an issue, that knowledge usually disappears into a Slack message or gets forgotten entirely. The next time someone hits the same problem, they start from scratch. Holmes aims to close that loop by automatically capturing what was learned during each debugging session and turning it into structured, searchable documentation. The system has two parts that work together. The first is this repository, a Python library and command-line tool that manages the knowledge base itself. Knowledge is stored as plain Markdown files with metadata headers inside a regular git repository, so there is no proprietary format or special database to maintain. The second part is a separate AI agent terminal interface (in a companion repository) that you interact with while debugging. When you describe a problem to the agent, it searches the knowledge base for relevant past incidents and presents them to you. When the problem is resolved, it automatically extracts the symptoms, root cause, and resolution steps and saves them as a new entry in draft form. Entries move through confidence levels over time. A draft entry becomes verified once it gets referenced in a real debugging session, and it becomes proven after being consulted multiple times. The system also automatically downgrades entries that have not been referenced recently, so the knowledge base reflects what is actually useful today rather than accumulating stale information indefinitely. A linter scans continuously for contradictions between entries, near-duplicate titles, and pending contributions that have not been confirmed. New entries go through a three-step validation check covering structure, deduplication, and a required human preview before anything is added to the official knowledge base. You can also import existing documentation from other sources using an AI-powered import command that reads any document and converts it into the standard entry format. The CLI handles setup, search, import, validation, and knowledge base maintenance without needing the agent component.

Copy-paste prompts

Prompt 1
Help me set up Holmes with a new git-based knowledge base for my team's incident notes.
Prompt 2
Show me how to configure Holmes to import our existing wiki pages into KB entries.
Prompt 3
Write a holmes-agent workflow that searches the KB before I start debugging a Redis timeout.
Prompt 4
Explain how Holmes decides when a KB entry moves from draft to verified to proven.

Frequently asked questions

What is holmes-kb?

A git-native knowledge base tool that automatically captures troubleshooting sessions and turns them into structured, searchable Markdown documentation for engineering teams.

What language is holmes-kb written in?

Mainly Python. The stack also includes Python, Markdown, Git.

What license does holmes-kb use?

License not stated in the README.

How hard is holmes-kb to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is holmes-kb for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.