astroray-index

Query Astroray's SQLite project index for package ownership, dependencies, and documentation.

Updated Dec 27, 2025
One-click install
npx skills add https://github.com/HendrikGC02/Astroray --skill astroray-index-hendrikgc02
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: astroray-index
Source: https://github.com/HendrikGC02/Astroray/tree/main/.agents/skills/astroray-index
Command: npx skills add https://github.com/HendrikGC02/Astroray --skill astroray-index-hendrikgc02

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Navigating a large renderer codebase like Astroray is slow when you must grep the whole repository to find which package owns a file, what a package depends on, or whether a script already exists for a task. This Skill routes those questions through Astroray's built-in SQLite project index so you get targeted answers before broad searching or adding new tooling. ## Core Features & Use Cases - Topic and ownership queries: Run project_index.py query "<topic>" or owns <path> to find which package or documentation covers a subject or file. - Dependency and package lookup: Use deps pkgNNN and whatis pkgNNN to inspect package relationships and status before dispatching work. - Script discovery: Use script "<task>" to check whether an existing script already handles a task instead of writing new tooling. - Use Case: Before modifying the spectral pipeline, ask which package owns src/spectral/ and what its dependencies are, then verify the returned package status against the live planning docs and git state. ## Quick Start Ask which Astroray package owns a given source file and what its dependencies are using the project index.

Frequently Asked Questions about astroray-index

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

FAQPage Schema
How do I find which package owns a file in Astroray?▼

Run `python scripts/project_index.py owns <path>` from the repository root. The index returns the owning package, which you should verify against the live planning docs and git state before making changes.

How do I check package dependencies in the Astroray repository?▼

Use `python scripts/project_index.py deps pkgNNN` to list a package's dependencies, and `whatis pkgNNN` to see its status and description. Treat results as routing evidence and inspect the actual source before editing.

How do I search the Astroray project index by topic?▼

Run `python scripts/project_index.py query "<topic>"` with a descriptive topic string. The index returns relevant packages, documentation, and source locations to guide further inspection.

Can I check if a script already exists before writing a new one?▼

Yes, run `python scripts/project_index.py script "<task>"` to search the index for existing scripts matching a task description. This avoids duplicating tooling that the repository already provides.

When should I not rely solely on the project index results?▼

Do not treat index output as final truth when package status may have changed. Always compare results with the live planning sources in .astroray_plan and the current git state before dispatching or implementing work.