// 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.
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.
Implement a feature across Sentry SDK repositories by spawning parallel agents. Use when you have Linear initiatives/projects/issues and want to create draft PRs. Triggers on "implement across SDKs", "spawn SDK agents", "SDK implementation", "parallel SDK implementation", "continue SDK rollout".
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".
Classify and apply Type labels to Linear issues based on their title and description.
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".
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".
| name | contributing-md |
| description | 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. |
Generate or align a Sentry SDK repository's CONTRIBUTING.md with the
standard template.
Spec compliance is the primary goal; SDK-specific content is preserved or added around it.
Target 100–200 lines — detailed process lives on develop.sentry.dev, link there, don't duplicate.
https://develop.sentry.dev/sdk/getting-started/templates/contributing-md-template/
This is the source of truth for required sections, structure, and links.
If CONTRIBUTING.md exists, read it. Commands and SDK-specific content already there
should be trusted. If it does not exist, use the fetched template as the starting point.
For missing or placeholder values, read in priority order:
.github/workflows/*.yml — authoritative test/lint/build commandsMakefile / Taskfile.yml / tox.ini — command wrappersREADME.md — install command, SDK namedocs.sentry.io for the SDK — setup steps if not found aboveCheck these repos for structural inspiration if needed:
sentry-python — integration principles, user vs contributor setupsentry-javascript — Volta pin, monorepo workflow, draft PR rulesentry-go — LOGAF usage, craft release-notes requirementsentry-cocoa — LOGAF with descriptions, copyright header rulesentry-java — API compatibility workflow, step-by-step setup<!-- TODO: review against standard: https://develop.sentry.dev/... -->
Grep for \[ — no unreplaced placeholder tokens should remain.
[placeholder] values replaced with real content