sdk-feature-implementation
SDK Feature Implementation
Implement a feature across Sentry SDK repositories by spawning parallel agents that create draft PRs.
Repo Access
Only operate on repos listed in SDK_REPOS.md. Only repos with Enabled=Yes are included by default. All repos are under the getsentry GitHub org.
Use gh CLI for all GitHub operations (PRs, branches, CI logs). Use Linear MCP for all context gathering and tracking.
Instructions
Step 1: Gather Context
Linear MCP is the primary source for all context gathering. The user needs to provide enough context to know what to implement and where. Accept any of these starting points:
- Linear initiative (ideal) — fetch with
mcp__linear-server__get_initiativeto get the overview, then drill into projects/issues per SDK team - Linear project or issue — extract spec, reference PRs, and target repo from the description
- Spec URL + target repos — user provides directly
More from getsentry/sdk-skills
daily-update
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".
4linear-type-labeler
>
4linear-initiative
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.
4span-convention-review
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".
4linear-sdk-telemetry-labeler
>
4contributing-md
>
3