absorb-tickets

Solid

Absorb domotion svg-scrubber `.ticket` files (and their frame PNGs) from the repo root into Hot Sheet tickets, then move the originals to the Trash. Use when the user has svg-scrubber review exports (`*.ticket` + `demo-*.png`) sitting in the project root to file.

Code & Development 34 stars 1 forks Updated today MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

100

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

Import **svg-scrubber** `.ticket` files into Hot Sheet, then trash the originals. ## Background The domotion **svg-scrubber** tool, run in *review mode*, lets a reviewer scrub an animated SVG (e.g. `assets/demo.svg`), mark a problem at a specific frame / time-range / region, and export it. Each exported issue lands in the project root as a pair: - `<slug>-<stamp>.ticket` — a JSON payload (`tool: "svg-scrubber"`, `version: 1`) - `<slug>-<stamp>.png` — the captured frame snapshot (referenced by the ticket's `framePng` field) The `.ticket` JSON is designed to map **straight onto Hot Sheet**: its `title`, `category`, and `details` fields drop directly into `hotsheet_create_ticket` (the `category` enum — `bug` / `issue` / `feature` / `task` / `investigation` / `requirement_change` — is already exactly Hot Sheet's category set, so **no mapping is needed**). The `details` field is pre-rendered Markdown containing the SVG path, frame time, selected range, and region coordinates. Example `.ticket`: ```json { "tool": "svg-scrubber", "version": 1, "title": "unnecessary crossfade", "category": "bug", "svgName": "demo", "framePng": "/Users/westphal/Documents/glassbox/demo-1782875621671.png", "details": "…markdown with SVG file / frame time / range / region…" } ``` ## What this skill does For every `*.ticket` in the repo root, in `createdAt` order: 1. Create a Hot Sheet ticket from `title` / `category` / `details`. 2. Attac...

Details

Author: brianwestphal
Repository: brianwestphal/glassbox
Created: 6 months ago
Last Updated: today
Language: TypeScript
License: MIT

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Listed

single-ticket

Retrofit an existing ticket to the five-section leaf-ticket standard so it can be handled by :plan --ticket-driven or a fleet run. Interviews toward the missing structure with /slopstop:grill, drafts the five sections, runs the huge-tier adversary loop, then confirms and pushes — preserving the original ticket verbatim below a separator. Interactive only. Invoke as /slopstop:single-ticket <TICKET-ID>.

2 Updated 3 days ago

iansmith

Web & Frontend Listed

ticket-shaping

Turn a UX/design-level description of a feature or change into an implementation-ready ticket in whichever tracker the repo uses (Linear, Notion, or in-repo docs/tickets) — UX spec plus a concrete, file-level recommended implementation plan the user challenges before it is written down. The user describes how something should behave and look, NOT the technical approach; this skill interviews them one question at a time, drafts the plan, hands it to `grill-plan`, then writes the ticket(s). Trigger when the user says "shape this", "write a ticket", "let's spec", "I want the app to…", "it should feel like…", "turn this idea into a task", or describes desired behavior/looks and asks to capture it for later implementation. NOT for stress-testing an already-written plan (that's `grill-plan` on its own) and NOT for actually building the feature.

0 Updated 1 months ago

ltatarev

AI & Automation Listed

to-tickets

Split a slice-ready spec from /to-spec into independent vertical-slice work-units for a large ticket, then render an approval board and STOP. Each slice is a thin COMPLETE path through every layer of the chain it needs, verifiable on its own testing seam. Writes one work-unit per slice under handoffs/<TICKET-ID>/slices/ plus a slice-board.md carrying the dependency waves and a DAG, for you to accept or edit. Internal work-units only — it never writes to the tracker. Runs inside the /start-ticket DECOMPOSE path, after /to-spec and before the orchestrator dispatches any slice.

2 Updated 4 days ago

konstantinos-malavazos