# contributing-md

Adopt this skill: https://proskills.md/skills/other/getsentry-sdk-skills-plugins-sentry-sdk-skills-skills-contributing-md

Page: https://proskills.md/skills/other/getsentry-sdk-skills-plugins-sentry-sdk-skills-skills-contributing-md
This document is the public skill bundle for that page. It contains SKILL.md and every helper file the catalog carries. No login is required.

## File: plugins/sentry-sdk-skills/skills/contributing-md/SKILL.md
size: 3120
upstream: https://github.com/getsentry/sdk-skills/blob/main/plugins/sentry-sdk-skills/skills/contributing-md/SKILL.md

````text
---
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.
---

# Contributing.md Skill

Generate 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 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`](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
  <!-- 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
````

## File: README.md
upstream: https://github.com/getsentry/sdk-skills/blob/main/README.md

````text
# Sentry SDK Skills

Agent skills for managing feature development across Sentry SDKs, following the [Agent Skills](https://agentskills.io) open format.

## Installation

### Claude Code (from local clone)

```bash
# Clone the repository
git clone git@github.com:getsentry/sdk-skills.git
cd sdk-skills

# Install the marketplace from the local clone
# Note: ./ (not .) - the slash indicates a local path vs remote marketplace name (owner/repo)
claude plugin marketplace add ./

# Install the plugin directly
claude plugin install sentry-sdk-skills
```

After installation, restart Claude Code. The skills will be automatically invoked when relevant to your task.

### Updating

```bash
# Update the marketplace index
claude plugin marketplace update

# Update the plugin
claude plugin update sentry-sdk-skills
```

Or use `/plugin` to open the interactive plugin manager.

### Other Agents

Copy the `skills/` directory to your agent's skills location, or reference the SKILL.md files directly according to your agent's documentation.

## Available Skills

| Skill | Description |
|-------|-------------|
| `contributing-md` | Generate or update CONTRIBUTING.md for Sentry SDK repositories. Use when asked to "create contributing.md", "update contributing.md", "contributing guide", or "align contributing.md with standard". |
| `daily-update` | Generate a formatted async daily standup message for the Sentry SDK team channel. Use when creating a "daily update", "async daily", or "standup update". |
| `linear-initiative` | Creates Linear projects for SDK teams from an initiative. Use when rolling out features across multiple SDKs. |
| `linear-sdk-telemetry-labeler` | Classify and apply SDK Telemetry labels (Errors, Spans, Traces, Profiles, Replays, Logs, Metrics, Checks, etc.) to Linear issues. Use when tagging issues by telemetry signal. Accepts a team name or a list of Linear IDs. |
| `linear-type-labeler` | Classify and apply Type labels (Bug, Feature, Improvement, Task, etc.) to Linear issues. Use when triaging unlabeled issues or bulk-tagging issues by type. Accepts a team name or a list of Linear IDs. |
| `sdk-feature-implementation` | Implement a feature across SDK repos by spawning parallel agents — from GitHub issues or Linear context to draft PRs with CI verification. |
| `span-convention-review` | Review OpenTelemetry tracing span changes in SDK repos for conformance to Sentry Conventions and OTel Semantic Conventions. |

## Repository Structure

```
sdk-skills/
├── .claude-plugin/
│   └── marketplace.json      # Marketplace manifest
├── plugins/
│   └── sentry-sdk-skills/
│       ├── .claude-plugin/
│       │   └── plugin.json   # Plugin manifest
│       └── skills/
├── AGENTS.md                 # Agent-facing documentation
├── CLAUDE.md                 # Symlink to AGENTS.md
└── README.md                 # This file
```

## Creating New Skills

Skills follow the [Agent Skills specification](https://agentskills.io/specification). Each skill requires a `SKILL.md` file with YAML frontmatter.

### Skill Template

Create a new directory under `plugins/sentry-sdk-skills/skills/`:

```
plugins/sentry-sdk-skills/skills/my-skill/
└── SKILL.md
```

**SKILL.md format:**

```yaml
---
name: my-skill
description: A clear description of what this skill does and when to use it. Include keywords that help agents identify when this skill is relevant.
---

# My Skill Name

## Instructions

Step-by-step guidance for the agent.

## Examples

Concrete examples showing expected input/output.

## Guidelines

- Specific rules to follow
- Edge cases to handle
```

### Naming Conventions

- **name**: 1-64 characters, lowercase alphanumeric with hyphens only
- **description**: Up to 1024 characters, include trigger keywords
- Keep SKILL.md under 500 lines; split longer content into reference files

### Optional Fields

| Field | Description |
|-------|-------------|
| `license` | License name or path to license file |
| `compatibility` | Environment requirements (max 500 chars) |
| `model` | Override model for this skill (e.g., `sonnet`, `opus`, `haiku`) |
| `allowed-tools` | Space-delimited list of tools the skill can use |
| `metadata` | Arbitrary key-value pairs for additional properties |

```yaml
---
name: my-skill
description: What this skill does
license: Apache-2.0
model: sonnet
allowed-tools: Read Grep Glob
---
```

## References

- [Agent Skills Specification](https://agentskills.io/specification)
- [Sentry Engineering Practices](https://develop.sentry.dev/engineering-practices/)

## License

Apache-2.0
````
