compiler-and-fourslash-tests Skill
How to write, run, and debug compiler tests and fourslash (LSP) tests in the typescript-go repository. Covers test file formats, directives, markers, baseline management, and the fourslash verification API. Published by microsoft in typescript-go.
Decision snapshot
Is this a fit?
Testing, Writing, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
24 days ago · Apache-2.0 license
No specific cautions were detected. Review the source and requested permissions before installing.
What is compiler-and-fourslash-tests Skill?
How to write, run, and debug compiler tests and fourslash (LSP) tests in the typescript-go repository. Covers test file formats, directives, markers, baseline management, and the fourslash verification API. Published by microsoft in typescript-go. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Writing
- Testing use cases
- Writing use cases
Declared skill metadata
- Source file: .github/skills/compiler-and-fourslash-tests/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use compiler-and-fourslash-tests Skill
- Use it for testing.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/typescript-go
- Skill file: .github/skills/compiler-and-fourslash-tests/SKILL.md
What it does
How to write, run, and debug compiler tests and fourslash (LSP) tests in the typescript-go repository. Covers test file formats, directives, markers, baseline management, and the fourslash verification API.
Skill instructions
Writing, Running, and Debugging Compiler Tests and Fourslash Tests This guide covers the complete testing workflow for the typescript-go repository, including compiler tests (type-checking, emit, diagnostics) and fourslash tests (language server features like completions, hover, go-to-definition). 1. Compiler Tests Compiler tests validate the TypeScript compiler's behavior: diagnostics, JavaScript emit, source maps, type/symbol baselines, and more. Each test is a .ts or .tsx file that the test runner compiles, then compares output against stored baselines. 1.1 Where Test Files Live | Path | Purpose | |------|---------| | testdata/tests/cases/compiler/ | Regression tests (local to this repo) | | testdata/tests/cases/conformance/ | Conformance tests (local to this repo) | | submodules/TypeScript/tests/cases/compiler/ | Submodule tests from upstream TypeScript | | submodules/TypeScript/tests/cases/conformance/ | Submodule conformance tests from upstream | 1.2 Writing a New Compiler Test A
Verified compatibility and discovery
Frequently asked questions
What is compiler-and-fourslash-tests?
compiler-and-fourslash-tests is a open-source AI agent skill with Copy skill directory. How to write, run, and debug compiler tests and fourslash (LSP) tests in the typescript-go repository.
Who is compiler-and-fourslash-tests best for?
compiler-and-fourslash-tests is best for reusing agent instructions, scripts, and references, testing workflows, writing workflows.
How do I install compiler-and-fourslash-tests?
Install or run compiler-and-fourslash-tests using Copy skill directory. Check compiler-and-fourslash-tests for the latest setup command.
Is compiler-and-fourslash-tests actively maintained?
compiler-and-fourslash-tests may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
