[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-sentry-linear-type-labeler":3,"mdc--e5cw84-key":35,"related-org-sentry-linear-type-labeler":725,"related-repo-sentry-linear-type-labeler":905},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":12,"stars":24,"repoUrl":25,"updatedAt":26,"license":27,"forks":28,"topics":29,"repo":31,"sourceUrl":33,"mdContent":34},"linear-type-labeler","classify and label Linear issues","Classify and apply Type labels to Linear issues based on their title and description.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},"sentry","Sentry","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fsentry.png","getsentry",[13,17,20,23],{"name":14,"slug":15,"type":16},"Operations","operations","tag",{"name":18,"slug":19,"type":16},"Productivity","productivity",{"name":21,"slug":22,"type":16},"Triage","triage",{"name":9,"slug":8,"type":16},2,"https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fsdk-skills","2026-04-06T18:14:58.40989",null,0,[30],"tag-production",{"repoUrl":25,"stars":24,"forks":28,"topics":32,"description":27},[30],"https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fsdk-skills\u002Ftree\u002FHEAD\u002Fplugins\u002Fsentry-sdk-skills\u002Fskills\u002Flinear-type-labeler","---\nname: linear-type-labeler\ndescription: >\n  Classify and apply Type labels to Linear issues based on their title and description.\nallowed-tools: mcp__linear-server__query_data mcp__linear-server__get_issue mcp__linear-server__save_issue AskUserQuestion\ncompatibility: Requires the Linear MCP server to be configured.\n---\n\n# Linear Type Labeler\n\nClassifies Linear issues and applies a **Type** label from the Sentry workspace's label\ntaxonomy based on the content of each issue's title and description.\n\n## Requirements\n\nThis skill requires the [Linear MCP server](https:\u002F\u002Fgithub.com\u002Flinear\u002Flinear-mcp) to be configured.\n\n## Type Label Reference\n\nType labels in the Sentry workspace (workspace-level, not per-team):\n\n| Label | When to use |\n|---|---|\n| **Bug** | Something is broken, regression, error, crash, incorrect behavior |\n| **Feature** | New capability, integration, API, SDK support — something that doesn't exist yet |\n| **Improvement** | Making existing functionality better — performance, DX, UX, reliability |\n| **Task** | Chore, investigation, spike, migration, cleanup, operational work |\n| **Tracking Issue** | Parent\u002Fumbrella tracking a larger body of work; has sub-issues or a checklist |\n| **Docs** | Documentation, RFC, write-up, changelog, guide |\n| **Tests** | Writing or fixing tests, coverage, test infrastructure |\n\n## Workflow\n\n### Step 1 — Identify issues to process\n\nTwo modes:\n\n**A — List of Linear IDs provided** (e.g. `SDK-123, SDK-456`):\n- Fetch each issue by ID using `get_issue`. Skip the team-fetch step entirely.\n\n**B — No IDs provided**:\n- Infer the team: (1) current GitHub repository name — for the `getsentry` org, the repo name\n  matches the Linear team name, (2) explicitly stated by the user, (3) if still ambiguous, ask.\n\n### Step 2 — Fetch label IDs\n\nUse `query_data` to fetch workspace-level labels and build a UUID map:\n\n```\nquery_data: fetch all labels for the workspace (not the team)\n→ filter to those whose parent label name is \"Type\"\n→ build a map: { \"Bug\": \"\u003Cuuid>\", \"Feature\": \"\u003Cuuid>\", ... }\n```\n\nIf the workspace has no \"Type\" label group, surface that to the user before proceeding.\n\n### Step 3 — Fetch and filter issues\n\n**If in mode A (list of IDs):** use the already-fetched issues from Step 1. Filter client-side:\nkeep only those where none of the issue's label IDs appear in the Step 2 UUID map values.\n\n**If in mode B (team):** use `query_data` to list issues for the team, **including each issue's\nlabel IDs**. Paginate (limit 50, use `cursor`) until done. Filter client-side: keep only issues\nwhere none of the issue's label IDs appear in the Step 2 UUID map values (i.e., no Type label\nassigned yet).\n\nAnnounce the total candidate count before continuing. If there are more than 25 candidates,\nprocess in chunks of 25, confirming each chunk before the next.\n\n### Step 4 — Classify each issue\n\nFor each candidate issue, read its **title** and **description**. Apply heuristics in **priority\norder** — stop at the first match:\n\n1. Title or description is clearly about testing work: mentions \"test\", \"tests\", \"coverage\",\n   \"test infra\", \"test suite\", \"unit test\", \"integration test\" → **Tests**\n2. Title or description is clearly about documentation: mentions \"docs\", \"README\", \"changelog\",\n   \"RFC\", \"spec\", \"guide\", \"write-up\", \"develop.sentry.dev\" → **Docs**\n3. Title contains `[META]`, `[EPIC]`, \"Track\", \"Tracking\"; or description has a checklist of\n   Linear\u002FGitHub issue links → **Tracking Issue**\n4. Title starts with \"Fix\", \"Fixes\", \"Broken\", \"Error\", \"Crash\", \"Regression\" → **Bug**\n5. Title starts with \"Improve\", \"Optimize\", \"Enhance\"; or is a refactor with user-visible impact\n   (changes behavior, performance, or API ergonomics) → **Improvement**\n6. Title starts with \"Investigate\", \"Spike\", \"Migrate\", \"Update\", \"Clean up\", \"Chore\"; or is a\n   refactor with no user-visible change → **Task**\n7. Title starts with \"Add\", \"Support\", \"Implement\", \"New\", \"Introduce\"; or adds something that\n   doesn't exist yet → **Feature**\n\nWhen ambiguous between **Feature** and **Improvement**: does it add something that doesn't exist\nat all, or make something existing better? Former → Feature, latter → Improvement.\n\nWhen ambiguous between **Task** and **Improvement**: is there a user-visible benefit (better\nperformance, reliability, DX, API ergonomics)? If yes → Improvement. If it's purely internal\nwith no user-visible impact → Task.\n\nAssign exactly one Type label. Mark confidence:\n- **High** — clear signal in title or description\n- **Low** — genuinely ambiguous; flag for human review, don't guess\n\n### Step 5 — Present the plan\n\nShow a summary table before writing anything:\n\n```\n| Issue   | Title                  | Proposed Type | Confidence          |\n|---------|------------------------|---------------|---------------------|\n| SDK-123 | Fix crash on startup   | Bug           | High                |\n| SDK-456 | Add OAuth support      | Feature       | High                |\n| SDK-789 | Some vague title       | Task          | Low — please review |\n```\n\nAsk: *\"Should I apply these labels? Reply with any corrections (e.g. 'SDK-789 → Bug') and I'll\nupdate the plan before applying.\"*\n\nIf the user provides corrections, update the table and show the revised plan before proceeding.\n\n### Step 6 — Apply labels\n\nFor each approved classification:\n\n1. Call `get_issue` to fetch the issue's **current** label IDs immediately before writing\n2. Append the Type label UUID from the Step 2 map\n3. Call `save_issue` with the full combined label set\n\n> **Always re-fetch and always pass the full combined set.** Linear replaces labels on\n> update — labels added between Step 3 and now would be silently stripped if you use\n> the cached label list.\n\nReport as you go: \"SDK-123 → Bug\", \"SDK-456 → Feature\".\n\n## Edge Cases\n\n- **Issue already has a Type label:** Skip it; don't overwrite human classifications.\n- **Very short title, no description:** Flag as low-confidence; surface for human review.\n- **Issue belongs to multiple types:** Pick the primary type (bug fix with a docs update → Bug).\n",{"data":36,"body":39},{"name":4,"description":6,"allowed-tools":37,"compatibility":38},"mcp__linear-server__query_data mcp__linear-server__get_issue mcp__linear-server__save_issue AskUserQuestion","Requires the Linear MCP server to be configured.",{"type":40,"children":41},"root",[42,50,64,71,87,93,98,238,244,251,256,275,293,303,318,324,337,349,354,360,370,402,407,413,439,522,538,553,558,581,587,592,601,612,617,623,628,667,681,686,692],{"type":43,"tag":44,"props":45,"children":46},"element","h1",{"id":4},[47],{"type":48,"value":49},"text","Linear Type Labeler",{"type":43,"tag":51,"props":52,"children":53},"p",{},[54,56,62],{"type":48,"value":55},"Classifies Linear issues and applies a ",{"type":43,"tag":57,"props":58,"children":59},"strong",{},[60],{"type":48,"value":61},"Type",{"type":48,"value":63}," label from the Sentry workspace's label\ntaxonomy based on the content of each issue's title and description.",{"type":43,"tag":65,"props":66,"children":68},"h2",{"id":67},"requirements",[69],{"type":48,"value":70},"Requirements",{"type":43,"tag":51,"props":72,"children":73},{},[74,76,85],{"type":48,"value":75},"This skill requires the ",{"type":43,"tag":77,"props":78,"children":82},"a",{"href":79,"rel":80},"https:\u002F\u002Fgithub.com\u002Flinear\u002Flinear-mcp",[81],"nofollow",[83],{"type":48,"value":84},"Linear MCP server",{"type":48,"value":86}," to be configured.",{"type":43,"tag":65,"props":88,"children":90},{"id":89},"type-label-reference",[91],{"type":48,"value":92},"Type Label Reference",{"type":43,"tag":51,"props":94,"children":95},{},[96],{"type":48,"value":97},"Type labels in the Sentry workspace (workspace-level, not per-team):",{"type":43,"tag":99,"props":100,"children":101},"table",{},[102,121],{"type":43,"tag":103,"props":104,"children":105},"thead",{},[106],{"type":43,"tag":107,"props":108,"children":109},"tr",{},[110,116],{"type":43,"tag":111,"props":112,"children":113},"th",{},[114],{"type":48,"value":115},"Label",{"type":43,"tag":111,"props":117,"children":118},{},[119],{"type":48,"value":120},"When to use",{"type":43,"tag":122,"props":123,"children":124},"tbody",{},[125,142,158,174,190,206,222],{"type":43,"tag":107,"props":126,"children":127},{},[128,137],{"type":43,"tag":129,"props":130,"children":131},"td",{},[132],{"type":43,"tag":57,"props":133,"children":134},{},[135],{"type":48,"value":136},"Bug",{"type":43,"tag":129,"props":138,"children":139},{},[140],{"type":48,"value":141},"Something is broken, regression, error, crash, incorrect behavior",{"type":43,"tag":107,"props":143,"children":144},{},[145,153],{"type":43,"tag":129,"props":146,"children":147},{},[148],{"type":43,"tag":57,"props":149,"children":150},{},[151],{"type":48,"value":152},"Feature",{"type":43,"tag":129,"props":154,"children":155},{},[156],{"type":48,"value":157},"New capability, integration, API, SDK support — something that doesn't exist yet",{"type":43,"tag":107,"props":159,"children":160},{},[161,169],{"type":43,"tag":129,"props":162,"children":163},{},[164],{"type":43,"tag":57,"props":165,"children":166},{},[167],{"type":48,"value":168},"Improvement",{"type":43,"tag":129,"props":170,"children":171},{},[172],{"type":48,"value":173},"Making existing functionality better — performance, DX, UX, reliability",{"type":43,"tag":107,"props":175,"children":176},{},[177,185],{"type":43,"tag":129,"props":178,"children":179},{},[180],{"type":43,"tag":57,"props":181,"children":182},{},[183],{"type":48,"value":184},"Task",{"type":43,"tag":129,"props":186,"children":187},{},[188],{"type":48,"value":189},"Chore, investigation, spike, migration, cleanup, operational work",{"type":43,"tag":107,"props":191,"children":192},{},[193,201],{"type":43,"tag":129,"props":194,"children":195},{},[196],{"type":43,"tag":57,"props":197,"children":198},{},[199],{"type":48,"value":200},"Tracking Issue",{"type":43,"tag":129,"props":202,"children":203},{},[204],{"type":48,"value":205},"Parent\u002Fumbrella tracking a larger body of work; has sub-issues or a checklist",{"type":43,"tag":107,"props":207,"children":208},{},[209,217],{"type":43,"tag":129,"props":210,"children":211},{},[212],{"type":43,"tag":57,"props":213,"children":214},{},[215],{"type":48,"value":216},"Docs",{"type":43,"tag":129,"props":218,"children":219},{},[220],{"type":48,"value":221},"Documentation, RFC, write-up, changelog, guide",{"type":43,"tag":107,"props":223,"children":224},{},[225,233],{"type":43,"tag":129,"props":226,"children":227},{},[228],{"type":43,"tag":57,"props":229,"children":230},{},[231],{"type":48,"value":232},"Tests",{"type":43,"tag":129,"props":234,"children":235},{},[236],{"type":48,"value":237},"Writing or fixing tests, coverage, test infrastructure",{"type":43,"tag":65,"props":239,"children":241},{"id":240},"workflow",[242],{"type":48,"value":243},"Workflow",{"type":43,"tag":245,"props":246,"children":248},"h3",{"id":247},"step-1-identify-issues-to-process",[249],{"type":48,"value":250},"Step 1 — Identify issues to process",{"type":43,"tag":51,"props":252,"children":253},{},[254],{"type":48,"value":255},"Two modes:",{"type":43,"tag":51,"props":257,"children":258},{},[259,264,266,273],{"type":43,"tag":57,"props":260,"children":261},{},[262],{"type":48,"value":263},"A — List of Linear IDs provided",{"type":48,"value":265}," (e.g. ",{"type":43,"tag":267,"props":268,"children":270},"code",{"className":269},[],[271],{"type":48,"value":272},"SDK-123, SDK-456",{"type":48,"value":274},"):",{"type":43,"tag":276,"props":277,"children":278},"ul",{},[279],{"type":43,"tag":280,"props":281,"children":282},"li",{},[283,285,291],{"type":48,"value":284},"Fetch each issue by ID using ",{"type":43,"tag":267,"props":286,"children":288},{"className":287},[],[289],{"type":48,"value":290},"get_issue",{"type":48,"value":292},". Skip the team-fetch step entirely.",{"type":43,"tag":51,"props":294,"children":295},{},[296,301],{"type":43,"tag":57,"props":297,"children":298},{},[299],{"type":48,"value":300},"B — No IDs provided",{"type":48,"value":302},":",{"type":43,"tag":276,"props":304,"children":305},{},[306],{"type":43,"tag":280,"props":307,"children":308},{},[309,311,316],{"type":48,"value":310},"Infer the team: (1) current GitHub repository name — for the ",{"type":43,"tag":267,"props":312,"children":314},{"className":313},[],[315],{"type":48,"value":11},{"type":48,"value":317}," org, the repo name\nmatches the Linear team name, (2) explicitly stated by the user, (3) if still ambiguous, ask.",{"type":43,"tag":245,"props":319,"children":321},{"id":320},"step-2-fetch-label-ids",[322],{"type":48,"value":323},"Step 2 — Fetch label IDs",{"type":43,"tag":51,"props":325,"children":326},{},[327,329,335],{"type":48,"value":328},"Use ",{"type":43,"tag":267,"props":330,"children":332},{"className":331},[],[333],{"type":48,"value":334},"query_data",{"type":48,"value":336}," to fetch workspace-level labels and build a UUID map:",{"type":43,"tag":338,"props":339,"children":343},"pre",{"className":340,"code":342,"language":48},[341],"language-text","query_data: fetch all labels for the workspace (not the team)\n→ filter to those whose parent label name is \"Type\"\n→ build a map: { \"Bug\": \"\u003Cuuid>\", \"Feature\": \"\u003Cuuid>\", ... }\n",[344],{"type":43,"tag":267,"props":345,"children":347},{"__ignoreMap":346},"",[348],{"type":48,"value":342},{"type":43,"tag":51,"props":350,"children":351},{},[352],{"type":48,"value":353},"If the workspace has no \"Type\" label group, surface that to the user before proceeding.",{"type":43,"tag":245,"props":355,"children":357},{"id":356},"step-3-fetch-and-filter-issues",[358],{"type":48,"value":359},"Step 3 — Fetch and filter issues",{"type":43,"tag":51,"props":361,"children":362},{},[363,368],{"type":43,"tag":57,"props":364,"children":365},{},[366],{"type":48,"value":367},"If in mode A (list of IDs):",{"type":48,"value":369}," use the already-fetched issues from Step 1. Filter client-side:\nkeep only those where none of the issue's label IDs appear in the Step 2 UUID map values.",{"type":43,"tag":51,"props":371,"children":372},{},[373,378,380,385,387,392,394,400],{"type":43,"tag":57,"props":374,"children":375},{},[376],{"type":48,"value":377},"If in mode B (team):",{"type":48,"value":379}," use ",{"type":43,"tag":267,"props":381,"children":383},{"className":382},[],[384],{"type":48,"value":334},{"type":48,"value":386}," to list issues for the team, ",{"type":43,"tag":57,"props":388,"children":389},{},[390],{"type":48,"value":391},"including each issue's\nlabel IDs",{"type":48,"value":393},". Paginate (limit 50, use ",{"type":43,"tag":267,"props":395,"children":397},{"className":396},[],[398],{"type":48,"value":399},"cursor",{"type":48,"value":401},") until done. Filter client-side: keep only issues\nwhere none of the issue's label IDs appear in the Step 2 UUID map values (i.e., no Type label\nassigned yet).",{"type":43,"tag":51,"props":403,"children":404},{},[405],{"type":48,"value":406},"Announce the total candidate count before continuing. If there are more than 25 candidates,\nprocess in chunks of 25, confirming each chunk before the next.",{"type":43,"tag":245,"props":408,"children":410},{"id":409},"step-4-classify-each-issue",[411],{"type":48,"value":412},"Step 4 — Classify each issue",{"type":43,"tag":51,"props":414,"children":415},{},[416,418,423,425,430,432,437],{"type":48,"value":417},"For each candidate issue, read its ",{"type":43,"tag":57,"props":419,"children":420},{},[421],{"type":48,"value":422},"title",{"type":48,"value":424}," and ",{"type":43,"tag":57,"props":426,"children":427},{},[428],{"type":48,"value":429},"description",{"type":48,"value":431},". Apply heuristics in ",{"type":43,"tag":57,"props":433,"children":434},{},[435],{"type":48,"value":436},"priority\norder",{"type":48,"value":438}," — stop at the first match:",{"type":43,"tag":440,"props":441,"children":442},"ol",{},[443,452,461,486,495,504,513],{"type":43,"tag":280,"props":444,"children":445},{},[446,448],{"type":48,"value":447},"Title or description is clearly about testing work: mentions \"test\", \"tests\", \"coverage\",\n\"test infra\", \"test suite\", \"unit test\", \"integration test\" → ",{"type":43,"tag":57,"props":449,"children":450},{},[451],{"type":48,"value":232},{"type":43,"tag":280,"props":453,"children":454},{},[455,457],{"type":48,"value":456},"Title or description is clearly about documentation: mentions \"docs\", \"README\", \"changelog\",\n\"RFC\", \"spec\", \"guide\", \"write-up\", \"develop.sentry.dev\" → ",{"type":43,"tag":57,"props":458,"children":459},{},[460],{"type":48,"value":216},{"type":43,"tag":280,"props":462,"children":463},{},[464,466,472,474,480,482],{"type":48,"value":465},"Title contains ",{"type":43,"tag":267,"props":467,"children":469},{"className":468},[],[470],{"type":48,"value":471},"[META]",{"type":48,"value":473},", ",{"type":43,"tag":267,"props":475,"children":477},{"className":476},[],[478],{"type":48,"value":479},"[EPIC]",{"type":48,"value":481},", \"Track\", \"Tracking\"; or description has a checklist of\nLinear\u002FGitHub issue links → ",{"type":43,"tag":57,"props":483,"children":484},{},[485],{"type":48,"value":200},{"type":43,"tag":280,"props":487,"children":488},{},[489,491],{"type":48,"value":490},"Title starts with \"Fix\", \"Fixes\", \"Broken\", \"Error\", \"Crash\", \"Regression\" → ",{"type":43,"tag":57,"props":492,"children":493},{},[494],{"type":48,"value":136},{"type":43,"tag":280,"props":496,"children":497},{},[498,500],{"type":48,"value":499},"Title starts with \"Improve\", \"Optimize\", \"Enhance\"; or is a refactor with user-visible impact\n(changes behavior, performance, or API ergonomics) → ",{"type":43,"tag":57,"props":501,"children":502},{},[503],{"type":48,"value":168},{"type":43,"tag":280,"props":505,"children":506},{},[507,509],{"type":48,"value":508},"Title starts with \"Investigate\", \"Spike\", \"Migrate\", \"Update\", \"Clean up\", \"Chore\"; or is a\nrefactor with no user-visible change → ",{"type":43,"tag":57,"props":510,"children":511},{},[512],{"type":48,"value":184},{"type":43,"tag":280,"props":514,"children":515},{},[516,518],{"type":48,"value":517},"Title starts with \"Add\", \"Support\", \"Implement\", \"New\", \"Introduce\"; or adds something that\ndoesn't exist yet → ",{"type":43,"tag":57,"props":519,"children":520},{},[521],{"type":48,"value":152},{"type":43,"tag":51,"props":523,"children":524},{},[525,527,531,532,536],{"type":48,"value":526},"When ambiguous between ",{"type":43,"tag":57,"props":528,"children":529},{},[530],{"type":48,"value":152},{"type":48,"value":424},{"type":43,"tag":57,"props":533,"children":534},{},[535],{"type":48,"value":168},{"type":48,"value":537},": does it add something that doesn't exist\nat all, or make something existing better? Former → Feature, latter → Improvement.",{"type":43,"tag":51,"props":539,"children":540},{},[541,542,546,547,551],{"type":48,"value":526},{"type":43,"tag":57,"props":543,"children":544},{},[545],{"type":48,"value":184},{"type":48,"value":424},{"type":43,"tag":57,"props":548,"children":549},{},[550],{"type":48,"value":168},{"type":48,"value":552},": is there a user-visible benefit (better\nperformance, reliability, DX, API ergonomics)? If yes → Improvement. If it's purely internal\nwith no user-visible impact → Task.",{"type":43,"tag":51,"props":554,"children":555},{},[556],{"type":48,"value":557},"Assign exactly one Type label. Mark confidence:",{"type":43,"tag":276,"props":559,"children":560},{},[561,571],{"type":43,"tag":280,"props":562,"children":563},{},[564,569],{"type":43,"tag":57,"props":565,"children":566},{},[567],{"type":48,"value":568},"High",{"type":48,"value":570}," — clear signal in title or description",{"type":43,"tag":280,"props":572,"children":573},{},[574,579],{"type":43,"tag":57,"props":575,"children":576},{},[577],{"type":48,"value":578},"Low",{"type":48,"value":580}," — genuinely ambiguous; flag for human review, don't guess",{"type":43,"tag":245,"props":582,"children":584},{"id":583},"step-5-present-the-plan",[585],{"type":48,"value":586},"Step 5 — Present the plan",{"type":43,"tag":51,"props":588,"children":589},{},[590],{"type":48,"value":591},"Show a summary table before writing anything:",{"type":43,"tag":338,"props":593,"children":596},{"className":594,"code":595,"language":48},[341],"| Issue   | Title                  | Proposed Type | Confidence          |\n|---------|------------------------|---------------|---------------------|\n| SDK-123 | Fix crash on startup   | Bug           | High                |\n| SDK-456 | Add OAuth support      | Feature       | High                |\n| SDK-789 | Some vague title       | Task          | Low — please review |\n",[597],{"type":43,"tag":267,"props":598,"children":599},{"__ignoreMap":346},[600],{"type":48,"value":595},{"type":43,"tag":51,"props":602,"children":603},{},[604,606],{"type":48,"value":605},"Ask: ",{"type":43,"tag":607,"props":608,"children":609},"em",{},[610],{"type":48,"value":611},"\"Should I apply these labels? Reply with any corrections (e.g. 'SDK-789 → Bug') and I'll\nupdate the plan before applying.\"",{"type":43,"tag":51,"props":613,"children":614},{},[615],{"type":48,"value":616},"If the user provides corrections, update the table and show the revised plan before proceeding.",{"type":43,"tag":245,"props":618,"children":620},{"id":619},"step-6-apply-labels",[621],{"type":48,"value":622},"Step 6 — Apply labels",{"type":43,"tag":51,"props":624,"children":625},{},[626],{"type":48,"value":627},"For each approved classification:",{"type":43,"tag":440,"props":629,"children":630},{},[631,650,655],{"type":43,"tag":280,"props":632,"children":633},{},[634,636,641,643,648],{"type":48,"value":635},"Call ",{"type":43,"tag":267,"props":637,"children":639},{"className":638},[],[640],{"type":48,"value":290},{"type":48,"value":642}," to fetch the issue's ",{"type":43,"tag":57,"props":644,"children":645},{},[646],{"type":48,"value":647},"current",{"type":48,"value":649}," label IDs immediately before writing",{"type":43,"tag":280,"props":651,"children":652},{},[653],{"type":48,"value":654},"Append the Type label UUID from the Step 2 map",{"type":43,"tag":280,"props":656,"children":657},{},[658,659,665],{"type":48,"value":635},{"type":43,"tag":267,"props":660,"children":662},{"className":661},[],[663],{"type":48,"value":664},"save_issue",{"type":48,"value":666}," with the full combined label set",{"type":43,"tag":668,"props":669,"children":670},"blockquote",{},[671],{"type":43,"tag":51,"props":672,"children":673},{},[674,679],{"type":43,"tag":57,"props":675,"children":676},{},[677],{"type":48,"value":678},"Always re-fetch and always pass the full combined set.",{"type":48,"value":680}," Linear replaces labels on\nupdate — labels added between Step 3 and now would be silently stripped if you use\nthe cached label list.",{"type":43,"tag":51,"props":682,"children":683},{},[684],{"type":48,"value":685},"Report as you go: \"SDK-123 → Bug\", \"SDK-456 → Feature\".",{"type":43,"tag":65,"props":687,"children":689},{"id":688},"edge-cases",[690],{"type":48,"value":691},"Edge Cases",{"type":43,"tag":276,"props":693,"children":694},{},[695,705,715],{"type":43,"tag":280,"props":696,"children":697},{},[698,703],{"type":43,"tag":57,"props":699,"children":700},{},[701],{"type":48,"value":702},"Issue already has a Type label:",{"type":48,"value":704}," Skip it; don't overwrite human classifications.",{"type":43,"tag":280,"props":706,"children":707},{},[708,713],{"type":43,"tag":57,"props":709,"children":710},{},[711],{"type":48,"value":712},"Very short title, no description:",{"type":48,"value":714}," Flag as low-confidence; surface for human review.",{"type":43,"tag":280,"props":716,"children":717},{},[718,723],{"type":43,"tag":57,"props":719,"children":720},{},[721],{"type":48,"value":722},"Issue belongs to multiple types:",{"type":48,"value":724}," Pick the primary type (bug fix with a docs update → Bug).",{"items":726,"total":904},[727,752,766,781,795,812,828,842,852,863,873,891],{"slug":728,"name":728,"fn":729,"description":730,"org":731,"tags":732,"stars":749,"repoUrl":750,"updatedAt":751},"xcodebuildmcp","build and test Apple apps with XcodeBuildMCP","Official skill for XcodeBuildMCP. Use when doing iOS\u002FmacOS\u002FwatchOS\u002FtvOS\u002FvisionOS work (build, test, run, debug, log, UI automation).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[733,736,739,742,743,746],{"name":734,"slug":735,"type":16},"Debugging","debugging",{"name":737,"slug":738,"type":16},"iOS","ios",{"name":740,"slug":741,"type":16},"macOS","macos",{"name":9,"slug":8,"type":16},{"name":744,"slug":745,"type":16},"Testing","testing",{"name":747,"slug":748,"type":16},"Xcode","xcode",6176,"https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP","2026-04-06T18:13:34.8719",{"slug":753,"name":753,"fn":754,"description":755,"org":756,"tags":757,"stars":749,"repoUrl":750,"updatedAt":765},"xcodebuildmcp-cli","build and test Apple apps via CLI","Official skill for the XcodeBuildMCP CLI. Use when doing iOS\u002FmacOS\u002FwatchOS\u002FtvOS\u002FvisionOS work (build, test, run, debug, log, UI automation).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[758,761,762,763,764],{"name":759,"slug":760,"type":16},"CLI","cli",{"name":737,"slug":738,"type":16},{"name":740,"slug":741,"type":16},{"name":744,"slug":745,"type":16},{"name":747,"slug":748,"type":16},"2026-04-06T18:13:36.13414",{"slug":767,"name":767,"fn":768,"description":769,"org":770,"tags":771,"stars":778,"repoUrl":779,"updatedAt":780},"agents-md","maintain project instruction files","Creates and maintains concise AGENTS.md and CLAUDE.md project instruction files. Use when asked to create AGENTS.md, update AGENTS.md, maintain agent docs, set up CLAUDE.md, document repository agent conventions, or keep coding-agent instructions minimal and reference-backed.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[772,775],{"name":773,"slug":774,"type":16},"Documentation","documentation",{"name":776,"slug":777,"type":16},"Engineering","engineering",861,"https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fskills","2026-05-15T06:16:29.695991",{"slug":782,"name":782,"fn":783,"description":784,"org":785,"tags":786,"stars":778,"repoUrl":779,"updatedAt":794},"blog-writing-guide","write and review engineering blog posts","Write, review, and improve blog posts for the Sentry engineering blog following Sentry's specific writing standards, voice, and quality bar. Use this skill whenever someone asks to write a blog post, draft a technical article, review blog content, improve a draft, write a product announcement, create an engineering deep-dive, or produce any written content destined for the Sentry blog or developer audience. Also trigger when the user mentions \"blog post,\" \"blog draft,\" \"write-up,\" \"announcement post,\" \"engineering post,\" \"deep dive,\" \"postmortem,\" or asks for help with technical writing for Sentry. Even if the user just says \"help me write about [feature\u002Ftopic]\" — if it sounds like it could become a Sentry blog post, use this skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[787,790,791],{"name":788,"slug":789,"type":16},"Communications","communications",{"name":9,"slug":8,"type":16},{"name":792,"slug":793,"type":16},"Technical Writing","technical-writing","2026-05-15T06:16:33.38217",{"slug":796,"name":796,"fn":797,"description":798,"org":799,"tags":800,"stars":778,"repoUrl":779,"updatedAt":811},"brand-guidelines","write copy following Sentry brand guidelines","Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Sentry Voice tones.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[801,804,807,808],{"name":802,"slug":803,"type":16},"Branding","branding",{"name":805,"slug":806,"type":16},"Content Creation","content-creation",{"name":9,"slug":8,"type":16},{"name":809,"slug":810,"type":16},"UX Copy","ux-copy","2026-05-15T06:16:22.395707",{"slug":813,"name":813,"fn":814,"description":815,"org":816,"tags":817,"stars":778,"repoUrl":779,"updatedAt":827},"claude-settings-audit","generate Claude Code settings permissions","Analyze a repository to generate recommended Claude Code settings.json permissions. Use when setting up a new project, auditing existing settings, or determining which read-only bash commands to allow. Detects tech stack, build tools, and monorepo structure.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[818,821,824],{"name":819,"slug":820,"type":16},"Claude Code","claude-code",{"name":822,"slug":823,"type":16},"Configuration","configuration",{"name":825,"slug":826,"type":16},"Security","security","2026-05-15T06:16:44.335977",{"slug":829,"name":829,"fn":830,"description":831,"org":832,"tags":833,"stars":778,"repoUrl":779,"updatedAt":841},"code-review","perform code reviews for Sentry projects","Perform code reviews following Sentry engineering practices. Use when reviewing pull requests, examining code changes, or providing feedback on code quality. Covers security, performance, testing, and design review.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[834,836,837,840],{"name":835,"slug":829,"type":16},"Code Review",{"name":776,"slug":777,"type":16},{"name":838,"slug":839,"type":16},"Performance","performance",{"name":825,"slug":826,"type":16},"2026-05-15T06:16:35.824864",{"slug":843,"name":843,"fn":844,"description":845,"org":846,"tags":847,"stars":778,"repoUrl":779,"updatedAt":851},"code-simplifier","simplify and refine source code","Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to \"simplify code\", \"clean up code\", \"refactor for clarity\", \"improve readability\", or review recently modified code for elegance. Focuses on project-specific best practices.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[848],{"name":849,"slug":850,"type":16},"Code Analysis","code-analysis","2026-05-15T06:16:32.127981",{"slug":853,"name":853,"fn":854,"description":855,"org":856,"tags":857,"stars":778,"repoUrl":779,"updatedAt":862},"commit","create commits with Sentry conventions","Use for every request to commit changes or draft a commit message. Creates Sentry-style conventional commits with issue references.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[858,861],{"name":859,"slug":860,"type":16},"Git","git",{"name":9,"slug":8,"type":16},"2026-07-18T05:15:10.723937",{"slug":864,"name":864,"fn":865,"description":866,"org":867,"tags":868,"stars":778,"repoUrl":779,"updatedAt":872},"create-branch","create git branches for Sentry workflows","Create a git branch following Sentry naming conventions. Use when asked to \"create a branch\", \"new branch\", \"start a branch\", \"make a branch\", \"switch to a new branch\", or when starting new work on the default branch.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[869,870,871],{"name":776,"slug":777,"type":16},{"name":859,"slug":860,"type":16},{"name":9,"slug":8,"type":16},"2026-05-15T06:16:39.458431",{"slug":874,"name":874,"fn":875,"description":876,"org":877,"tags":878,"stars":778,"repoUrl":779,"updatedAt":890},"django-access-review","review Django access control and IDOR","Django access control and IDOR security review. Use when reviewing Django views, DRF viewsets, ORM queries, or any Python\u002FDjango code handling user authorization. Trigger keywords: \"IDOR\", \"access control\", \"authorization\", \"Django permissions\", \"object permissions\", \"tenant isolation\", \"broken access\".",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[879,882,883,886,889],{"name":880,"slug":881,"type":16},"Access Control","access-control",{"name":849,"slug":850,"type":16},{"name":884,"slug":885,"type":16},"Django","django",{"name":887,"slug":888,"type":16},"Python","python",{"name":825,"slug":826,"type":16},"2026-05-15T06:16:43.098698",{"slug":892,"name":892,"fn":893,"description":894,"org":895,"tags":896,"stars":778,"repoUrl":779,"updatedAt":903},"django-perf-review","review and optimize Django performance","Django performance code review. Use when asked to \"review Django performance\", \"find N+1 queries\", \"optimize Django\", \"check queryset performance\", \"database performance\", \"Django ORM issues\", or audit Django code for performance problems.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[897,898,901,902],{"name":835,"slug":829,"type":16},{"name":899,"slug":900,"type":16},"Database","database",{"name":884,"slug":885,"type":16},{"name":838,"slug":839,"type":16},"2026-05-15T06:16:24.832813",88,{"items":906,"total":1000},[907,920,933,948,964,971,984],{"slug":908,"name":908,"fn":909,"description":910,"org":911,"tags":912,"stars":24,"repoUrl":25,"updatedAt":919},"contributing-md","generate standardized CONTRIBUTING.md files","Generate or align a CONTRIBUTING.md for a Sentry SDK repository with the develop.sentry.dev standard template. Use when asked to \"create contributing.md\", \"update contributing.md\", \"align contributing docs\", \"standardize contributor docs\", or when the contributing guide is outdated, missing sections, or does not exist.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[913,914,917,918],{"name":773,"slug":774,"type":16},{"name":915,"slug":916,"type":16},"GitHub","github",{"name":9,"slug":8,"type":16},{"name":792,"slug":793,"type":16},"2026-04-06T18:14:57.157686",{"slug":921,"name":921,"fn":922,"description":923,"org":924,"tags":925,"stars":24,"repoUrl":25,"updatedAt":932},"daily-update","generate async daily standup updates","Generate a formatted async daily standup message for the Sentry SDK team channel. Use when asked to create a \"daily update\", \"async daily\", \"standup update\", or \"async team update\".",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[926,927,928,929],{"name":788,"slug":789,"type":16},{"name":18,"slug":19,"type":16},{"name":9,"slug":8,"type":16},{"name":930,"slug":931,"type":16},"Standup","standup","2026-04-06T18:14:53.472546",{"slug":934,"name":934,"fn":935,"description":936,"org":937,"tags":938,"stars":24,"repoUrl":25,"updatedAt":947},"linear-initiative","create Linear projects from initiatives","Creates Linear projects for SDK repositories based on a Linear initiative. Use when rolling out a feature across multiple SDKs, creating SDK projects from initiative, or setting up cross-SDK alignment work.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[939,940,943,946],{"name":14,"slug":15,"type":16},{"name":941,"slug":942,"type":16},"Product Management","product-management",{"name":944,"slug":945,"type":16},"SDK","sdk",{"name":9,"slug":8,"type":16},"2026-04-06T18:14:54.704594",{"slug":949,"name":949,"fn":950,"description":951,"org":952,"tags":953,"stars":24,"repoUrl":25,"updatedAt":963},"linear-sdk-telemetry-labeler","classify and label Linear issues with telemetry data","Classify and apply SDK Telemetry labels to Linear issues based on their title and description. Use when triaging issues related to SDK telemetry signals: errors, traces, spans, profiles, replays, logs, metrics, cron checks, client reports, user feedbacks, or attachments. Triggers: \"sdk telemetry label\", \"telemetry labeler\", \"label telemetry issues\", \"tag telemetry\".\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[954,957,960,961,962],{"name":955,"slug":956,"type":16},"Linear","linear",{"name":958,"slug":959,"type":16},"Observability","observability",{"name":944,"slug":945,"type":16},{"name":9,"slug":8,"type":16},{"name":21,"slug":22,"type":16},"2026-04-06T18:15:00.931727",{"slug":4,"name":4,"fn":5,"description":6,"org":965,"tags":966,"stars":24,"repoUrl":25,"updatedAt":26},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[967,968,969,970],{"name":14,"slug":15,"type":16},{"name":18,"slug":19,"type":16},{"name":9,"slug":8,"type":16},{"name":21,"slug":22,"type":16},{"slug":972,"name":972,"fn":973,"description":974,"org":975,"tags":976,"stars":24,"repoUrl":25,"updatedAt":983},"sdk-feature-implementation","implement features across Sentry SDKs","Implement a feature across Sentry SDK repositories by spawning parallel agents. Use when you have Linear initiatives\u002Fprojects\u002Fissues and want to create draft PRs. Triggers on \"implement across SDKs\", \"spawn SDK agents\", \"SDK implementation\", \"parallel SDK implementation\", \"continue SDK rollout\".",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[977,978,981,982],{"name":14,"slug":15,"type":16},{"name":979,"slug":980,"type":16},"Pull Requests","pull-requests",{"name":944,"slug":945,"type":16},{"name":9,"slug":8,"type":16},"2026-04-06T18:14:55.930879",{"slug":985,"name":985,"fn":986,"description":987,"org":988,"tags":989,"stars":24,"repoUrl":25,"updatedAt":999},"span-convention-review","review OTel tracing span changes","Review OpenTelemetry tracing span changes in SDK repositories for conformance to Sentry Conventions and OTel Semantic Conventions. Use when reviewing span instrumentation, \"review spans\", \"check span conventions\", \"span review\", \"OTel span check\", \"tracing convention review\".",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[990,991,992,995,996],{"name":835,"slug":829,"type":16},{"name":958,"slug":959,"type":16},{"name":993,"slug":994,"type":16},"OpenTelemetry","opentelemetry",{"name":9,"slug":8,"type":16},{"name":997,"slug":998,"type":16},"Tracing","tracing","2026-04-06T18:14:59.655998",7]