New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Raven Test Triage

by marinasundstrom in marinasundstrom/raven

Testing and stabilization workflow for the Raven compiler test suite.

MITAuto-check passedTesting & QA

Install Raven Test Triage

skills CLI
$ npx skills add marinasundstrom/raven --skill raven-test-triage -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install marinasundstrom/raven raven-test-triage --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/marinasundstrom/raven.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/raven-test-triage .claude/skills/raven-test-triage && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
raven-test-triage
GitHub stars
108
Token cost
~1.4k tokens
SKILL.md length
676 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

Testing and stabilization workflow for the Raven compiler test suite.

  • Works in 4 steps: Run the smallest targeted test set that… → Run the appropriate baseline or isolated… → Clean up outdated assertions in the… → …
  • Establishing baselines
  • SKILL.md covers Baseline Strategy, Build Decision, Test Philosophy and Legacy Codegen Tests, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Raven Test Triage is an agent skill from marinasundstrom/raven. Testing and stabilization workflow for the Raven compiler test suite. Use when establishing baselines, fixing failing tests, isolating runtime and emission-heavy failures, validating binder/semantic-model regressions, testing incremental compilation behavior, or converting unstable codegen assertions into behavior-focused coverage.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Project scaffolding, Failing and flaky tests and Test generation. It works with .NET. The repository describes itself as: Raven is a pragmatic, typed, general-purpose programming language for .NET. The licence is MIT.

When your agent uses it

  • Establishing baselines
  • Fixing failing tests
  • Isolating runtime and emission-heavy failures
  • Validating binder/semantic-model regressions

Example prompts

  • “/raven-test-triage”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Run the smallest targeted test set that proves the fix.
  2. Run the appropriate baseline or isolated suite for the affected area.
  3. Clean up outdated assertions in the touched area instead of preserving obviously stale expectations.
  4. For a bootstrap-stage candidate, record the exact commit, active SDK,

What it can do on your machine

Read from SKILL.md and the folder at commit 562a449. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Raven Test Triage loads about 1.4k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 676 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~88
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from marinasundstrom/raven at commit 562a449, republished under its MIT licence (© marinasundstrom). 676 words, ~1,402 tokens.

