scalex

Index Git-tracked Scala/Java sources for command-driven code exploration.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/Quafadas/Mathlify --skill scalex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scalex
Source: https://github.com/Quafadas/Mathlify/tree/main/.github/skills/scalex
Command: npx skills add https://github.com/Quafadas/Mathlify --skill scalex

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Navigate large Scala/Java codebases by indexing Git-tracked sources and offering fast, command-driven exploration of definitions, usages, and documentation.

Core Features & Use Cases

  • Index top-level declarations from git-tracked Scala/Java files.
  • Find definitions, implementations, usages, scaladoc, and file contents across a codebase.
  • Generate overviews, member lists, and import graphs to understand project structure quickly.

Quick Start

Run scalex def MySymbol -w /project to locate its definition.

Frequently Asked Questions about scalex

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I navigate and find definitions in a large Scala or Java codebase?

To navigate large Scala/Java codebases, you can index Git-tracked sources and use commands like def, impl, and refs to quickly locate definitions, implementations, and usages across multiple files.

Can I search for Scaladoc and import graphs in Scala projects without an IDE?

Yes, you can retrieve Scaladoc and generate import graphs by indexing Git-tracked Scala sources, allowing you to understand project structure and dependencies directly from the command line.

Does code navigation work with multi-file Scala and Java projects tracked in Git?

Yes, code navigation works with large, multi-file Scala and Java projects by building a local index from Git-tracked files on the first run and reusing cached results for subsequent queries.

What is the best way to explore top-level declarations and members in Scala code?

The best way to explore top-level declarations and members is to index the Scala codebase and use dedicated commands like members and graph to generate structural overviews and lists.

Why does the code analysis tool build an index on the first run?

The code analysis tool builds a local index on the first run to enable fast, accurate code navigation and exploration of Git-tracked sources, reusing cached results for subsequent queries.

Do I need to cache results to perform code navigation on Java sources?

You do not need to manually cache results; the tool automatically builds a local index from Git-tracked Java files on the first run and reuses the cached results for subsequent code navigation.