linear-bug-revise

To standardize Linear bug reports, this Skill extracts issue details via MCP tools, analyzes the content, and rewrites titles and descriptions into a structured template. It then presents the revised version for user confirmation before updating the issue.

Standardizing a Linear bug report will not cause information loss. The Skill strictly preserves all original details, including environment info and attachments, and only modifies the title, description, and labels while adding a 'revised by ai' label.

You can automate Linear issue tracking format updates by providing a Linear issue link to this Skill. It refactors hastily written tickets into clear, actionable reports with standardized sections for environment, steps to reproduce, and expected results.

Yes, the Linear bug report revision process requires manual confirmation. The Skill analyzes the current content, generates a revised version, and presents it to the user for approval before updating the Linear issue.

When applying standardized formatting to an existing Linear issue, only the title, description, and labels are modified. The Skill adds a 'revised by ai' label to the issue while strictly retaining all other original information.

Yes, you can use this tool to rewrite Linear issue titles and descriptions for your QA team. It refactors existing bug reports into clear, actionable tickets with standardized sections, ensuring they contain all necessary information for efficient tracking and resolution.