skills.rest
Disentinel
DisentinelCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

grafema-discovery-unbuilt-projects

Configure explicit services in config.yaml to fix Grafema source discovery.

36|2|Updated Jan 19, 2026
Search Tags:#code analysis#discovery#configuration#monorepo#build tools#grafema
One-click install
npx skills add https://github.com/Disentinel/grafema --skill grafema-discovery-unbuilt-projects
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grafema-discovery-unbuilt-projects
Source: https://github.com/Disentinel/grafema/tree/main/.claude/skills/grafema-discovery-unbuilt-projects
Command: npx skills add https://github.com/Disentinel/grafema --skill grafema-discovery-unbuilt-projects

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves issues where Grafema fails to analyze any source files, reporting zero modules or functions, typically due to package.json entry points referencing non-existent build directories.

Core Features & Use Cases

  • Corrects Grafema's Code Discovery: Ensures Grafema indexes source files in projects where build steps haven't been run or where entry points are misconfigured.
  • Handles Monorepos: Supports projects with multiple source directories (e.g., src/, hooks/src/).
  • Use Case: When grafema analyze shows only 29 nodes and no functions or modules despite source code existing, this skill provides the configuration to fix it.

Quick Start

Add an explicit services array to your .grafema/config.yaml file to define your project's source directories and entry points.

Frequently Asked Questions about grafema-discovery-unbuilt-projects

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

FAQPage Schema
Why does Grafema code analysis report zero modules when source files exist?▼

Grafema code analysis reports zero modules when `package.json` entry points reference non-existent `dist/` or `build/` directories. Adding an explicit `services` array to `.grafema/config.yaml` configures the correct source directories for indexing.

How do I fix Grafema code discovery in projects with unbuilt directories?▼

Fix Grafema code discovery by adding explicit `services` configuration to your `.grafema/config.yaml` file. This defines the correct source directories and entry points, bypassing missing or outdated build outputs.

Can I analyze monorepos with multiple source directories using Grafema?▼

Yes, Grafema analyzes monorepos with multiple source directories like `src/` and `hooks/src/`. You configure these paths explicitly within the `services` array in your `.grafema/config.yaml` file for correct indexing.

How do I configure Grafema for SWE-bench tasks with misconfigured entry points?▼

Configure Grafema for SWE-bench tasks by adding explicit `services` entries to `.grafema/config.yaml`. This corrects codebase indexing when `package.json` points to outdated or missing build directories.

What is the best way to index source files in a monorepo without running build steps?▼

The best way to index source files without running build steps is configuring explicit `services` in `.grafema/config.yaml`. This directs Grafema to index actual source directories instead of non-existent build outputs.

Related Skills

Explore More Software Engineering Skills→
kunwl123456kunwl123456
26

Skill Health Monitor

Scan skills directories for structural compliance and generate health and dependency reports.

Community
Basic
a747895159a747895159

refactor-assistant

Analyze source code to identify smells and propose refactoring opportunities.

Community
Intermediate
sayali-ingle-pdlsayali-ingle-pdl

prettierignore

Generate a repository-level .prettierignore for build outputs and dependencies.

Community
Advanced
VoDaiLoczVoDaiLocz
24

lint-and-validate

Automate linting and static analysis of code in CI pipelines.

Community
Intermediate