skills.rest
Brave-Labs
Brave-LabsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

Dev10x:investigate

Identify root causes from Slack bug threads and post technical replies with GitHub links.

Updated Aug 23, 2026
Search Tags:#automation#github#linear#slack#investigate#root-cause#bug
One-click install
npx skills add https://github.com/Brave-Labs/dev10x --skill dev10x-investigate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Dev10x:investigate
Source: https://github.com/Brave-Labs/dev10x/tree/main/skills/investigate
Command: npx skills add https://github.com/Brave-Labs/dev10x --skill dev10x-investigate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Root-cause a bug report, question, or unexpected behaviour from a Slack thread and post a technical reply with GitHub links and creates a Linear ticket when warranted.

Core Features & Use Cases

  • Reads Slack thread reports, maps symptoms to proximate code sources, and drafts a reply with contextual links.
  • Delegates PR reviews when a PR link is present, and can trigger a ticket creation workflow for non-trivial fixes.
  • Uses playbooks to orchestrate tasks and ensures tasks are created at startup for end-to-end traceability.

Quick Start

Investigate a Slack thread, identify the root cause in the codebase, and post a technical reply with GitHub links.

Frequently Asked Questions about Dev10x:investigate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the root cause of a bug reported in a Slack thread?▼

To find the root cause of a bug from a Slack thread, the Skill parses the thread URL, maps the reported symptoms to proximate code sources in your codebase, and drafts a technical reply with contextual GitHub links.

Can I automatically create a Linear ticket from a Slack bug report?▼

Yes, you can automatically create a Linear ticket from a Slack bug report. The Skill triggers a ticket creation workflow for non-trivial fixes after identifying the root cause and mapping the unexpected behavior to codebase locations.

How do I investigate a Slack thread that includes a GitHub PR link?▼

To investigate a Slack thread with a GitHub PR link, the Skill reads the thread, identifies the root cause, and delegates the PR review to ensure the fix addresses the unexpected behavior reported in the Slack conversation.

Does this tool work with my existing GitHub, Linear, and Slack automation workflow?▼

Yes, the tool works with GitHub, Linear, and Slack automation workflows. It parses Slack URLs, maps symptoms to GitHub codebase locations, delegates PR reviews, and creates Linear tickets through configured tools to ensure end-to-end traceability.

What is the best way to reply to a Slack bug report with relevant codebase links?▼

The best way to reply to a Slack bug report with codebase links is to use this Skill, which reads the thread, identifies the proximate code sources causing the unexpected behavior, and drafts a technical reply with contextual GitHub links.

When should I not use automated root-cause investigation for a Slack thread?▼

You should not use automated root-cause investigation when a Slack thread lacks a clear bug report or unexpected behavior to map. The Skill requires parsing a Slack URL and mapping described symptoms to proximate code sources to function correctly.

Related Skills

Explore More Software Engineering Skills→
Dev10x-GuruDev10x-Guru
7

Dev10x:investigate

Parse Slack thread URLs to investigate issues and draft replies.

Official
Advanced
HabibTorjmenHabibTorjmen

fix

Analyze Linear issues against the Blockchain codebase and create draft pull requests for confirmed fixes.

Community
Advanced
jonkikyjonkiky

investigate

Trace reported issue symptoms to code paths and verify root cause hypotheses.

Community
Advanced
unblockedunblocked
13

headless-validate-bug

Validate bug reports from Jira, Linear, and GitHub Issues.

Official
Advanced