
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.
SKILL.md
Contributing.md Skill
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.
Steps
1. Fetch the template
https://develop.sentry.dev/sdk/getting-started/templates/contributing-md-template/
This is the source of truth for required sections, structure, and links.
2. Read the existing file (if any)
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.
3. Find commands from the repo
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.iofor the SDK — setup steps if not found above
4. Reference good examples
Check 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
5. Write the file
- Follow the section order from the fetched template
- Append preserved SDK-specific sections after standard content
- Flag contradictions rather than removing:
<!-- TODO: review against standard: https://develop.sentry.dev/... --> - If file would exceed 200 lines, move verbose steps to a linked doc and reference it
6. Verify
Grep for \[ — no unreplaced placeholder tokens should remain.
Quality Checklist
- All
[placeholder]values replaced with real content - Commands verified against CI config or README
- Existing SDK-specific sections preserved
- Non-standard content flagged with TODO comments
- AI attribution section present
- File is 100–200 lines
- No links point to Notion or Linear
More skills from the sdk-skills repository
View all 7 skillsdaily-update
generate async daily standup updates
Apr 6CommunicationsProductivitySentryStanduplinear-initiative
create Linear projects from initiatives
Apr 6OperationsProduct ManagementSDKSentrylinear-sdk-telemetry-labeler
classify and label Linear issues with telemetry data
Apr 6LinearObservabilitySDKSentry +1linear-type-labeler
classify and label Linear issues
Apr 6OperationsProductivitySentryTriagesdk-feature-implementation
implement features across Sentry SDKs
Apr 6OperationsPull RequestsSDKSentryspan-convention-review
review OTel tracing span changes
Apr 6Code ReviewObservabilityOpenTelemetrySentry +1
More from Sentry
View publisherxcodebuildmcp
build and test Apple apps with XcodeBuildMCP
XcodeBuildMCP
Apr 6DebuggingiOSmacOSSentry +2xcodebuildmcp-cli
build and test Apple apps via CLI
XcodeBuildMCP
Apr 6CLIiOSmacOSTesting +1agents-md
maintain project instruction files
skills
May 15DocumentationEngineeringblog-writing-guide
write and review engineering blog posts
skills
May 15CommunicationsSentryTechnical Writingbrand-guidelines
write copy following Sentry brand guidelines
skills
May 15BrandingContent CreationSentryUX Copyclaude-settings-audit
generate Claude Code settings permissions
skills
May 15Claude CodeConfigurationSecurity