[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-sentry-daily-update":3,"mdc-fv9k2d-key":35,"related-org-sentry-daily-update":296,"related-repo-sentry-daily-update":474},{"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},"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},"sentry","Sentry","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fsentry.png","getsentry",[13,17,20,21],{"name":14,"slug":15,"type":16},"Productivity","productivity","tag",{"name":18,"slug":19,"type":16},"Standup","standup",{"name":9,"slug":8,"type":16},{"name":22,"slug":23,"type":16},"Communications","communications",2,"https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fsdk-skills","2026-04-06T18:14:53.472546",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\u002Fdaily-update","---\nname: daily-update\ndescription: 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\".\n---\n\n# Async Daily Update\n\nGenerate a properly formatted async daily standup message for posting in the team Slack channel.\n\n## Step 1: Gather Information\n\nAsk the user for the following. Collect all answers before generating the message.\n\n**Required:**\n- What are you working on today? (list each task; ask if any have Linear issue links to include)\n\n**Optional — ask about each, only include in output if the user has something to report:**\n- Any blockers? (something preventing you from making progress)\n- Anything you need from a specific teammate? (who and what)\n- Any time OOO today? (if yes, ask for the time range and time zone)\n\n## Step 2: Generate the Message\n\nFormat the message exactly as follows:\n\n```\n🔄 YYYY-MM-DD\n\n- [task one]\n- [task two — add link if provided]\n- **Blocker:** [description]\n- **Needs:** [what you need — @mention the person directly]\n- **OOO:** [time range with time zone, e.g., 14:00–17:00 CET]\n```\n\n### Rules\n\n- Always start with the 🔄 emoji — this makes the update searchable in Slack\n- Use today's date in `YYYY-MM-DD` format\n- Leave a blank line between the date and the first bullet\n- Each task is a separate bullet point\n- If the user provides a Linear issue link, inline it after the task description: `Task description [SDK-123](https:\u002F\u002Flinear.app\u002F...)`\n- Only include **Blocker**, **Needs**, and **OOO** lines if the user has something to report — omit them entirely otherwise\n- For **Needs**, mention the specific person by name or @handle\n- For **OOO**, always include the time zone (e.g., CET, EST, PST)\n\n## Step 3: Output\n\nDisplay the final message as a plain code block so the user can copy and paste it directly into Slack.\n\nAfter the code block, remind the user: post this in your `#team-sdk-*` channel.\n\n## Examples\n\n**Minimal (no optional fields):**\n```\n🔄 2024-02-16\n\n- Finishing OTLP exporter implementation [SDK-234](https:\u002F\u002Flinear.app\u002Fteam\u002Fissue\u002FSDK-234)\n- Code review for Marco's span processor refactor [SDK-245](https:\u002F\u002Flinear.app\u002Fteam\u002Fissue\u002FSDK-245)\n```\n\n**With optional fields:**\n```\n🔄 2024-02-16\n\n- Wrapping up bugfixes in profiling integration and preparing release notes\n- Shifting focus to client reports implementation after bugfixes merge\n- **Blocker:** Need test credentials for staging environment to verify the span ingestion fix\n- **Needs:** API design review on error handling from @Sarah\n- **OOO:** 14:00–17:00 CET\n```\n",{"data":36,"body":37},{"name":4,"description":6},{"type":38,"children":39},"root",[40,49,55,62,67,76,86,94,112,118,123,136,143,232,238,243,256,262,270,279,287],{"type":41,"tag":42,"props":43,"children":45},"element","h1",{"id":44},"async-daily-update",[46],{"type":47,"value":48},"text","Async Daily Update",{"type":41,"tag":50,"props":51,"children":52},"p",{},[53],{"type":47,"value":54},"Generate a properly formatted async daily standup message for posting in the team Slack channel.",{"type":41,"tag":56,"props":57,"children":59},"h2",{"id":58},"step-1-gather-information",[60],{"type":47,"value":61},"Step 1: Gather Information",{"type":41,"tag":50,"props":63,"children":64},{},[65],{"type":47,"value":66},"Ask the user for the following. Collect all answers before generating the message.",{"type":41,"tag":50,"props":68,"children":69},{},[70],{"type":41,"tag":71,"props":72,"children":73},"strong",{},[74],{"type":47,"value":75},"Required:",{"type":41,"tag":77,"props":78,"children":79},"ul",{},[80],{"type":41,"tag":81,"props":82,"children":83},"li",{},[84],{"type":47,"value":85},"What are you working on today? (list each task; ask if any have Linear issue links to include)",{"type":41,"tag":50,"props":87,"children":88},{},[89],{"type":41,"tag":71,"props":90,"children":91},{},[92],{"type":47,"value":93},"Optional — ask about each, only include in output if the user has something to report:",{"type":41,"tag":77,"props":95,"children":96},{},[97,102,107],{"type":41,"tag":81,"props":98,"children":99},{},[100],{"type":47,"value":101},"Any blockers? (something preventing you from making progress)",{"type":41,"tag":81,"props":103,"children":104},{},[105],{"type":47,"value":106},"Anything you need from a specific teammate? (who and what)",{"type":41,"tag":81,"props":108,"children":109},{},[110],{"type":47,"value":111},"Any time OOO today? (if yes, ask for the time range and time zone)",{"type":41,"tag":56,"props":113,"children":115},{"id":114},"step-2-generate-the-message",[116],{"type":47,"value":117},"Step 2: Generate the Message",{"type":41,"tag":50,"props":119,"children":120},{},[121],{"type":47,"value":122},"Format the message exactly as follows:",{"type":41,"tag":124,"props":125,"children":129},"pre",{"className":126,"code":128,"language":47},[127],"language-text","🔄 YYYY-MM-DD\n\n- [task one]\n- [task two — add link if provided]\n- **Blocker:** [description]\n- **Needs:** [what you need — @mention the person directly]\n- **OOO:** [time range with time zone, e.g., 14:00–17:00 CET]\n",[130],{"type":41,"tag":131,"props":132,"children":134},"code",{"__ignoreMap":133},"",[135],{"type":47,"value":128},{"type":41,"tag":137,"props":138,"children":140},"h3",{"id":139},"rules",[141],{"type":47,"value":142},"Rules",{"type":41,"tag":77,"props":144,"children":145},{},[146,151,164,169,174,185,211,222],{"type":41,"tag":81,"props":147,"children":148},{},[149],{"type":47,"value":150},"Always start with the 🔄 emoji — this makes the update searchable in Slack",{"type":41,"tag":81,"props":152,"children":153},{},[154,156,162],{"type":47,"value":155},"Use today's date in ",{"type":41,"tag":131,"props":157,"children":159},{"className":158},[],[160],{"type":47,"value":161},"YYYY-MM-DD",{"type":47,"value":163}," format",{"type":41,"tag":81,"props":165,"children":166},{},[167],{"type":47,"value":168},"Leave a blank line between the date and the first bullet",{"type":41,"tag":81,"props":170,"children":171},{},[172],{"type":47,"value":173},"Each task is a separate bullet point",{"type":41,"tag":81,"props":175,"children":176},{},[177,179],{"type":47,"value":178},"If the user provides a Linear issue link, inline it after the task description: ",{"type":41,"tag":131,"props":180,"children":182},{"className":181},[],[183],{"type":47,"value":184},"Task description [SDK-123](https:\u002F\u002Flinear.app\u002F...)",{"type":41,"tag":81,"props":186,"children":187},{},[188,190,195,197,202,204,209],{"type":47,"value":189},"Only include ",{"type":41,"tag":71,"props":191,"children":192},{},[193],{"type":47,"value":194},"Blocker",{"type":47,"value":196},", ",{"type":41,"tag":71,"props":198,"children":199},{},[200],{"type":47,"value":201},"Needs",{"type":47,"value":203},", and ",{"type":41,"tag":71,"props":205,"children":206},{},[207],{"type":47,"value":208},"OOO",{"type":47,"value":210}," lines if the user has something to report — omit them entirely otherwise",{"type":41,"tag":81,"props":212,"children":213},{},[214,216,220],{"type":47,"value":215},"For ",{"type":41,"tag":71,"props":217,"children":218},{},[219],{"type":47,"value":201},{"type":47,"value":221},", mention the specific person by name or @handle",{"type":41,"tag":81,"props":223,"children":224},{},[225,226,230],{"type":47,"value":215},{"type":41,"tag":71,"props":227,"children":228},{},[229],{"type":47,"value":208},{"type":47,"value":231},", always include the time zone (e.g., CET, EST, PST)",{"type":41,"tag":56,"props":233,"children":235},{"id":234},"step-3-output",[236],{"type":47,"value":237},"Step 3: Output",{"type":41,"tag":50,"props":239,"children":240},{},[241],{"type":47,"value":242},"Display the final message as a plain code block so the user can copy and paste it directly into Slack.",{"type":41,"tag":50,"props":244,"children":245},{},[246,248,254],{"type":47,"value":247},"After the code block, remind the user: post this in your ",{"type":41,"tag":131,"props":249,"children":251},{"className":250},[],[252],{"type":47,"value":253},"#team-sdk-*",{"type":47,"value":255}," channel.",{"type":41,"tag":56,"props":257,"children":259},{"id":258},"examples",[260],{"type":47,"value":261},"Examples",{"type":41,"tag":50,"props":263,"children":264},{},[265],{"type":41,"tag":71,"props":266,"children":267},{},[268],{"type":47,"value":269},"Minimal (no optional fields):",{"type":41,"tag":124,"props":271,"children":274},{"className":272,"code":273,"language":47},[127],"🔄 2024-02-16\n\n- Finishing OTLP exporter implementation [SDK-234](https:\u002F\u002Flinear.app\u002Fteam\u002Fissue\u002FSDK-234)\n- Code review for Marco's span processor refactor [SDK-245](https:\u002F\u002Flinear.app\u002Fteam\u002Fissue\u002FSDK-245)\n",[275],{"type":41,"tag":131,"props":276,"children":277},{"__ignoreMap":133},[278],{"type":47,"value":273},{"type":41,"tag":50,"props":280,"children":281},{},[282],{"type":41,"tag":71,"props":283,"children":284},{},[285],{"type":47,"value":286},"With optional fields:",{"type":41,"tag":124,"props":288,"children":291},{"className":289,"code":290,"language":47},[127],"🔄 2024-02-16\n\n- Wrapping up bugfixes in profiling integration and preparing release notes\n- Shifting focus to client reports implementation after bugfixes merge\n- **Blocker:** Need test credentials for staging environment to verify the span ingestion fix\n- **Needs:** API design review on error handling from @Sarah\n- **OOO:** 14:00–17:00 CET\n",[292],{"type":41,"tag":131,"props":293,"children":294},{"__ignoreMap":133},[295],{"type":47,"value":290},{"items":297,"total":473},[298,323,337,352,364,381,397,411,421,432,442,460],{"slug":299,"name":299,"fn":300,"description":301,"org":302,"tags":303,"stars":320,"repoUrl":321,"updatedAt":322},"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},[304,307,310,313,314,317],{"name":305,"slug":306,"type":16},"Debugging","debugging",{"name":308,"slug":309,"type":16},"iOS","ios",{"name":311,"slug":312,"type":16},"macOS","macos",{"name":9,"slug":8,"type":16},{"name":315,"slug":316,"type":16},"Testing","testing",{"name":318,"slug":319,"type":16},"Xcode","xcode",6176,"https:\u002F\u002Fgithub.com\u002Fgetsentry\u002FXcodeBuildMCP","2026-04-06T18:13:34.8719",{"slug":324,"name":324,"fn":325,"description":326,"org":327,"tags":328,"stars":320,"repoUrl":321,"updatedAt":336},"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},[329,332,333,334,335],{"name":330,"slug":331,"type":16},"CLI","cli",{"name":308,"slug":309,"type":16},{"name":311,"slug":312,"type":16},{"name":315,"slug":316,"type":16},{"name":318,"slug":319,"type":16},"2026-04-06T18:13:36.13414",{"slug":338,"name":338,"fn":339,"description":340,"org":341,"tags":342,"stars":349,"repoUrl":350,"updatedAt":351},"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},[343,346],{"name":344,"slug":345,"type":16},"Documentation","documentation",{"name":347,"slug":348,"type":16},"Engineering","engineering",861,"https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fskills","2026-05-15T06:16:29.695991",{"slug":353,"name":353,"fn":354,"description":355,"org":356,"tags":357,"stars":349,"repoUrl":350,"updatedAt":363},"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},[358,359,360],{"name":22,"slug":23,"type":16},{"name":9,"slug":8,"type":16},{"name":361,"slug":362,"type":16},"Technical Writing","technical-writing","2026-05-15T06:16:33.38217",{"slug":365,"name":365,"fn":366,"description":367,"org":368,"tags":369,"stars":349,"repoUrl":350,"updatedAt":380},"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},[370,373,376,377],{"name":371,"slug":372,"type":16},"Branding","branding",{"name":374,"slug":375,"type":16},"Content Creation","content-creation",{"name":9,"slug":8,"type":16},{"name":378,"slug":379,"type":16},"UX Copy","ux-copy","2026-05-15T06:16:22.395707",{"slug":382,"name":382,"fn":383,"description":384,"org":385,"tags":386,"stars":349,"repoUrl":350,"updatedAt":396},"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},[387,390,393],{"name":388,"slug":389,"type":16},"Claude Code","claude-code",{"name":391,"slug":392,"type":16},"Configuration","configuration",{"name":394,"slug":395,"type":16},"Security","security","2026-05-15T06:16:44.335977",{"slug":398,"name":398,"fn":399,"description":400,"org":401,"tags":402,"stars":349,"repoUrl":350,"updatedAt":410},"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},[403,405,406,409],{"name":404,"slug":398,"type":16},"Code Review",{"name":347,"slug":348,"type":16},{"name":407,"slug":408,"type":16},"Performance","performance",{"name":394,"slug":395,"type":16},"2026-05-15T06:16:35.824864",{"slug":412,"name":412,"fn":413,"description":414,"org":415,"tags":416,"stars":349,"repoUrl":350,"updatedAt":420},"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},[417],{"name":418,"slug":419,"type":16},"Code Analysis","code-analysis","2026-05-15T06:16:32.127981",{"slug":422,"name":422,"fn":423,"description":424,"org":425,"tags":426,"stars":349,"repoUrl":350,"updatedAt":431},"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},[427,430],{"name":428,"slug":429,"type":16},"Git","git",{"name":9,"slug":8,"type":16},"2026-07-18T05:15:10.723937",{"slug":433,"name":433,"fn":434,"description":435,"org":436,"tags":437,"stars":349,"repoUrl":350,"updatedAt":441},"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},[438,439,440],{"name":347,"slug":348,"type":16},{"name":428,"slug":429,"type":16},{"name":9,"slug":8,"type":16},"2026-05-15T06:16:39.458431",{"slug":443,"name":443,"fn":444,"description":445,"org":446,"tags":447,"stars":349,"repoUrl":350,"updatedAt":459},"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},[448,451,452,455,458],{"name":449,"slug":450,"type":16},"Access Control","access-control",{"name":418,"slug":419,"type":16},{"name":453,"slug":454,"type":16},"Django","django",{"name":456,"slug":457,"type":16},"Python","python",{"name":394,"slug":395,"type":16},"2026-05-15T06:16:43.098698",{"slug":461,"name":461,"fn":462,"description":463,"org":464,"tags":465,"stars":349,"repoUrl":350,"updatedAt":472},"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},[466,467,470,471],{"name":404,"slug":398,"type":16},{"name":468,"slug":469,"type":16},"Database","database",{"name":453,"slug":454,"type":16},{"name":407,"slug":408,"type":16},"2026-05-15T06:16:24.832813",88,{"items":475,"total":571},[476,489,496,513,531,542,555],{"slug":477,"name":477,"fn":478,"description":479,"org":480,"tags":481,"stars":24,"repoUrl":25,"updatedAt":488},"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},[482,483,486,487],{"name":344,"slug":345,"type":16},{"name":484,"slug":485,"type":16},"GitHub","github",{"name":9,"slug":8,"type":16},{"name":361,"slug":362,"type":16},"2026-04-06T18:14:57.157686",{"slug":4,"name":4,"fn":5,"description":6,"org":490,"tags":491,"stars":24,"repoUrl":25,"updatedAt":26},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[492,493,494,495],{"name":22,"slug":23,"type":16},{"name":14,"slug":15,"type":16},{"name":9,"slug":8,"type":16},{"name":18,"slug":19,"type":16},{"slug":497,"name":497,"fn":498,"description":499,"org":500,"tags":501,"stars":24,"repoUrl":25,"updatedAt":512},"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},[502,505,508,511],{"name":503,"slug":504,"type":16},"Operations","operations",{"name":506,"slug":507,"type":16},"Product Management","product-management",{"name":509,"slug":510,"type":16},"SDK","sdk",{"name":9,"slug":8,"type":16},"2026-04-06T18:14:54.704594",{"slug":514,"name":514,"fn":515,"description":516,"org":517,"tags":518,"stars":24,"repoUrl":25,"updatedAt":530},"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},[519,522,525,526,527],{"name":520,"slug":521,"type":16},"Linear","linear",{"name":523,"slug":524,"type":16},"Observability","observability",{"name":509,"slug":510,"type":16},{"name":9,"slug":8,"type":16},{"name":528,"slug":529,"type":16},"Triage","triage","2026-04-06T18:15:00.931727",{"slug":532,"name":532,"fn":533,"description":534,"org":535,"tags":536,"stars":24,"repoUrl":25,"updatedAt":541},"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},[537,538,539,540],{"name":503,"slug":504,"type":16},{"name":14,"slug":15,"type":16},{"name":9,"slug":8,"type":16},{"name":528,"slug":529,"type":16},"2026-04-06T18:14:58.40989",{"slug":543,"name":543,"fn":544,"description":545,"org":546,"tags":547,"stars":24,"repoUrl":25,"updatedAt":554},"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},[548,549,552,553],{"name":503,"slug":504,"type":16},{"name":550,"slug":551,"type":16},"Pull Requests","pull-requests",{"name":509,"slug":510,"type":16},{"name":9,"slug":8,"type":16},"2026-04-06T18:14:55.930879",{"slug":556,"name":556,"fn":557,"description":558,"org":559,"tags":560,"stars":24,"repoUrl":25,"updatedAt":570},"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},[561,562,563,566,567],{"name":404,"slug":398,"type":16},{"name":523,"slug":524,"type":16},{"name":564,"slug":565,"type":16},"OpenTelemetry","opentelemetry",{"name":9,"slug":8,"type":16},{"name":568,"slug":569,"type":16},"Tracing","tracing","2026-04-06T18:14:59.655998",7]