Menu
Create a new bug ticket in Hot Sheet
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Generate a diff-grounded, one-page technical changelog for a Domotion release — from the actual code changes between the last production tag and HEAD (the next, still-unreleased version). Asks for the next version number, since HEAD is not yet in package.json.
Check requirements docs against implementation and report discrepancies
Create a new feature ticket in Hot Sheet
Create a new investigation ticket in Hot Sheet
Create a new issue ticket in Hot Sheet
Create a new req change ticket in Hot Sheet
| name | hs-bug |
| description | Create a new bug ticket in Hot Sheet |
Create a new Hot Sheet bug ticket. Bugs that should be fixed in the codebase.
Parsing the input:
up_next to true and use the remaining text as the titleCreate 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:4174/api/tickets \
-H "Content-Type: application/json" \
-H "X-Hotsheet-Secret: 827ca73d6e98e85625df80114bdb6607" \
-d '{"title": "<TITLE>", "defaults": {"category": "bug", "up_next": <true|false>}}'
If the request fails (connection refused or 403), re-read .hotsheet/settings.json for the current port and secret values — you may be connecting to the wrong Hot Sheet instance.
Report the created ticket number and title to the user.