issue-audit

Analyze a Linear team's issues to surface organization patterns and conventions.

16|3|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/breethomas/bette-think --skill issue-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-audit
Source: https://github.com/breethomas/bette-think/tree/main/plugins/bette-think/skills/issue-audit
Command: npx skills add https://github.com/breethomas/bette-think --skill issue-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps product managers onboarding to a new team quickly understand how that team organizes work in Linear by identifying workflow states, label taxonomies, cycle usage, and writing patterns so the PM can follow established conventions.

Core Features & Use Cases

  • Team structure analysis: Fetches workflow states, labels, and cycle configuration to map how work flows from triage to done.
  • Sampled issue review: Selects a balanced nine-issue sample (active, completed, backlog) and reports patterns in titles, descriptions, hierarchy, and label usage.
  • Onboarding guidance: Produces concrete recommendations and follow-up queries (e.g., show issue details, filter by label) to help new PMs adopt team conventions quickly.

Quick Start

Invoke the skill by typing /issue-audit followed by the team's name, for example /issue-audit Customer Experience.

Frequently Asked Questions about issue-audit

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

FAQPage Schema
How do I understand a new team's Linear issue conventions during onboarding?

Auditing Linear issue conventions involves sampling active, completed, and backlog issues to surface organization patterns. It maps workflow states, labels, and cycle configurations so you can follow established team conventions.

How do I analyze Linear workflow states and labels to map team structure?

You analyze Linear workflow states and labels by fetching issue metadata, workflow states, and cycle configurations. Sampling nine issues across active, completed, and backlog states reveals how the team structures work from triage to done.

Do I need Linear MCP access to sample and audit team issues?

Yes, you need Linear MCP access to audit team issues. The skill requires fetching issue fields, workflow states, labels, and cycle information through Linear MCP metadata to infer conventions from the sampled issues.

What is the best way to discover patterns in Linear issue titles and descriptions?

The best way to discover patterns in Linear issue titles and descriptions is by sampling a balanced set of active, completed, and backlog issues. This approach reveals writing patterns, hierarchy usage, and label taxonomies.

Can I get onboarding recommendations for following established Linear team conventions?

Yes, analyzing a Linear team's issue patterns produces concrete onboarding recommendations and follow-up queries. This helps new PMs adopt team conventions quickly by providing guidance on issue details and label filtering.

How many Linear issues do I need to sample to infer team conventions?

A nine-issue sample across active, completed, and backlog states is needed to infer team conventions in Linear. This balanced sample surfaces patterns in titles, descriptions, hierarchy, and label usage.