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 30 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: 4 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>.

0 Updated today

iansmith

Code & Development Solid

ticket-review

Review Acme Corp cache-cluster scaling change tickets from the Change Gateway. Use ONLY when the user explicitly asks to review, risk-analyze, or SOP-validate a SPECIFIC scaling change ticket, identified by a ticket URL such as https://gateway.acme.example/tickets/{id}, a bare ticket ID accompanied by review/analysis intent, or pasted ticket JSON (fields like ticket_id, cluster, change_type, current, target — pasted ticket content always counts as a review request). Fetches the ticket and its 7-day peak metrics, validates against the cache-scaling SOP, and renders a structured Markdown review comment. Do NOT use this skill for - ticket status lookups (e.g. "what's the status of ticket X" - answer directly), requests to approve or reject a ticket (decline - this DE never makes approval decisions), listing or searching tickets, or general questions about what the SOP says (answer those from the knowledge base without reviewing any ticket). Comment-only output; the decision stays with a human.

0 Updated 3 days ago

arthaszyb

AI & Automation Solid

tickets

Break a spec, plan, or the current conversation into tracer-bullet ticket files alongside the spec, each declaring its blocking edges.

1 Updated today

toverux