agentleFS
SentryKnown publishergetsentry/sentry-godot/.agents/skills/test-review/SKILL.md

test-review

Skill260 starsChanged 4 days agoMITView on GitHub

Finds sentry-godot tests that cannot fail, pass for the wrong reason, race against asynchronous capture, or break on a supported platform. Use for pull request review of GDScript gdUnit4 tests, C++ doctest tests, Pester integration tests, web Playwright tests, .NET tests, Android JUnit tests, and the JS bridge test.

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use test-plan, maintain-verification-skill and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • mbwsimsSkill

    test-plan

    This skill should be used when the user asks to "plan tests", "what should I test", "what tests do I need", "test plan for", "testing strategy for", "test matrix for", "what cases should I cover", "help me plan tests", mentions "/test-plan", or wants to understand what tests are needed before writing any test code.

    Also in 3 projects that use this

  • jaydubya818Skill

    maintain-verification-skill

    Use when a project's verification driver or feature map may be stale.

    Also in 3 projects that use this

  • jaydubya818Skill

    create-verification-skill

    Use when a repository needs a repeatable driver that proves real UI, CLI, or service behavior.

    Also in 3 projects that use this

  • MicrosoftSkill

    blast-radius

    Assesses network dependency and shared-infrastructure exposure. Use when the user asks which services, customers, SLA policies, routes, or redundant links are affected by a network fault.

    Also in 3 projects that use this

  • asterkinSkill

    adr

    Create Architecture Decision Records (ADRs) following project standards. Guides template usage, process, and best practices for documenting architecturally significant decisions.

    Also in 3 projects that use this

  • AnthropicSkill

    architecture

    Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Test style, naming, duplication, or helper refactors.

    line 41

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

You review test changes for the Sentry SDK for Godot Engine. Report only tests that would hide a real regression, fail on a platform CI runs, or call code that does not exist. Missing coverage on its own is not a finding.

Test Layout

PathFrameworkNotes
project/test/suites/gdUnit4Run together in one Godot process per platform.
project/test/isolated/gdUnit4One process per file, for tests that need their own init_sdk() or project settings.
project/test/util/sentry_test_suite.gdhelpersinit_sdk, _before_send, wait_for_captured_event_json, assert_json.
project/test/dotnet/DotnetTestHarness.csC# harnessCalled by name from integration and C++ tests.
tests/cpp/tests/doctestBuilt into the extension with tests=yes.
tests/integration/PesterRuns exported apps on desktop, Android, iOS, and Sauce Labs; shared cases in CommonTestCases.ps1.
tests/web/PlaywrightWeb export tests.
android_lib/src/test/JUnitKotlin plugin unit tests, run by Gradle.
src/sentry/javascript/bridge/test.jsNodeJS bridge bundle test (npm test).

Platform skips use before(_do_skip = ...) with OS.has_feature() or OS.get_name(). Unit tests run on several supported Godot versions across Linux, Windows, and macOS, plus Android and Web jobs.

What To Report

  • Tests that cannot fail or pass for the wrong reason.
  • Tests wired to a harness method, helper, signal, or shared case that does not match what they call or expect.
  • Assertions that race against asynchronous capture.
  • Skip changes that make a test run on a backend without the feature, or stop running on one that has it.

What Not To Report

  • Missing tests or low coverage.
  • Test style, naming, duplication, or helper refactors.
  • PowerShell or GDScript language claims you cannot confirm from this repo's code. Example: Pester script blocks accept extra named arguments; that was a false positive here.
  • Bugs in SDK code under src/ (handled by sdk-review).
  • Flakiness you cannot tie to a specific race or ordering in the code.

Severity

  • high: a test that would pass while a shipped feature is broken on a whole platform.
  • medium: a test that fails or flakes on a supported CI platform, or checks a weaker condition than its name says.
  • low: a narrow gap in an otherwise valid test.

Finding Format

  • Title: the test name and why it passes or fails wrongly.
  • Description: one or two sentences on the regression it hides and the fix.
  • Verification: the default, timing, or name that makes the assertion vacuous or broken, with the file that proves it.

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.