How do I install the Contributing Md skill?

Run npx skillmds@latest add getsentry/contributing-md in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Contributing Md safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Contributing Md?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Contributing Md free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Contributing Md?

Sentry (@getsentry) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Contributing Md by getsentry — Agent Skill

Name: Contributing Md
Author: Sentry

Contributing Md

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.

Sentry a802c8f 3.0 KB Updated Sep 17, 2026 845 repo stars

File contents

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 commands
Makefile / Taskfile.yml / tox.ini — command wrappers
README.md — install command, SDK name
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

---name: contributing-mddescription: 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.---# Contributing.md SkillGenerate or align a Sentry SDK repository's `CONTRIBUTING.md` with the[standard template](https://develop.sentry.dev/sdk/getting-started/templates/contributing-md-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 thereshould be trusted. If it does not exist, use the fetched template as the starting point.### 3. Find commands from the repoFor missing or placeholder values, read in priority order:1. `.github/workflows/*.yml` — authoritative test/lint/build commands2. `Makefile` / `Taskfile.yml` / `tox.ini` — command wrappers3. `README.md` — install command, SDK name4. `docs.sentry.io` for the SDK — setup steps if not found above### 4. Reference good examplesCheck these repos for structural inspiration if needed:- [`sentry-python`](https://github.com/getsentry/sentry-python/blob/master/CONTRIBUTING.md) — integration principles, user vs contributor setup- [`sentry-javascript`](https://github.com/getsentry/sentry-javascript/blob/master/CONTRIBUTING.md) — Volta pin, monorepo workflow, draft PR rule- [`sentry-go`](https://github.com/getsentry/sentry-go/blob/master/CONTRIBUTING.md) — LOGAF usage, craft release-notes requirement- [`sentry-cocoa`](https://github.com/getsentry/sentry-cocoa/blob/master/CONTRIBUTING.md) — LOGAF with descriptions, copyright header rule- [`sentry-java`](https://github.com/getsentry/sentry-java/blob/master/CONTRIBUTING.md) — 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: ```html  ```- If file would exceed 200 lines, move verbose steps to a linked doc and reference it### 6. VerifyGrep 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

Frequently asked questions