New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Investigate Bug

by BuilderIO in BuilderIO/agent-native

Given a bug report (GitHub issue, Jira ticket, file, or pasted text), find its root cause and decide per symptom whether it is a one-off or one instance of a pattern worth fixing at the root, then…

No licenceAuto-check passedTesting & QA

Install Investigate Bug

skills CLI
$ npx skills add BuilderIO/agent-native --skill investigate-bug -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install BuilderIO/agent-native investigate-bug --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/BuilderIO/agent-native.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/investigate-bug .claude/skills/investigate-bug && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
investigate-bug
GitHub stars
7.1k
Token cost
~1k tokens
SKILL.md length
484 words
Files
4 (incl. scripts, references)
Skills in repo
108
Repo updated
First seen
Licence
None found

At a glance

Given a bug report (GitHub issue, Jira ticket, file, or pasted text), find its root cause and decide per symptom whether it is a one-off or one instance of a pattern worth fixing at the root, then…

  • Works in 11 steps: Preflight: $H/doctor.ts and… → Intake: $B/bug-intake.ts --issue |… → Split symptoms, and give each a short… → …
  • Tasks that involve QA and bug reports
  • SKILL.md covers Steps and Report
  • Runs TypeScript scripts from its folder

What it does

Investigate Bug is an agent skill from BuilderIO/agent-native. Given a bug report (GitHub issue, Jira ticket, file, or pasted text), find its root cause and decide per symptom whether it is a one-off or one instance of a pattern worth fixing at the root, then file or sight a deduplicated refactor ticket when it is. Use proactively whenever handed a bug report and asked what is wrong or whether something deeper is broken.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/bug-verdicts.md`, `scripts/bug-verdict.ts` and `scripts/summarize.ts`).

It sits in Testing & QA, covering QA and bug reports, Root cause analysis and Refactoring. It works with Jira and GitHub. The repository describes itself as: A framework for building agentic apps.

When your agent uses it

  • Tasks that involve QA and bug reports
  • Tasks that involve Root cause analysis
  • Tasks that involve Refactoring

Example prompts

  • “/investigate-bug”

Requirements

  • Node.js

Workflow steps

11 steps, taken from the first numbered list in SKILL.md.

  1. Preflight: $H/doctor.ts and $J/doctor.ts. Stop on any nonzero exit.
  2. Intake: $B/bug-intake.ts --issue | --jira | --file | --text "".
  3. Split symptoms, and give each a short label.
  4. Trace: for each symptom, follow steps 1 and 2 of
  5. History: $H/collect.ts --run $RUN --lookback-days 60 --no-prs, then
  6. Dedup early: $J/jira-match.ts --run $RUN. If an existing ticket's
  7. Investigate each remaining symptom with steps 3 to 6 of the brief
  8. Decide each symptom using references/bug-verdicts.md. A
  9. Plan if pattern: $P/new-plan.ts --run $RUN .... The scaffold adds a
  10. Record a verdict for each symptom
  11. Summarize: $S/summarize.ts --run $RUN. Exit 1 means no verdict yet.

What it can do on your machine

Read from SKILL.md and the folder at commit 1c2de07. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (TypeScript), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Investigate Bug loads about 1k tokens when it runs, and up to ~1.8k if it reads all its reference files. Until then it costs about 94 tokens; SKILL.md has 484 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~94
When it runs · the whole SKILL.md, loaded when a task matches
~1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

Without a licence we can't republish the file, so here is its outline and opening line. It has 484 words (~1,045 tokens).

“The question is not only "what broke". It's also "why did it break now", and "will it keep breaking". This skill strings together:”

— opening of SKILL.md by BuilderIO
name
investigate-bug
user-invocable
true
scope
dev
metadata.internal
true

Read the full SKILL.md on GitHub

Files

SKILL.md and 3 other files (scripts, references) in .agents/skills/investigate-bug of BuilderIO/agent-native.

  • SKILL.md
  • references/bug-verdicts.md
  • scripts/bug-verdict.ts
  • scripts/summarize.ts

Open the folder on GitHubat commit 1c2de07

Compare with similar skills

Investigate Bug next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Investigate Bug compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Investigate Bug this skillBuilderIO/agent-native7.1k—~1kAutomated safety check: PassNone
Supporthomebridge-plugins/homebridge-eufy224—~1.7kAutomated safety check: PassApache-2.0
Bug To Patch GeneratorArabelaTso/Skills-4-SE253—~4.4kAutomated safety check: PassApache-2.0
Dev ReportFHIR/fhir-codegen155—~4.1kAutomated safety check: PassMIT
Prp DebugWirasm/prp2.3k—~1.1kAutomated safety check: PassMIT
Prp DebugWirasm/prp2.3k—~1.1kAutomated safety check: PassMIT

Similar skills

  • Support

    homebridge-plugins/homebridge-eufy

    Triage a GitHub issue using diagnostics archives and logs. An agent skill from homebridge-plugins/homebridge-eufy.

    224 GitHub stars~1.7k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Bug To Patch Generator

    ArabelaTso/Skills-4-SE

    Generate code fixes and patches from bug reports, failing test cases, error messages, and stack traces.

    253 GitHub stars~4.4k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

  • Dev Report

    FHIR/fhir-codegen

    Drafts and iterates on local-development bug reports in the role of a staff-level Tech Lead.

    155 GitHub stars~4.1k tokensUpdated 2 days ago
    Testing & QAAuto-check passed

  • Prp Debug

    Wirasm/prp

    Diagnoses a bug, error, stack trace, regression, or unexplained behavior and publishes the evidence-backed root cause to GitHub.

    2.3k GitHub stars~1.1k tokensUpdated 8 days ago
    DevelopmentAuto-check passed

  • Prp Debug

    Wirasm/prp

    Diagnoses a bug, error, stack trace, regression, or unexplained behavior and publishes the evidence-backed root cause to GitHub.

    2.3k GitHub stars~1.1k tokensUpdated 8 days ago
    DevelopmentAuto-check passed

  • Generate Test Plan

    openshift-eng/ai-helpers

    Generate a comprehensive manual testing guide from a Jira issue, GitHub PR URLs, or both.

    120 GitHub stars~1.6k tokensUpdated 3 days ago
    Testing & QAAuto-check passed

More from BuilderIO/agent-native

All 108 skills in this repo

  • Bug Trace

    BuilderIO/agent-native

    Find the root cause of a reported bug: take in the report (GitHub issue, Jira ticket, file, or pasted text), trace the failing path hop by hop with each hop's runtime precondition, find the recent…

    7.1k GitHub stars~555 tokensUpdated today
    Auto-check passed

  • Identify Fragile Systems

    BuilderIO/agent-native

    Nightly refactor review: find the systems the last day's commits hit hardest, use three weeks of history to tell fragile from fast-moving, write a plan per systemic fix, and file deduplicated Jira…

    7.1k GitHub stars~957 tokensUpdated today
    Auto-check passed

  • Jira Refactor Findings

    BuilderIO/agent-native

    File and track refactor findings in Jira without duplicates: match a run against existing refactor-findings tickets, create tickets from plan files (Pod, label, attached plan, run link), record…

    7.1k GitHub stars~779 tokensUpdated today
    Auto-check passed

  • System History

    BuilderIO/agent-native

    Blobless-safe git and PR history for this repo. An agent skill from BuilderIO/agent-native.

    7.1k GitHub stars~727 tokensUpdated today
    Auto-check passed

  • Actions

    BuilderIO/agent-native

    How to create and run agent actions. An agent skill from BuilderIO/agent-native.

    7.1k GitHub stars~4.4k tokensUpdated today
    Auto-check passed

  • Client Methods

    BuilderIO/agent-native

    Client method surface rules. An agent skill from BuilderIO/agent-native.

    7.1k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Investigate Bug

What does Investigate Bug do?

Given a bug report (GitHub issue, Jira ticket, file, or pasted text), find its root cause and decide per symptom whether it is a one-off or one instance of a pattern worth fixing at the root, then…. Investigate Bug is an agent skill from BuilderIO/agent-native. Given a bug report (GitHub issue, Jira ticket, file, or pasted text), find its root cause and decide per symptom whether it is a one-off or one instance of a pattern worth fixing at the root, then file or sight a deduplicated refactor ticket when it is.

When should I use Investigate Bug?

Investigate Bug fits situations like: tasks that involve QA and bug reports; tasks that involve Root cause analysis; tasks that involve Refactoring.

How do I install Investigate Bug in Claude Code?

Run `npx skills add BuilderIO/agent-native --skill investigate-bug -a claude-code`. Or copy the skill folder (.agents/skills/investigate-bug in BuilderIO/agent-native) into .claude/skills/investigate-bug in your project. Claude Code loads it when a task matches its description.

How do I install Investigate Bug in Codex?

Run `npx skills add BuilderIO/agent-native --skill investigate-bug -a codex`. Or copy the skill folder (.agents/skills/investigate-bug in BuilderIO/agent-native) into .agents/skills/investigate-bug in your project. Codex loads it when a task matches its description.

Can I use Investigate Bug in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add BuilderIO/agent-native --skill investigate-bug -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/investigate-bug, .gemini/skills/investigate-bug, .github/skills/investigate-bug and .opencode/skills/investigate-bug in your project.

What does Investigate Bug need to run?

Going by SKILL.md and its folder, Investigate Bug needs TypeScript for the scripts in its folder. Our summary lists: Node.js.

Does Investigate Bug access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Investigate Bug safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Investigate Bug use?

No licence was found for Investigate Bug or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Investigate Bug use?

About 1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 716 tokens, read only when the agent opens those files.

What are the alternatives to Investigate Bug?

Skills that share tags, products or a category with Investigate Bug: Support (homebridge-plugins/homebridge-eufy, 224 stars), Bug To Patch Generator (ArabelaTso/Skills-4-SE, 253 stars), Dev Report (FHIR/fhir-codegen, 155 stars) and Prp Debug (Wirasm/prp, 2.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Investigate Bug?

BuilderIO (a GitHub organization) maintains it in BuilderIO/agent-native, which has 7,113 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on October 10, 2026.

Source: BuilderIO/agent-native on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.