Make /index command ecosystem-aware with auto-detection#33
Open
robertmclaws wants to merge 2 commits intosupermemoryai:mainfrom
Open
Make /index command ecosystem-aware with auto-detection#33robertmclaws wants to merge 2 commits intosupermemoryai:mainfrom
robertmclaws wants to merge 2 commits intosupermemoryai:mainfrom
Conversation
The /index command previously hardcoded JS/TS-specific file names and entry points, leaving Rust/Python/Go with minimal guidance and .NET/C#, Java, Ruby, PHP with none at all. This restructures the command with: - Phase 0: Auto-detect ecosystem by globbing for manifest files - Ecosystem Reference table: per-language guidance for manifests, entry points, architectural patterns, conventions, and key files - Coverage for 8 ecosystems: .NET/C#, JS/TS, Rust, Python, Go, Java/Kotlin, Ruby, PHP - Expanded skip list for language-specific build output folders The single-command UX is preserved (no arguments needed). The agent detects the stack automatically and uses the reference table to guide its exploration. Fixes supermemoryai#32 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
robertmclaws
force-pushed
the
fix/ecosystem-aware-index-command
branch
from
86cde9c to
0740bf9
Compare
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
Comment on lines
-24
to
25
| - Identify API routes, database models | ||
| - Find entry points per the Ecosystem Reference | ||
| - Identify the architectural patterns listed for the detected ecosystem | ||
| - Look for API routes/endpoints, database models/entities, and data flow | ||
|
|
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Phase 0 detected Swift (Package.swift) and Elixir (mix.exs) but the subsequent reference tables had no entries for them, leaving the agent with no ecosystem-specific guidance after detection. Adds complete rows for both ecosystems across all four tables: - Manifest & Config Files - Entry Points & Architecture - Conventions & Patterns - Key Files to Read Also adds .build, _build, and deps to the skip list for Swift and Elixir build output folders. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
bin,obj,target,vendor,__pycache__,.gradle,build)The single-command UX is preserved — no arguments needed. The agent detects the stack automatically and uses the reference table to guide what it should look for in each phase.
Problem
The
/indexcommand hardcoded ecosystem-specific hints directly into the prompt, creating a tiered experience:See #32 for the full breakdown.
What Changed
plugin/commands/index.md— Single file, rewritten to be ecosystem-aware:Test plan
/indexon a JS/TS repo — should still work as before, now with explicit ecosystem detection step/indexon a .NET/C# repo — should detect*.sln/*.csprojand use .NET-specific guidance/indexon a Python repo — should detectpyproject.tomland use Python-specific guidance/indexon a multi-ecosystem repo (e.g., JS frontend + Go backend) — should detect both and explore accordinglyFixes #32
🤖 Generated with Claude Code