agentleFS
Sign inStart free
fotis89fotis89/ctx-launcher/.github/skills/run-tests/SKILL.md

run-tests

Skill4 starsChanged 34 days agoMITView on GitHub

Run tests for the ctx-launcher project and report results

48 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use prepare-release, create-pr and 2 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.
  • ShopifySkill

    prepare-release

    Prepare the changeset-release/main branch for release by syncing version.ts files and running pnpm install

    Also in 3 projects that use this

  • SentrySkill

    create-pr

    Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.

    Also in 4 projects that use this

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 4 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 44 edited versions we read keep these.

  • 2

    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:

    Run the test suite and report results.

    line 7
  2. Distinctive:

    If tests fail, read the failure output, identify the failing test, and trace it to the source code.

    line 17

“Common” is measured: kept by at least 6 in 10 of the 44 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

Run the test suite and report results.

Default: unit tests (IL mode, fast)

dotnet test tests\wl.tests\wl.tests.csproj --verbosity quiet

Expected: all tests pass, 0 failures, 0 warnings.

If tests fail, read the failure output, identify the failing test, and trace it to the source code. Common causes:

  • LaunchServiceTests / CopilotServiceTests — Copilot args changed (flags and values are separate list elements; --name=/--session-id=/--resume= are single elements), plugin manifests
  • PathHelperTests — Slugify, $VAR/~ resolution, PATH/PATHEXT lookup
  • CopilotRunnerTests — executable resolution or TryGetVersion
  • PromptServiceTests — frontmatter parsing edge case
  • WorkspaceServiceTests / SetupServiceTests — workspace validation (schemaVersion), .gitignore merge

Optional: E2E tests against the AOT binary

The E2E suite spawns the published native binary against a fake copilot shim to catch AOT-only regressions (trimming, embedded resources, System.CommandLine init). Build it first (see /publish, "publish only"), then:

$env:WL_BINARY_PATH = (Resolve-Path src\wl\bin\Release\net10.0\win-x64\publish\wl.exe).Path
dotnet test tests\wl.e2e.tests\wl.e2e.tests.csproj --verbosity quiet

WL_BINARY_PATH must be absolute. Skip E2E for routine dev loops; run it before a release or when debugging an AOT-only issue. scripts\install-local.ps1 runs both suites automatically.

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.

Check your setup, free