whatisgithub

What is nitpick?

flylikeapenguin/nitpick — explained in plain English

Analysis updated 2026-05-18

21PythonAudience · ops devopsLicenseSetup · moderate

In one sentence

A local tool that turns recurring Datadog production errors into deduplicated Claude written root cause analyses, GitHub or Linear issues, and reviewable fix pull requests.

Mindmap

mindmap
  root((repo))
    Pipeline
      Datadog error logs
      Fingerprint and dedup
      Claude root cause analysis
    Outputs
      RCA documents
      GitHub or Linear issues
      Reviewable fix PRs
    Safety model
      Read only investigation
      Auto-fix off by default
      250 line diff ceiling
    Audience
      Engineering teams
      Incident response

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 deduplicate thousands of raw error log entries into a manageable set of distinct recurring problems.

USE CASE 2

Generate a written root cause analysis and file a tracked issue for each new production error.

USE CASE 3

Open a reviewable pull request for small, safe fixes instead of letting an AI change production code directly.

What is it built with?

PythonDatadogClaude CLIGitHubSQLite

How does it compare?

flylikeapenguin/nitpick0whitedev/detranspiler2951461586/mulerun-pool
Stars212121
LanguagePythonPythonPython
Setup difficultymoderatehardmoderate
Complexity4/53/5
Audienceops devopsdeveloperdeveloper

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

How do you get it running?

Difficulty · moderate Time to first run · 1h+

Needs Python 3.12+, Claude CLI, gh CLI, and Datadog API and App keys for at least one site.

So what is it?

Nitpick is an open source tool that automates the early, repetitive parts of handling production errors. It watches error logs coming from Datadog, groups together errors that are really the same underlying problem happening again and again, and then hands each new distinct error to Claude, Anthropic's AI coding assistant, to investigate. For each new error, Claude reads the relevant parts of your codebase, works out a likely root cause, and Nitpick turns that into a written root cause analysis document plus a filed issue in GitHub or Linear. If a fix looks safe and small enough, typically under 250 lines of code, Nitpick can also create an isolated copy of the repository, apply the fix there, and open it as a pull request for a human to review. It never pushes a fix directly to a live checkout, and automatic fixes are switched off by default until someone deliberately turns that setting on for a given part of the codebase. According to the README, a real deployment has been running this continuously for about two months at a voice AI company, processing over 40,000 raw log entries down to a few hundred distinct recurring problems, filing over a thousand issues automatically, and opening 21 fix pull requests, six of which were merged. Nitpick runs locally rather than as a hosted service, so error data and source code stay under your control, and only the specific records needed to file an issue or write a document are sent to outside providers. Right now it supports Datadog as its error source, with GitHub or Linear for issue tracking and Markdown or Notion for documentation, and the project describes more sources and integrations as planned future work. This is aimed at engineering teams who want repeated production errors turned into reviewable, actionable work instead of getting lost in noisy alert channels, without giving an AI system the ability to change production code unsupervised.

Copy-paste prompts

Prompt 1
Help me configure Nitpick's config.yml to connect my Datadog source to a GitHub issue tracker.
Prompt 2
Explain how Nitpick's fingerprinting and deduplication step works before an error reaches Claude.
Prompt 3
Walk me through enabling auto-fix pull requests safely for one service in Nitpick's dashboard.

Frequently asked questions

What is nitpick?

A local tool that turns recurring Datadog production errors into deduplicated Claude written root cause analyses, GitHub or Linear issues, and reviewable fix pull requests.

What language is nitpick written in?

Mainly Python. The stack also includes Python, Datadog, Claude CLI.

How hard is nitpick to set up?

Setup difficulty is rated moderate, with roughly 1h+ to a first successful run.

Who is nitpick for?

Mainly ops devops.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.