hs-bug

SkillDev tools

Create a new bug ticket in Hot Sheet

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the hs-bug skill

What this skill tells your AI

The instructions your AI receives, as published by brianwestphal/glassbox in .agents/skills/hs-bug/SKILL.md and read by ahel’s review.

Create a new Hot Sheet bug ticket. Bugs that should be fixed in the codebase.

Parsing the input:

  • If the input starts with "next", "up next", or "do next" (case-insensitive), set up_next to true and use the remaining text as the title
  • Otherwise, use the entire input as the title

Create the ticket — MCP tool (preferred when the channel is connected): Call the hotsheet_create_ticket tool with { "title": "<TITLE>", "category": "bug", "up_next": <true|false> }. The tool is schema-validated and routes to the channel server's --data-dir so there's no chance of cross-project misrouting.

Fallback (curl):

curl -s -X POST "http://localhost:$HOTSHEET_PORT/api/tickets" \
  -H "Content-Type: application/json" \
  -H "X-Hotsheet-Secret: $HOTSHEET_SECRET" \
  -d '{"title": "<TITLE>", "defaults": {"category": "bug", "up_next": <true|false>}}'

Set these first. Both are machine-specific and deliberately not stored in this file (which is committed and shared with everyone on the repo):

export HOTSHEET_PORT=$(node -p "require('./.hotsheet/settings.local.json').port ?? 4174")
export HOTSHEET_SECRET=$(node -p "require('./.hotsheet/secret.json').secret")

If the request fails (connection refused or 403), re-read those two files — you may be connecting to the wrong Hot Sheet instance. (Older projects keep port and secret in .hotsheet/settings.json instead.)

Report the created ticket number and title to the user.

Signals

GitHub stars
34
Forks
1
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
hs-bug
Source
github.com/brianwestphal/glassbox