# Create Issue From Telebugs

> Use when creating an issue in your project tracker from a Telebugs error — fetches error data and creates a structured bug ticket.

- Skill: `zhuravel/create-issue-from-telebugs` (Agent Skill)
- Install (CLI): `npx skillmds@latest add zhuravel/create-issue-from-telebugs`
- Raw SKILL.md: https://api.skillmd.com/api/skills/zhuravel/create-issue-from-telebugs/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: zhuravel (https://skillmd.com/u/zhuravel)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/zhuravel/create-issue-from-telebugs

---


# Create Issue from Telebugs Error

Fetch error data from Telebugs and create a structured issue in your project tracker.

**REQUIRED:** Use the `telebugs` skill for tool loading, data fetching, and response parsing.

## Steps

### 1. Fetch Error Data

Follow the `telebugs` skill to:

1. Load deferred MCP tools
2. Extract `group_id` from the URL
3. Fetch error group and latest report in parallel
4. Extract error details and stack traces using the Python extraction commands

### 2. Summarize the Error

From the extracted data, identify:

- **Error type and message** (from error details extraction)
- **Culprit** — the job or controller that triggered the error (from error group `culprit` field)
- **In-app stack frames** — file paths and line numbers marked with `in_app: 1`
- **Occurrence count** and time range (`first_seen` / `last_seen` from error group)
- **Team notes** — any prior investigation context from the error group notes
- **Dashboard link** — `https://<your-telebugs-host>/errors/{group_id}`

### 3. Create the Issue

Create an issue in your project tracker with:

- **Title**: `"[ErrorType] short description"` (e.g., `"[TimeoutError] DNS timeout in background import job"`)
- **Labels**: `["Bug"]`
- **Priority**: based on occurrence count and severity:
  - Urgent: actively breaking core functionality
  - High: high occurrence count (1000+), user-facing impact
  - Normal: moderate occurrence count, background job failures
  - Low: rare, non-critical, handled errors
- **Description**: use the bug template below

### Bug Description Template

```markdown
## Bug Description

{error_type}: {short error message}

**Occurrences:** {count} since {first_seen}
**Last seen:** {last_seen}
**Culprit:** {culprit}
**Telebugs:** https://<your-telebugs-host>/errors/{group_id}

## Stack Trace (in-app frames)

- `{file}:{line}` in `{function}`
- `{file}:{line}` in `{function}`

## Error Message

{full error message, truncated to ~500 chars}

## Notes

{any team notes from the error group}

## Context

{breadcrumb summary or additional context if relevant}
```

### 4. Display Result

After creating the issue, display:

- Issue URL from your project tracker
- Telebugs link: `https://<your-telebugs-host>/errors/{group_id}`