Menu
Create a new feature 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
Run all tests and linters, audit stateful modules for untested state transitions, check anti-patterns, and generate a comprehensive code-quality report for video-studio. Use for broad quality audits and release-readiness checks.
Check video-studio code for standardization, readability, maintenance complexity, and defensive coding. Use for maintainability reviews, cleanup audits, and defensive-coding assessments.
Compare video-studio requirements with implementation, find drift, and synchronize AI summaries and repository guidance. Use for requirements audits, documentation drift checks, and requirements-summary maintenance.
Read the latest Glassbox code review and apply all feedback annotations. Use when asked to process, apply, or follow up on a Glassbox review.
Prepare video-studio for a notable or major release by refreshing the README, upgrading domotion-svg, rebuilding generated demos, reviewing release media, and producing a capture list without publishing. Use before a major release or presentation-focused release review.
Create a new bug ticket in Hot Sheet
| name | hs-feature |
| description | Create a new feature ticket in Hot Sheet |
Create a new Hot Sheet feature ticket. New features to be implemented.
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": "feature", "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: 6f11befdc8c3a7c5263607dda96d69fb" \
-d '{"title": "<TITLE>", "defaults": {"category": "feature", "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.