ticket-sanitizer

Rename ticket folders to org-ticket_description and create logs, repro, and description.md.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/COLDTURNIP/longhorn-workspace --skill ticket-sanitizer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ticket-sanitizer
Source: https://github.com/COLDTURNIP/longhorn-workspace/tree/main/.opencode/skills/ticket-sanitizer
Command: npx skills add https://github.com/COLDTURNIP/longhorn-workspace --skill ticket-sanitizer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires defensive_prelude.sh.

What problem does it solve?

This skill enforces a standardized naming scheme for ticket folders (${org}-${ticket_id}-${description}) and initializes a ready-to-use directory structure to support consistent task tracking.

Core Features & Use Cases

  • Renames misformatted ticket folders to a three-segment pattern: org-ticket_description (all lowercase).
  • Creates standard subdirectories (logs/ and repro) inside each ticket folder and ensures a description.md exists.
  • Useful after creating or cloning a workspace when ticket folders may arrive in varied formats or lack structure.

Quick Start

Run the script from the workspace root to normalize ticket folders and initialize their structure: bash .opencode/skills/ticket-sanitizer/ticket_sanitizer.sh

Frequently Asked Questions about ticket-sanitizer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize ticket folder naming conventions in bulk?▼

Standardize ticket folder naming by running a Bash script that parses and renames every subfolder under the ticket root to an org-ticket_description format in lowercase. It handles edge cases automatically and provides a dry-run option for safe execution.

What does a standardized ticket directory structure need to include?▼

A standardized ticket directory structure needs logs/ and repro subdirectories along with a description.md file inside each folder. The script creates these missing components automatically while renaming folders to the lowercase naming convention.

Can I preview ticket folder renaming before applying changes permanently?▼

Yes, you can preview ticket folder renaming using the dry-run option before applying changes. The script also offers a force option to bypass safety checks and execute the renaming and directory initialization directly.

How do I initialize logs and repro directories for existing ticket folders?▼

Initialize logs and repro directories by running the sanitizer script from your workspace root. It scans every ticket subfolder, creates missing logs/extracted and repro paths, and ensures a description.md file exists for task tracking.

Does the ticket sanitizer script work without additional shell dependencies?▼

No, the ticket sanitizer script requires the defensive_prelude.sh dependency to execute properly. You need this Bash prerequisite available in your environment before running the folder standardization workflow.

When should I normalize ticket folder formats using a Bash script?▼

Normalize ticket folder formats after creating or cloning a workspace when folders arrive in varied formats or lack standard structure. This ensures consistent task tracking across the org-ticket_description naming convention before starting work.