skills.rest
mark22013333
mark22013333COMMUNITY
Explore all skills by this author →
WebsiteGitHub

bug-investigate

Automate hypothesis-driven root-cause investigation for software bugs with Notion.

9|1|Updated Mar 11, 2026
Search Tags:#automation#git#investigation#logs#notion#root-cause#bug
One-click install
npx skills add https://github.com/mark22013333/crew --skill bug-investigate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-investigate
Source: https://github.com/mark22013333/crew/tree/main/plugins/bug-workflow/skills/bug-investigate
Command: npx skills add https://github.com/mark22013333/crew --skill bug-investigate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates hypothesis-driven root-cause investigation for bugs, coordinating evidence collection, pattern matching, and hypothesis validation while synchronizing results to Notion.

Core Features & Use Cases

  • Automated evidence collection from logs, Git history, and knowledge bases.
  • Pattern matching against known bug templates to surface likely causes.
  • Hypothesis creation, testing, and iterative refinement with Notion-backed collaboration.

Quick Start

Describe a bug symptom or start an investigation with /bug-start to trigger the workflow.

Frequently Asked Questions about bug-investigate

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

FAQPage Schema
How do I automate root-cause investigation for software bugs using logs and Git history?▼

Root-cause investigation is automated by collecting evidence from logs and Git history, creating hypotheses, and validating them against known bug patterns. Results are synchronized to Notion to coordinate evidence collection and guide decision making.

What is hypothesis-driven bug investigation and how does it work with Notion?▼

Hypothesis-driven bug investigation creates and validates potential root causes against collected evidence. It integrates with Notion by reading settings, fetching context pages, and writing structured findings back to support team decision making.

Can I use Notion to coordinate bug investigation across logs and Git history?▼

Yes, you can coordinate bug investigation through Notion by fetching context pages and analyzing logs and Git history. The workflow writes structured findings back to Notion to support collaborative evidence collection and decision making.

How do I start an automated bug investigation workflow?▼

Start an automated bug investigation by describing a bug symptom or triggering the /bug-start command. This initiates the workflow to fetch Notion pages, analyze logs and Git history, and write structured findings back.

What's the best way to find the root cause of a bug from application logs?▼

The best way to find the root cause from application logs is to use an automated workflow that collects evidence, applies pattern matching against known bug templates, and iteratively refines hypotheses. Findings are written back to Notion.

Related Skills

Explore More Software Engineering Skills→
metric-space-aimetric-space-ai
2

notion-knowledge-capture

Extract decisions, actions, and owners from conversations into structured Notion pages.

Official
Advanced
slbugslbug
7

rb:investigate

Guide structured root-cause investigations for Ruby, Rails, and Grape bugs.

Community
Advanced
alangebalangeb

git-advanced

Perform Git bisecting, cherry-picking, and log analysis operations locally.

Community
Advanced
doitiandoitian
14

systematic-debugging

Enforce a four-phase root-cause debugging process for code and tests.

Community
Advanced