Convert test findings into Linear tickets with frontmatter metadata and priority mapping.
npx skills add https://github.com/Cottage-Energy/cottage-tests --skill log-bug
Please help me install this Agent Skill. Skill: log-bug Source: https://github.com/Cottage-Energy/cottage-tests/tree/main/.claude/skills/log-bug Command: npx skills add https://github.com/Cottage-Energy/cottage-tests --skill log-bug
Create well-structured Linear tickets from test findings — for both bugs (things that are broken) and improvements (areas that could be better). This guide helps QA and development teams standardize ticket creation, reduce manual drafting, and ensure consistent prioritization and context.
Provide a test finding summary and context to generate a Linear bug or improvement ticket.
High-intent search queries and answers about installing and using this skill.
To convert test findings into Linear tickets, provide a test finding summary and context. The system classifies the ticket as a bug or improvement, applies the correct title prefix and priority mapping, formats the ticket using frontmatter metadata, and links related work.
Structuring Linear bug reports from exploratory tests requires applying standardized prefixes like [BUG] or [IMPROVEMENT] and mapping severity to priority. This approach uses test context to classify tickets, ensure input validation, and avoid duplicate bug reports.
Yes, you can use exploratory test context to set priority and link related work in Linear. The system leverages test context to decide the ticket type and applies severity- or impact-based priority mappings to reflect urgency accurately.
Generating Linear tickets for improvements does not require manual priority mapping. The system automatically applies severity- or impact-based priority mappings and uses frontmatter metadata to ensure consistent prioritization and context for both bugs and improvements.
Duplicate avoidance when creating Linear tickets from test plans works by validating input and checking existing tickets before creation. This ensures test findings are not duplicated and maintains consistent context by linking related work across exploratory tests and test plans.
leonj1Analyze sampled project test files for naming, structure, and framework conventions.
bradtaylorsfAnalyze Linear tickets to detect duplicates and investigate Git history for fixes.
Dev10x-GuruExecute QA regression tests on staging with headless Playwright and post results to Linear.
mytechsonamyClassify test failures into BUG, FLAKY, ENVIRONMENT, TEST-DEFECT, or UNCLASSIFIED with RTM linkage.
