Trellis Session Insight
mindfold-ai/Trellis
Reach into past AI conversation history through the trellis mem CLI.
Investigate and fix a specific Honeybadger exception in the Bike Index app — pull the fault, read its backtrace, find the offending code, write the fix.
Install Honeybadger Debugging
$ npx skills add bikeindex/bike_index --skill honeybadger-debugging -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install bikeindex/bike_index honeybadger-debugging --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/bikeindex/bike_index.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/honeybadger-debugging .claude/skills/honeybadger-debugging && rm -rf skills-srcUse ~/.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/
Install the "honeybadger-debugging" agent skill from https://github.com/bikeindex/bike_index/tree/main/.claude/skills/honeybadger-debugging into .claude/skills/honeybadger-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honeybadger-debugging", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/bikeindex/bike_index/tree/main/.claude/skills/honeybadger-debuggingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add bikeindex/bike_index --skill honeybadger-debugging -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install bikeindex/bike_index honeybadger-debugging --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bikeindex/bike_index.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/honeybadger-debugging .agents/skills/honeybadger-debugging && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "honeybadger-debugging" agent skill from https://github.com/bikeindex/bike_index/tree/main/.claude/skills/honeybadger-debugging into .agents/skills/honeybadger-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honeybadger-debugging", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bikeindex/bike_index --skill honeybadger-debugging -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install bikeindex/bike_index honeybadger-debugging --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bikeindex/bike_index.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/honeybadger-debugging .cursor/skills/honeybadger-debugging && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "honeybadger-debugging" agent skill from https://github.com/bikeindex/bike_index/tree/main/.claude/skills/honeybadger-debugging into .cursor/skills/honeybadger-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honeybadger-debugging", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/bikeindex/bike_index.git --path .claude/skills/honeybadger-debugging--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add bikeindex/bike_index --skill honeybadger-debugging -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install bikeindex/bike_index honeybadger-debugging --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bikeindex/bike_index.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/honeybadger-debugging .gemini/skills/honeybadger-debugging && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "honeybadger-debugging" agent skill from https://github.com/bikeindex/bike_index/tree/main/.claude/skills/honeybadger-debugging into .gemini/skills/honeybadger-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honeybadger-debugging", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install bikeindex/bike_index honeybadger-debuggingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add bikeindex/bike_index --skill honeybadger-debugging -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/bikeindex/bike_index.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/honeybadger-debugging .github/skills/honeybadger-debugging && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "honeybadger-debugging" agent skill from https://github.com/bikeindex/bike_index/tree/main/.claude/skills/honeybadger-debugging into .github/skills/honeybadger-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honeybadger-debugging", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bikeindex/bike_index --skill honeybadger-debugging -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install bikeindex/bike_index honeybadger-debugging --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bikeindex/bike_index.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/honeybadger-debugging .opencode/skills/honeybadger-debugging && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "honeybadger-debugging" agent skill from https://github.com/bikeindex/bike_index/tree/main/.claude/skills/honeybadger-debugging into .opencode/skills/honeybadger-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honeybadger-debugging", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
honeybadger-debugging- GitHub stars
- 308
- Token cost
- ~1k tokens
- SKILL.md length
- 494 words
- Files
- 1
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Investigate and fix a specific Honeybadger exception in the Bike Index app — pull the fault, read its backtrace, find the offending code, write the fix.
- Works in 4 steps: message and params — the failing input… → App frames — the default listing,… → all-frames — when the raise is inside a… → …
- Ever a request names one Honeybadger error: a pasted fault URL (app.honeybadger.io/projects/…/faults/…)
- SKILL.md covers Pull the fault with bin/binx_hb, Read the notice in this order and Then fix it
- Calls git; needs HONEYBADGER_PERSONAL_AUTH_TOKEN
What it does
Honeybadger Debugging is an agent skill from bikeindex/bike_index. Investigate and fix a specific Honeybadger exception in the Bike Index app — pull the fault, read its backtrace, find the offending code, write the fix. Trigger whenever a request names one Honeybadger error: a pasted fault URL (app.honeybadger.io/projects/…/faults/…), a fault ID, an error class plus "in production" (Vips::Error, NoMethodError in AfterStolenRecordSaveJob), or phrasings like "fix this Honeybadger error", "why is this erroring in prod", "what's causing this exception", "look at this HB fault". Use…
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Debugging. The repository describes itself as: All the code for Bike Index, because we love you. The licence is AGPL-3.0.
When your agent uses it
- Ever a request names one Honeybadger error: a pasted fault URL (app.honeybadger.io/projects/…/faults/…)
- An error class plus in production (Vips::Error
- NoMethodError in AfterStolenRecordSaveJob)
- Phrasings like fix this Honeybadger error
Example prompts
- “in production”
- “fix this Honeybadger error”
- “why is this erroring in prod”
- “/honeybadger-debugging”
Requirements
- A credential in HONEYBADGER_PERSONAL_AUTH_TOKEN
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- message and params — the failing input is usually right here. For a
- App frames — the default listing, deepest first. The top frame is where it
- all-frames — when the raise is inside a gem and you need the call path
- deploy — the revision live when it fired. A fault created minutes after
What it can do on your machine
Read from SKILL.md and the folder at commit f1852cb. 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
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, 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 these keys or tokens, usually read from environment variables:
HONEYBADGER_PERSONAL_AUTH_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Honeybadger Debugging loads about 1k tokens when it runs. Until then it costs about 192 tokens; SKILL.md has 494 words of instructions outside code blocks.
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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:32
`HONEYBADGER_PERSONAL_AUTH_TOKEN` from `.env.development`. Without it
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); files beside SKILL.md are not scanned.
SKILL.md
The full file from bikeindex/bike_index at commit f1852cb, republished under its AGPL-3.0 licence (© bikeindex). 494 words, ~1,044 tokens.
Download SKILL.mdSave it as
.claude/skills/honeybadger-debugging/SKILL.md (or your agent's skills folder).- name
- honeybadger-debugging
- description
- Investigate and fix a specific Honeybadger exception in the Bike Index app — pull the fault, read its backtrace, find the offending code, write the fix. Trigger whenever a request names one Honeybadger error: a pasted fault URL (`app.honeybadger.io/projects/…/faults/…`), a fault ID, an error class plus "in production" (`Vips::Error`, `NoMethodError in AfterStolenRecordSaveJob`), or phrasings like "fix this Honeybadger error", "why is this erroring in prod", "what's causing this exception", "look at this HB fault". Use `bin/binx_hb` for fault and notice detail; it is the only Honeybadger reader this repo uses. Not for a broad production health sweep across many sources, and not for reading raw log files (that's production-log-inspection).
Fixing a Honeybadger exception
Pull the fault with bin/binx_hb
Run it from the repo root. Two modes matter here: fault for the summary, notice for the backtrace.
bin/binx_hb fault https://app.honeybadger.io/projects/35931/faults/133010748
bin/binx_hb notice backend/133010748Both take a pasted fault URL or <project>/<fault_id>, where project is
backend, frontend, or csp. Each prints raw: tmp/hb-…json on its last
line — answer follow-up questions with jq against that file rather than
fetching again.
It reads HONEYBADGER_PERSONAL_AUTH_TOKEN from .env.development. Without it
the command exits saying so — get a new token at honeybadger.io/users/edit and
ask the user to set it. Don't fall back to the honeybadger MCP server — it can't redirect a notice to
a file, so a 130 KB backtrace lands whole in context. Aggregates are covered too
— binx_hb faults, trend and counts.
Read the notice in this order
messageandparams— the failing input is usually right here. For a job,paramsholds the Sidekiq hash andargsnames the record to reproduce against.- App frames — the default listing, deepest first. The top frame is where it
raised, the bottom is the entry point.
[PROJECT_ROOT]is the repo root. --all-frames— when the raise is inside a gem and you need the call path that reached it.deploy— the revision live when it fired. A fault created minutes after that deploy makesgit show <revision>the first place to look.
One notice is almost always enough; repeat notices of a fault are near-identical.
Pass --limit N only when you suspect the occurrences genuinely differ — a
browser-specific frontend error, or params that vary between failures.
Then fix it
Decide which kind of fault it is first — the two need different work.
Show full SKILL.md (222 more words)Show less
Deterministic — a bug reachable from the input
- Reproduce from
args/paramsbefore changing code —bundle exec rails runneragainst the dev database is usually enough. - Cover the fix with a spec; the
rspec-testingskill has the house style. - Check whether the same pattern exists elsewhere.
Errno::ENOENTin one image job usually means every image job shares the bug.
Transient — a 5xx or timeout from S3/R2, the image CDN, another service
Don't try to reproduce it. The tell is a burst of notices inside a few seconds
and then nothing, with a message naming the provider rather than your code.
- Check the job's retry setting first.
config/honeybadger.ymlsetssidekiq.attempt_threshold, which only drops the first failure of a retryable job —retry: falsereports every blip, andScheduledJobdefaults to it. - A retry only silences a blip shorter than Sidekiq's first backoff,
15 + rand(10)seconds. Check the notice timestamps against that. - Check what a mid-operation failure leaves behind — retrying doesn't help work
that isn't idempotent.
ActiveStorage::Blob#purgedestroys the row before deleting the file, so a failed delete orphans the file for good. - Find prior occurrences by error class, not job name. Honeybadger's
qdoesn't match the component field, and a renamed component splits the history.
Don't resolve, ignore, or comment on the fault in Honeybadger — marking it fixed is the user's call once the fix ships.
© bikeindex, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/honeybadger-debugging of bikeindex/bike_index.
Open the folder on GitHubat commit f1852cb
Compare with similar skills
Honeybadger Debugging 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Honeybadger Debugging this skillbikeindex/bike_index | 308 | — | ~1k | Automated safety check: Notes | AGPL-3.0 | |
| Trellis Session Insightmindfold-ai/Trellis | 15k | 4 repos | ~1.7k | Automated safety check: Pass | AGPL-3.0 | |
| Native Data FetchingCherryHQ/cherry-studio-app | 4k | 6 repos | ~2.9k | Automated safety check: Notes | MIT | |
| Debugging Executionsn8n-io/n8n | 207k | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Aoti Debugpytorch/pytorch | 104k | 1 repos | ~1.7k | Automated safety check: Pass | Custom licence | |
| Herdr Throwaway Reproductionherdrdev/herdr | 43k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Native Data Fetching
CherryHQ/cherry-studio-app
A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.
- Official
Debugging Executions
n8n-io/n8n
Debug failed or wrong-output workflow executions using executions tools.
Aoti Debug
pytorch/pytorch
Debug AOTInductor (AOTI) errors and crashes. An agent skill from pytorch/pytorch.
Herdr Throwaway Reproduction
herdrdev/herdr
Runs a disposable, uniquely named Herdr session inside an existing one so runtime, pane, terminal or API bugs can be reproduced without touching the main session.
Systematic Debugging
ultralisp/ultralisp
A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes
More from bikeindex/bike_index
All 11 skills in this repoAdmin Data API
bikeindex/bike_index
Read live production data from Bike Index through the admin OAuth token — Sidekiq and PgHero status, and the user-submitted bug reports — the same data as the cookie-gated dashboards, but…
GitHub PR Images
bikeindex/bike_index
Embed a local image file into an existing GitHub PR — either in the PR body or as a comment.
Manufacturers
bikeindex/bike_index
Add a manufacturer to Bike Index in production through the admin OAuth token (POST /admin/manufacturers).
PR
bikeindex/bike_index
Create or update a pull request for the current branch. An agent skill from bikeindex/bike_index.
Fixing Flaky Failures
bikeindex/bike_index
How to fix a test that fails intermittently in Bike Index — one that passes locally but fails on CI, fails on one shard, passes on re-run, or is already tagged :flaky.
Merge Conflicts
bikeindex/bike_index
How to bring a branch up to date and resolve git merge conflicts the way this repo expects — merge (never rebase or force-push), understand each side's intent before choosing, ask when a resolution…
Related
Categories
Questions about Honeybadger Debugging
What does Honeybadger Debugging do?
Investigate and fix a specific Honeybadger exception in the Bike Index app — pull the fault, read its backtrace, find the offending code, write the fix. Honeybadger Debugging is an agent skill from bikeindex/bike_index. Investigate and fix a specific Honeybadger exception in the Bike Index app — pull the fault, read its backtrace, find the offending code, write the fix.
When should I use Honeybadger Debugging?
Honeybadger Debugging fits situations like: ever a request names one Honeybadger error: a pasted fault URL (app.honeybadger.io/projects/…/faults/…); an error class plus in production (Vips::Error; noMethodError in AfterStolenRecordSaveJob); phrasings like fix this Honeybadger error.
How do I install Honeybadger Debugging in Claude Code?
Run `npx skills add bikeindex/bike_index --skill honeybadger-debugging -a claude-code`. Or copy the skill folder (.claude/skills/honeybadger-debugging in bikeindex/bike_index) into .claude/skills/honeybadger-debugging in your project. Claude Code loads it when a task matches its description.
How do I install Honeybadger Debugging in Codex?
Run `npx skills add bikeindex/bike_index --skill honeybadger-debugging -a codex`. Or copy the skill folder (.claude/skills/honeybadger-debugging in bikeindex/bike_index) into .agents/skills/honeybadger-debugging in your project. Codex loads it when a task matches its description.
Can I use Honeybadger Debugging 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 bikeindex/bike_index --skill honeybadger-debugging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/honeybadger-debugging, .gemini/skills/honeybadger-debugging, .github/skills/honeybadger-debugging and .opencode/skills/honeybadger-debugging in your project.
What does Honeybadger Debugging need to run?
Going by SKILL.md and its folder, Honeybadger Debugging needs the command-line tools its instructions call (git) and credentials named HONEYBADGER_PERSONAL_AUTH_TOKEN. Our summary lists: A credential in HONEYBADGER_PERSONAL_AUTH_TOKEN.
Does Honeybadger Debugging access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Honeybadger Debugging safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Honeybadger Debugging use?
Honeybadger Debugging is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Honeybadger Debugging 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.
What are the alternatives to Honeybadger Debugging?
Skills that share tags, products or a category with Honeybadger Debugging: Trellis Session Insight (mindfold-ai/Trellis, 15k stars), Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars), Debugging Executions (n8n-io/n8n, 207k stars) and Aoti Debug (pytorch/pytorch, 104k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Honeybadger Debugging?
bikeindex (a GitHub organization) maintains it in bikeindex/bike_index, which has 308 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 9, 2026.
Source: bikeindex/bike_index on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.