Skip to content

fix: skill prompt covers both .graph and three-file formats #121

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jonathanpopham wants to merge 1 commit into from
Closed

fix: skill prompt covers both .graph and three-file formats #121

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 12 additions & 6 deletions cmd/skill.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,14 +8,20 @@ import (

const skillPrompt = `This repository has Supermodel graph shard files next to source files.

Files ending in .calls.* contain function call relationships (who calls what, with file and line number).
Files ending in .deps.* contain dependency relationships (imports and imported-by).
Files ending in .impact.* contain blast radius data (risk level, affected domains, direct/transitive dependents).
There are two formats — use whichever is present:

Single-file format:
Files ending in .graph.* contain all graph data (deps, calls, impact) in one file with [deps], [calls], and [impact] sections.

Three-file format (recommended):
Files ending in .calls.* contain function call relationships (who calls what, with file and line number).
Files ending in .deps.* contain dependency relationships (imports and imported-by).
Files ending in .impact.* contain blast radius data (risk level, affected domains, direct/transitive dependents).

When navigating the codebase:
- Read .deps files to understand what a module depends on and what depends on it
- Read .calls files to trace call chains across files
- Read .impact files to assess the blast radius before making changes
- Read .deps or .graph files to understand what a module depends on and what depends on it
- Read .calls or .graph files to trace call chains across files
- Read .impact or .graph files to assess the blast radius before making changes
- These files appear in grep/rg results alongside source code — use the data to navigate faster`

func init() {
Expand Down
Loading