Skip to main content

getsentry/sentry-dart

SkillsMP has collected 6 skills from getsentry/sentry-dart. Open a skill to review its source and details.

Latest recorded source activity
SkillsMP catalog refreshed
skills collected
6
GitHub stars
871
GitHub forks
298

Skills in this repository

Showing 6 of 6 collected skills.

occupation
Software Developers
description

Enforce Sentry Dart/Flutter SDK code guidelines for implementation, refactoring, and review. Use when implementing features, adding new functionality, refactoring code, reviewing code, designing APIs, modifying public API surface, handling breaking changes,…

updated
occupation
Software Developers
description

Shape non-trivial work before writing it — decide the modules, the seams, and the public API surface up front. Use when starting a feature, adding an integration, changing a public barrel file, crossing a package or native-interop boundary, or deciding where…

updated
occupation
Software Developers
description

A discipline for hard bugs, flaky tests, CI hangs, and performance regressions in this SDK. Use when the user says "diagnose" or "debug this", reports something broken/throwing/failing/hanging/slow, or a test is flaky. Builds a tight, red-capable feedback…

updated
occupation
Software Quality Assurance Analysts & Testers
description

Three-axis review of the branch diff — Standards (this repo's documented standards + public API surface), Spec (the originating Linear issue / PR), and Correctness (runtime bugs + the SDK threat model — PII, native leaks, buffers, serialization, concurrency).…

updated
occupation
Project Management Specialists
description

Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I…

updated
occupation
Software Quality Assurance Analysts & Testers
description

Enforce Sentry Dart/Flutter SDK test conventions for naming, structure, and fixtures. Use when writing tests, adding tests, modifying tests, reviewing test code, fixing failing tests, adding test coverage, TDD, test-first / red-green, reproducing bugs with…

updated
Showing 6 of 6 collected skills.