Download SKILL.mdSave it as .claude/skills/raven-test-triage/SKILL.md (or your agent's skills folder).
name
raven-test-triage
description
Testing and stabilization workflow for the Raven compiler test suite. Use when establishing baselines, fixing failing tests, isolating runtime and emission-heavy failures, validating binder/semantic-model regressions, testing incremental compilation behavior, or converting unstable codegen assertions into behavior-focused coverage.

Raven Test Triage

Use this skill when the task is primarily about test failures, stabilization, or regression coverage.

Baseline Strategy

For large stabilization passes, use a planned task sequence: define the current test or behavior slice, keep one step active, verify it before moving on, and re-evaluate the next slice after each result. Tell the user what the next step is after each verified slice. Prefer a reduced compiler test that locks the invariant first, then broaden to LSP, sample builds, baseline, or runtime suites only when the affected layer warrants it.

Establish the baseline with:

bash
scripts/test-baseline.sh

This excludes runtime or emission-heavy noise from the initial stabilization pass.

Run isolated heavy suites separately with:

bash
scripts/test-runtime-isolated.sh

For release preparation, cross-target SDK changes, or a bootstrap-stage gate, also follow docs/testing/release-and-bootstrap-gates.md. In particular, run:

bash
scripts/test-target-framework-matrix.sh
scripts/build-project-samples.sh

The target matrix must use the .NET 11 repository compiler host to build and run both net10.0 and net11.0 representatives. Do not treat a build using an installed SDK, or a repository compiler DLL combined with installed MSBuild targets, as equivalent evidence. The baseline plus the standalone and project sample corpora are compatibility gates for stage transitions.

Use WarningLevel=0 for ad hoc test runs.

Build Decision

Run scripts/codex-build.sh only when needed:

  • first compile in a fresh workspace
  • after changing generator inputs, syntax models, bound models, or related generated artifacts

Otherwise prefer targeted builds and targeted test runs.

Test Philosophy

Prefer stable assertions:

  • diagnostics
  • symbol shape
  • metadata shape
  • operation shape
  • observable runtime behavior
  • binder-owned state when testing binder lifecycle, local/parameter ownership, scope contents, or binder-produced diagnostics
  • public semantic API behavior when testing language-service-facing answers such as symbol lookup, type info, declared symbols, and diagnostics before/after edits

Avoid asserting:

  • emitted opcodes
  • exact lowered instruction sequences
  • fragile internal IL shapes for stabilized features

Legacy Codegen Tests

Treat legacy emitted-opcode and lowered-shape tests as unstable scaffolding.

When touching such tests:

  • remove or replace them with behavior-focused coverage when possible
  • if temporary instruction-level checks are still useful during development, move or keep them under test/Raven.CodeAnalysis.Tests/CodeGen/Development

Development-only codegen tests should stay out of normal baseline or runtime stabilization passes.

Show full SKILL.md (334 more words)Show less

Regression Locking

Compiler bug fixes must be locked with focused tests. Choose the narrowest layer that proves the bug is fixed:

  • parser issue: syntax test
  • semantic issue: binding or diagnostic test
  • binder ownership issue: binder or semantic-model test for the responsible scope
  • incremental issue: before/after semantic-model or diagnostics test that proves stale binder state is not reused
  • language-service issue: compiler API test first, then LSP presentation/scheduling test if editor behavior is also involved
  • operation modeling issue: operations test
  • runtime behavior issue: runtime or codegen behavior test
  • compiler-host/target-framework issue: metadata/reference assertion plus the executable target-framework matrix
  • lazy-binding issue: test both a cold semantic query and, when relevant, a second query that proves the first query populated compiler-owned state for reuse
  • available-state optimization: include a negative or ambiguous case proving the code falls back to normal full binding instead of returning a partial or guessed answer
  • cross-file incremental issue: add or update another document in the same project, then query symbols/diagnostics in the original document through the current compilation snapshot
  • LSP scheduling issue: test that foreground semantic requests are not blocked by broad background gates, while background diagnostics/analyzers/inlays can skip, cancel, or requeue
  • binder lifecycle issue: prove invalidated binders lose their owned symbols and diagnostics, and unchanged binders keep valid derived state only when their syntax and semantic context are equivalent

Keep documentation in step with stabilized behavior. When test triage exposes behavior that should be documented but is missing from docs/, consider adding the documentation instead of leaving the expectation only in tests.

ITestOutputHelper may be used for targeted diagnostics during investigation.

Validation

  1. Run the smallest targeted test set that proves the fix.
  2. Run the appropriate baseline or isolated suite for the affected area.
  3. Clean up outdated assertions in the touched area instead of preserving obviously stale expectations.
  4. For a bootstrap-stage candidate, record the exact commit, active SDK, target frameworks, toolchain provenance, baseline result, and sample-corpus result. Classify port-discovered defects before deciding whether to backport them to the maintained pre-bootstrap line.

© marinasundstrom, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/raven-test-triage of marinasundstrom/raven.

Open the folder on GitHubat commit 562a449

Compare with similar skills

Raven Test Triage next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Raven Test Triage compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Raven Test Triage this skillmarinasundstrom/raven108—~1.4kAutomated safety check: PassMIT
Corvus Build And Testcorvus-dotnet/Corvus.JsonSchema200—~5.5kAutomated safety check: PassApache-2.0
Run Testsrunceel/ReactiveProperty944—~3.6kAutomated safety check: PassMIT
MAUI UI Test Writerdotnet/maui23k—~3kAutomated safety check: PassMIT
Exp Test Maintainabilitydotnet/skills5.6k1 repos~2.5kAutomated safety check: PassMIT
Issue To Regression Testbrunosabot/streamline-card269—~529Automated safety check: PassMIT

Similar skills

  • Corvus Build And Test

    corvus-dotnet/Corvus.JsonSchema

    Build, test, and run the Corvus.JsonSchema solution correctly.

    200 GitHub stars~5.5k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Run Tests

    runceel/ReactiveProperty

    Runs .NET tests with dotnet test. An agent skill from runceel/ReactiveProperty.

    944 GitHub stars~3.6k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

  • MAUI UI Test Writer

    dotnet/maui

    Official

    Writes UI tests that reproduce a GitHub issue in .NET MAUI and keeps iterating until the tests actually fail, proving they catch the bug.

    23k GitHub stars~3k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Exp Test Maintainability

    dotnet/skills

    Official

    Detects duplicate boilerplate, copy-paste tests, and structural maintainability issues across .NET test suites.

    5.6k GitHub starsUsed in 1 repo~2.5k tokens
    DevelopmentAuto-check passed

  • Issue To Regression Test

    brunosabot/streamline-card

    A skill your agent uses when the user asks to fix a bug, references a GitHub issue number, or describes an issue and wants a fix.

    269 GitHub stars~529 tokensUpdated 4 mo ago
    Testing & QAAuto-check passed

  • Fix Random CI Test Failure

    dotnet/macios

    Official

    Investigate and fix flaky/random CI test failures in dotnet/macios.

    2.9k GitHub stars~1.3k tokensUpdated 2 days ago
    Testing & QAAuto-check passed

More from marinasundstrom/raven

  • Raven Debug Compiler

    marinasundstrom/raven

    Debug workflow for Raven compiler analysis and emission issues using rvn frontend tooling and the rvnc compiler driver.

    108 GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Raven Lsp Debug

    marinasundstrom/raven

    Troubleshooting workflow for Raven language service and editor failures.

    108 GitHub stars~3.7k tokensUpdated today
    Auto-check passed

  • Raven Feature Workflow

    marinasundstrom/raven

    End-to-end workflow for Raven language and compiler feature work.

    108 GitHub stars~2.5k tokensUpdated today
    Auto-check passed

  • Raven Test Cleanup

    marinasundstrom/raven

    Coverage-improvement workflow for Raven tests through cleanup.

    108 GitHub stars~2.2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Raven Test Triage

What does Raven Test Triage do?

Testing and stabilization workflow for the Raven compiler test suite. Raven Test Triage is an agent skill from marinasundstrom/raven. Testing and stabilization workflow for the Raven compiler test suite.

When should I use Raven Test Triage?

Raven Test Triage fits situations like: establishing baselines; fixing failing tests; isolating runtime and emission-heavy failures; validating binder/semantic-model regressions.

How do I install Raven Test Triage in Claude Code?

Run `npx skills add marinasundstrom/raven --skill raven-test-triage -a claude-code`. Or copy the skill folder (.agents/skills/raven-test-triage in marinasundstrom/raven) into .claude/skills/raven-test-triage in your project. Claude Code loads it when a task matches its description.

How do I install Raven Test Triage in Codex?

Run `npx skills add marinasundstrom/raven --skill raven-test-triage -a codex`. Or copy the skill folder (.agents/skills/raven-test-triage in marinasundstrom/raven) into .agents/skills/raven-test-triage in your project. Codex loads it when a task matches its description.

Can I use Raven Test Triage in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add marinasundstrom/raven --skill raven-test-triage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/raven-test-triage, .gemini/skills/raven-test-triage, .github/skills/raven-test-triage and .opencode/skills/raven-test-triage in your project.

What does Raven Test Triage need to run?

SKILL.md names no scripts, command-line tools or credentials: Raven Test Triage is instructions for the agent only.

Does Raven Test Triage access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Raven Test Triage safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Raven Test Triage use?

Raven Test Triage is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Raven Test Triage use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Raven Test Triage?

Skills that share tags, products or a category with Raven Test Triage: Corvus Build And Test (corvus-dotnet/Corvus.JsonSchema, 200 stars), Run Tests (runceel/ReactiveProperty, 944 stars), MAUI UI Test Writer (dotnet/maui, 23k stars) and Exp Test Maintainability (dotnet/skills, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Raven Test Triage?

marinasundstrom (a GitHub user) maintains it in marinasundstrom/raven, which has 108 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 10, 2026.

Source: marinasundstrom/raven on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.