contributing-md

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.

npx skills add https://github.com/getsentry/sdk-skills --skill contributing-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:

  1. .github/workflows/*.yml — authoritative test/lint/build commands
  2. Makefile / Taskfile.yml / tox.ini — command wrappers
  3. README.md — install command, SDK name
  4. docs.sentry.io for 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 setup
  • sentry-javascript — Volta pin, monorepo workflow, draft PR rule
  • sentry-go — LOGAF usage, craft release-notes requirement
  • sentry-cocoa — LOGAF with descriptions, copyright header rule
  • sentry-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 sentry

generate-frontend-forms
sentry
Guide for creating forms using Sentry's new form system. Use when implementing forms, form fields, validation, or auto-save functionality.
official
sentry-snapshots-cocoa
sentry
Full Sentry Snapshots setup for Apple/Cocoa projects. Use when asked to "setup SnapshotPreviews", "setup Apple snapshot testing", "upload Apple snapshots to…
official
architecture-review
sentry
Staff-level codebase health review. Finds monolithic modules, silent failures, type safety gaps, test coverage holes, and LLM-friendliness issues.
official
linear-type-labeler
sentry
Classifies Linear issues and applies a Type label from the Sentry workspace's label taxonomy based on the content of each issue's title and description.
official
sentry-flutter-sdk
sentry
Full Sentry SDK setup for Flutter and Dart. Use when asked to "add Sentry to Flutter", "install sentry_flutter", "setup Sentry in Dart", or configure error…
official
sentry-svelte-sdk
sentry
Full Sentry SDK setup for Svelte and SvelteKit. Use when asked to "add Sentry to Svelte", "add Sentry to SvelteKit", "install @sentry/sveltekit", or configure…
official
vercel-react-best-practices
sentry
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js…
official
sentry-tanstack-start-sdk
sentry
Full Sentry SDK setup for TanStack Start React. Use when asked to "add Sentry to TanStack Start", "install @sentry/tanstackstart-react", or configure error…
official