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

Bug Trace

by BuilderIO in 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…

No licenceAuto-check passedDevelopment

Install Bug Trace

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

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

GitHub CLI
$ gh skill install BuilderIO/agent-native bug-trace --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/bug-trace .claude/skills/bug-trace && 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
bug-trace
GitHub stars
7.1k
Token cost
~555 tokens
SKILL.md length
252 words
Files
3 (incl. scripts, references)
Skills in repo
108
Repo updated
First seen
Licence
None found

At a glance

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…

  • Works in 3 steps: Take in the report → Split symptoms → Trace each symptom
  • Any bug investigation where the cause is not yet known
  • SKILL.md covers 1. Take in the report, 2. Split symptoms, 3. Trace each symptom and Output
  • Runs TypeScript scripts from its folder; calls pnpm

What it does

Bug Trace is an agent skill from 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 change that broke it, and rule out rival explanations. Use for any bug investigation where the cause is not yet known.

Its SKILL.md is about 560 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts and reference files (for example `references/bug-investigation.md` and `scripts/bug-intake.ts`).

It sits in Development, covering Root cause analysis. It works with Jira and GitHub. The repository describes itself as: A framework for building agentic apps.

When your agent uses it

  • Any bug investigation where the cause is not yet known
  • Tasks that involve Root cause analysis

Example prompts

  • “/bug-trace”

Requirements

  • Node.js

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Take in the report
  2. Split symptoms
  3. Trace each symptom

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 1 file in scripts/ (TypeScript), which the agent can run.

    Shell commands in SKILL.md call:

    • pnpm

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

  • Network

    No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.

    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

Bug Trace loads about 555 tokens when it runs, and up to ~1.5k if it reads all its reference files. Until then it costs about 81 tokens; SKILL.md has 252 words of instructions outside code blocks.

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

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 252 words (~555 tokens).

“This skill finds a root cause. It doesn't judge whether the cause is systemic; investigate-bug adds that judgment on top. Never change product code while tracing.”

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

Read the full SKILL.md on GitHub

Files

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

  • SKILL.md
  • references/bug-investigation.md
  • scripts/bug-intake.ts

Open the folder on GitHubat commit 1c2de07

Compare with similar skills

Bug Trace 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.

Bug Trace compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Bug Trace this skillBuilderIO/agent-native7.1k—~555Automated safety check: PassNone
PRP Implementation PlannerWirasm/prp2.3k—~4.1kAutomated safety check: PassMIT
PRP PlanWirasm/prp2.3k—~4kAutomated safety check: PassMIT
YugabyteDB Issue Creatoryugabyte/yugabyte-db11k—~2kAutomated safety check: PassCustom licence
OpenROAD Bug FixerThe-OpenROAD-Project/OpenROAD3.2k—~784Automated safety check: PassBSD-3-Clause
Octocode Code Researchbgauryy/octocode949—~1.5kAutomated safety check: PassMIT

Similar skills

  • PRP Implementation Planner

    Wirasm/prp

    Turns a PRD, issue or description into an implementation-ready plan grounded in codebase evidence, adding root-cause analysis for bugs and publishing issue plans back to the issue.

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

  • PRP Plan

    Wirasm/prp

    Writes an implementation-ready plan for a feature, bug fix, refactor or chore from a PRD, issue or description, grounded in codebase evidence, and can post it back to the source issue.

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

  • YugabyteDB Issue Creator

    yugabyte/yugabyte-db

    Creates a GitHub issue or JIRA ticket for a YugabyteDB change or bug, after scrubbing customer data, secrets and unreleased details from anything public.

    11k GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check passed

  • OpenROAD Bug Fixer

    The-OpenROAD-Project/OpenROAD

    Fixes an OpenROAD bug from a GitHub issue or error code: finds the root cause, implements the fix, adds a regression test and prepares a signed-off commit.

    3.2k GitHub stars~784 tokensUpdated today
    DevelopmentAuto-check passed

  • Octocode Code Research

    bgauryy/octocode

    Researches code with evidence: traces callers, imports and cross-repo links, diagnoses failures and reports findings with exact file and line references and a confidence label.

    949 GitHub stars~1.5k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Link Ticket To Session

    JayantDevkar/claude-code-karma

    Link the current Claude Code session to a ticket (Linear, Jira, GitHub Issues, or GitHub Pull Requests) and cache its title/status in karma.

    329 GitHub stars~1.8k tokensUpdated today
    DevelopmentAuto-check: notes

More from BuilderIO/agent-native

All 108 skills in this repo

  • 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

  • Investigate Bug

    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…

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

Works with

Categories

Questions about Bug Trace

What does Bug Trace do?

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…. Bug Trace is an agent skill from 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 change that broke it, and rule out rival explanations.

When should I use Bug Trace?

Bug Trace fits situations like: any bug investigation where the cause is not yet known; tasks that involve Root cause analysis.

How do I install Bug Trace in Claude Code?

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

How do I install Bug Trace in Codex?

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

Can I use Bug Trace 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 bug-trace -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bug-trace, .gemini/skills/bug-trace, .github/skills/bug-trace and .opencode/skills/bug-trace in your project.

What does Bug Trace need to run?

Going by SKILL.md and its folder, Bug Trace needs TypeScript for the scripts in its folder and the command-line tools its instructions call (pnpm). Our summary lists: Node.js.

Does Bug Trace 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 Bug Trace 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 Bug Trace use?

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

How many tokens does Bug Trace use?

About 555 tokens (SKILL.md is roughly 2.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 950 tokens, read only when the agent opens those files.

What are the alternatives to Bug Trace?

Skills that share tags, products or a category with Bug Trace: PRP Implementation Planner (Wirasm/prp, 2.3k stars), PRP Plan (Wirasm/prp, 2.3k stars), YugabyteDB Issue Creator (yugabyte/yugabyte-db, 11k stars) and OpenROAD Bug Fixer (The-OpenROAD-Project/OpenROAD, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bug Trace?

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.