srcx-context

Regenerate .srcx/ codebase context reports from Kotlin source via Gradle.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ClankerGuru/opsx --skill srcx-context
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: srcx-context
Source: https://github.com/ClankerGuru/opsx/tree/main/cli/src/main/resources/content/skills/srcx-context
Command: npx skills add https://github.com/ClankerGuru/opsx --skill srcx-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Regenerate the .srcx/ codebase context report (hub classes, interfaces, entry points, anti-patterns, cross-build links) from current Kotlin source. Agents (especially @scout) read these to answer context questions without grepping the whole tree.

Core Features & Use Cases

  • Scan Kotlin source via PSI and produce Markdown reports under .srcx/ that summarize the codebase's structure, hub classes, public interfaces, entry points, anti-patterns, and cross-build dependency flow.
  • Agents use the generated reports to answer context questions quickly without traversing the codebase.
  • Use Case: After refactoring, regenerate the context map to ensure agents have up-to-date entry points and dependencies.

Quick Start

Run the Gradle task to regenerate the srcx context reports from the project root.

Frequently Asked Questions about srcx-context

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

FAQPage Schema
How do I generate a context map for a Kotlin project?▼

To generate a context map for a Kotlin project, run the Gradle srcx-context task. This scans your Kotlin source via PSI and produces Markdown reports under the .srcx/ directory summarizing hub classes, interfaces, and dependencies.

What is a codebase context report and why do I need one?▼

A codebase context report summarizes your project's structure, entry points, and anti-patterns. Agents read these generated Markdown files to answer context questions quickly without needing to grep or traverse the entire source tree.

How do I update cross-build dependency maps after refactoring Kotlin code?▼

To update cross-build dependency maps after refactoring Kotlin code, execute the srcx-context Gradle task. It regenerates the .srcx/ reports from current source, ensuring agents have up-to-date dependency flow and entry point information.

Do I need a specific Gradle plugin to scan Kotlin source for hub classes?▼

Yes, you need the zone.clanker.srcx settings plugin applied at the project root. This plugin enables the srcx-context Gradle task to scan Kotlin source files and write the generated context maps under the project root and included builds.

Can I use srcx-context with Gradle included builds?▼

Yes, srcx-context supports Gradle included builds. When you run the task from the project root, it writes the generated .srcx/ codebase context reports into both the root directory and each individual included build.

Why are my Kotlin project entry points outdated after code changes?▼

Kotlin project entry points become outdated after code changes because the .srcx/ reports are static snapshots. You must regenerate the context map by running the srcx-context Gradle task to refresh hub classes and cross-build links.