Menu
Create a new bug ticket in Hot Sheet
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Prepare gitgist for a major release — refresh README.md so it stays compelling and advertises the most important features, upgrade the demo renderer (domotion-svg) to the latest version, and review the README demo modes (scripts/demo.mjs) to decide whether the screenshots should change.
Run all available tests and linters, check for anti-patterns, and generate a comprehensive code quality report
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 |
| allowed-tools | Bash |
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: a6d01feccf9904936b8dc30a61e4af97" \
-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.