메뉴
Use when investigating production/staging errors, exceptions, crashes, or faults reported in Honeybadger — fetching recent errors, backtraces, occurrence counts, or affected users for a project.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | honeybadger |
| description | Use when investigating production/staging errors, exceptions, crashes, or faults reported in Honeybadger — fetching recent errors, backtraces, occurrence counts, or affected users for a project. |
Read errors from Honeybadger via the hb CLI. The auth token lives in fnox, so
prefix every command with fnox exec --.
hb (/opt/homebrew/bin/hb), NOT honeybadger. The honeybadger
gem CLI only reports data; hb has the Data API for reading faults.HONEYBADGER_AUTH_TOKEN, provided by fnox. Always wrap:
fnox exec -- hb .... Run from a dir where fnox resolves the token
(user's global config at ~/.config/fnox/config.toml provides it).--project-id is required for fault commands. Resolve it from the current
repo (see below) rather than hardcoding one.Before running fault commands, infer which Honeybadger project the user means from the repo you're in:
basename -s .git "$(git remote get-url origin)"
(e.g. github.com/username/example → example). Fall back to the working
dir name if there's no remote.fnox exec -- hb projects list — the first ID column holds the
--project-id value. Match the repo name against the NAME column
case-insensitively.fnox exec -- hb projects list # list projects + fault counts
fnox exec -- hb faults list --project-id <ID> --limit 15 # recent faults (default order=recent)
fnox exec -- hb faults list --project-id <ID> --order frequent
fnox exec -- hb faults list --project-id <ID> -q "NoMethodError" # search/filter
fnox exec -- hb faults get --project-id <ID> --id <FAULT_ID> # detail + backtrace
fnox exec -- hb faults notices --project-id <ID> --id <FAULT_ID> # individual occurrences
fnox exec -- hb faults counts --project-id <ID>
fnox exec -- hb faults affected-users --project-id <ID> --id <FAULT_ID>
--limit max is 25; --order is recent (default) or frequent.recent orders by last-seen regardless of status, so the list mixes
resolved and unresolved faults. There's no server-side resolved filter —
check the RESOLVED column (✓) and filter client-side if you only want
open problems.-o json whenever a message is cut off or you need the full backtrace.-o json
output carries a url field; otherwise build it as
https://app.honeybadger.io/projects/<ID>/faults/<FAULT_ID>.hb deployments, hb insights, hb uptime, hb check-ins.
Run fnox exec -- hb <cmd> --help for flags.fnox exec -- hb faults list --project-id <id> to see what's broken.hb faults get --id <id> for the backtrace.Enable concise, focused mode for the rest of the conversation
Fast-path Playwright CLI recipes for ad-hoc browser testing and screenshots. Use when manually verifying UI changes in a local dev environment - covers installation, the open-snapshot-interact-screenshot loop, stable element targeting, and the gotchas that waste time.
Run a one-shot Claude Code subagent review of the current branch or PR without editing files.
Use when working with the user's dotfiles managed by the `dotfiles` CLI — saving live config into the tracked repository, installing tracked files to live paths, inspecting tracked-file status, or scaffolding a new dotfiles repo.
Use the notes CLI to create, list, read, append to, update, annotate, and delete notes in a date-based markdown archive — including daily todos with task rollover and tag operations across the store.
Enable "Explain Like I'm a Smart 18 Year Old" mode for the rest of the conversation. Use when the user types /eli18.