# Investigate Production

Find out what is actually happening in production from Sazabi's logs, traces and issues...

- Repository: https://github.com/ParadevAI/Paradev (15823 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add ParadevAI/Paradev --skill investigate-production -g -a claude-code -y`
Codex: `npx skills add ParadevAI/Paradev --skill investigate-production -g -a codex -y`
Cursor: `npx skills add ParadevAI/Paradev --skill investigate-production -g -a cursor -y`
Gemini CLI: `npx skills add ParadevAI/Paradev --skill investigate-production -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add ParadevAI/Paradev`

## Description

Find out what is actually happening in production from Sazabi's logs, traces and issues before touching code, ask the logs a precise question, read the lines behind the answer, and separate the symptom from its cause. Use when the user reports a production error, a slow or failing endpoint, a customer complaint, an alert, or asks what is broken, what changed, or why something stopped working.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Investigate with the logs, not the guess

Sazabi stores your logs, traces and metrics and answers questions about them.
The job is to turn "something is broken" into a claim about *what* fails, *why*,
and *who* it hits, backed by real log lines, before anyone edits code.

## 0. How the tools work

The Sazabi MCP server lists only two tools, `search` and `execute`. Browse
Sazabi's operations with `search` and `namespace: "sazabi"` (an empty query
without a namespace lists connected connectors, not Sazabi operations). Before
calling one, repeat `search` with `namespace: "sazabi"`, the hit's full name as
the query, and `includeInputSchema: true` to load its arguments. Then run it
with `execute` as `{ name, arguments }`, the name copied from the hit (for
example `sazabi/logs.ask`).

Most operations work on one project. If the user did not name one and more
than one exists, ask which, or pick the one whose name matches this repository.

## 1. Start from what is already known

Run `sazabi/issues.search` for the symptom. Sazabi opens issues on its own when
it sees new or growing errors, so the bug may already have a title, a severity,
and a first-seen time. Then run `sazabi/search.threads` for the same words: a
teammate or the Sazabi agent may already have investigated it.

Treat search hits as candidates. Match on the error and the code path, not on
title similarity.

## 2. Ask the logs one precise question at a time

`sazabi/logs.ask` takes a question in plain language and returns an `answer`,
an `explanation` of what it measured, the `window`, and a `queryId`.

The rest: https://github.com/ParadevAI/Paradev/blob/HEAD/plugins/sazabi/skills/investigate-production/SKILL.md