What is a .Skip file?
SKIP is a small marker file some test suites use to record that a particular test is deliberately skipped.
- Did you know
- In libigl’s test data a .skip file sits next to a test to tell the harness not to run it - a lightweight alternative to commenting the test out.
- Because it is just plain text, a .skip file often holds a short reason or a reference explaining why the test is disabled.
- .skip is a project convention rather than a registered format, so its exact meaning depends on the test framework that reads it.
- What Analyser reads
- Open and read programming-language source, build and configuration files as text: C, C++ and their headers, C#, Java, Kotlin, Go, Rust, Python, Ruby, PHP, Swift, Scala, Lua, Perl, R, Dart, Groovy and Visual Basic, GPU shaders (GLSL, HLSL), shell scripts (sh, Bash, Zsh, Fish), and the build and tooling files that fill a source repository - CMake, Makefiles, Ninja, Autotools (.in / .ac / .am / .m4), qmake projects, Doxygen configs and the dotfiles that configure Git, Docker, npm, ESLint, Prettier, Cursor and clang-format. Also opens Objective-C++ (.mm / .hmm), more GPU shaders (.fs / .vs / .gs), Boost.Jam and Meson build scripts, Unix manual pages, web stylesheets (Less, Sass/SCSS) and Svelte components, gettext translations (.po / .pot), Apple entitlements and licence/readme text, plus Cython (.pyx), OpenGL shaders (.fsh / .vsh / .geom), Git hook samples, ESLint and Yarn configs and ASP.NET (.aspx) pages. Each opens with a source preview, line count and metadata, entirely in your browser.
- Depth of analysis
- .Skip is an identification-grade format: Analyser recognises it from its bytes and decodes the header metadata it carries, rather than opening it in a full viewer. Formats that do get a full viewer are marked "Full" on the formats page.
- Open a .Skip file
- Drag a .Skip file onto the Analyser home page (or tap to pick one). It is identified entirely in your browser - nothing is uploaded, there is no account, and it works offline once installed.