om-prepare-issue

Creates deduplicated, spec-linked tracker issues with SDLC labels from briefs.

2.6k|159|Updated Mar 8, 2021
One-click install
npx skills add https://github.com/go-musicfox/go-musicfox --skill om-prepare-issue-go-musicfox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: om-prepare-issue
Source: https://github.com/go-musicfox/go-musicfox/tree/main/.agents/skills/om-prepare-issue
Command: npx skills add https://github.com/go-musicfox/go-musicfox --skill om-prepare-issue-go-musicfox

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a rough feature idea or bug report into a well-formed, actionable tracker issue is tedious and error-prone: duplicates pile up, issues lack implementation guidance, and labels are applied inconsistently. This Skill converts a free-form brief into a single high-quality issue that a future developer or automation run can pick up cold. ## Core Features & Use Cases - Duplicate Detection: Searches open issues and PRs with multiple query phrasings before creating anything, reusing or commenting on credible duplicates instead of filing copies. - Spec Linking and Authoring: Links an existing covering spec when one exists, or delegates to a spec-authoring workflow that lands a design-only spec PR when a substantial feature needs one. - Codebase-Grounded Guidance: When no spec applies, embeds step-by-step implementation instructions referencing real file paths, functions, and required tests. - SDLC Labeling and Evidence: Applies category, priority, and risk labels with an auditable rationale comment, and attaches user-provided screenshots as issue evidence. - Use Case: A product manager says "file an issue for adding DLNA volume control" — the Skill checks for duplicates, finds no spec, analyzes the codebase, and files a labeled issue with concrete implementation steps. ## Quick Start Ask the agent to file an issue for your idea, for example: "File an issue for adding gapless playback support to the player."

Frequently Asked Questions about om-prepare-issue

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

FAQPage Schema
How do I turn a feature idea into a well-formed tracker issue?

Provide a free-form brief describing the feature or bug. The Skill searches for duplicates, links or authors a covering spec when needed, embeds codebase-grounded implementation steps, and creates the issue with SDLC labels applied.

How does the issue creation avoid duplicate tickets?

It runs multiple search queries against open issues and PRs using varied phrasings of the brief's key terms, then reads top candidates to judge semantic overlap. Credible duplicates get a comment with new detail instead of a new issue.

Does it write the implementation code for the issue?

No, it only creates tracker issues and never edits repository source files. The one exception is delegating a design-only spec PR for substantial features lacking a spec; implementation happens later through separate fix or implement workflows.

Can I attach screenshots to the created issue?

Yes, pasted screenshots or image file paths are uploaded through the tracker's image evidence operation and embedded in an evidence section. If upload is unavailable, local paths are referenced in the body without failing issue creation.

What labels get applied to new issues automatically?

Each issue receives one category label such as feature or bug, plus exactly one priority and one risk label inferred from the brief. Priority and risk can be overridden with explicit flags, and a rationale comment documents the reasoning.

When should I use issue management instead of creating a new issue?

Use the issue management skill when the issue already exists and needs relabeling, clarification, or screenshot analysis. This Skill only creates new issues; enriching existing ones is deliberately out of its scope.