agentleFS
SentryKnown publishergetsentry/sentry-go/.agents/skills/sdk-review/SKILL.md

sdk-review

Skill1.1k starsChanged 4 days agoMITView on GitHub

Review sentry-go changes for violations of Sentry SDK contracts: host-app safety, data-collection gates, dependency versions, public API, context propagation, flush deadlines, client reports and event types.

6 other projects use a version of this, 3 of them edited.

Trending

Quiet since July.about the whole repository

Dec 2025: 1 mentionJan 2026: 0 mentionsFeb 2026: 1 mentionMar 2026: 1 mentionApr 2026: 3 mentionsMay 2026: 3 mentionsJun 2026: 1 mentionJul 2026: 1 mentionAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the getsentry/sentry-go repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about getsentry/sentry-go

The biggest 5 of 23 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 23

Talked about on GitHub (23 times).

On GitHub · 23

18 more on GitHub
  • Other versions6 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 3

    1. getsentry/sentry-python★ 2.2k26% same
    2. getsentry/sentry-ruby★ 99011% same
    3. getsentry/sentry-dotnet★ 77627% same

    Wrote their own version · 3

    1. DataDog/dd-trace-java★ 739same name
    2. DataDog/dd-trace-dotnet★ 573same name
    3. getsentry/sentry-godot★ 260same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

Files
SKILL.md

Report a finding only if you can show from the code how the change violates one of the rules below. Propose the simplest fix.

Rules

  1. Never break the host app (high). SDK code that can panic, block, or change the user's behavior: returned errors or values, request or job flow.
  2. Data collected without its gate (high). Bodies, headers, cookies, user info, gen_ai inputs/outputs or DB results recorded without their data-collection option. Header and cookie names match case-insensitively. Gate on ClientOptions.DataCollection; SendDefaultPII is deprecated. Automatically collected header, cookie, query or body values must go through the denylist filter in data_collection_filter.go; a new path that sends them raw is a finding. Data the user set explicitly (scope, span, BeforeSend) is never gated or scrubbed: don't flag reading it back from the scope, but do flag new code that gates or rewrites it.
  3. Dependency versions (high). Third-party dependency APIs newer than the version the module's own go.mod requires. CI builds every module through go.work, so a newer version that another module requires can hide the gap.
  4. Public API (medium). Breaking public changes without a deprecation path, or internals exposed as public API.
  5. Context propagation (high). An integration must fork the scope from the incoming request and pass context.Context on, calls should reuse context.Context, logs and metrics should be linked using WithCtx and sentry-trace / baggage should agree with the span's sampling decision.
  6. Flush deadline (high). Flush / FlushWithContext must bound draining and sending, not only the final transport flush, and return false once the deadline passes. Close dropping queued items and rejecting late ones is intended; leaked goroutines are not.
  7. Client reports (medium). Dropped items (rate limit, sampling, BeforeSend) that aren't recorded, or are recorded under the wrong category.
  8. Event types (medium). Check-ins, logs or metrics going through error sampling or BeforeSend, or losing their type.

Do not report

  • Anything CI already fails on: compile and type errors, language features or standard library APIs newer than Go 1.26 (test.yml builds on Go 1.26 and 1.27), go vet, untidy go.mod files (make mod-tidy), known-vulnerable dependencies (govulncheck), and the golangci-lint checks in .golangci.yml, such as unchecked errors (errcheck), unclosed response bodies (bodyclose), gosec, staticcheck, unused code, and formatting (gofmt, goimports).
  • A trade-off or follow-up (stacked PR, major branch) that the PR description explains.
  • Edge cases that need misuse or very unlikely timing.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.