메뉴
Query and analyze the codebase using CodeEagle's knowledge graph. Provides structured code data (symbols, interfaces, edges), impact analysis, design review, and general Q&A — all grounded in an indexed knowledge graph. Use this FIRST before reading source files.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/imyousuf/CodeEagle --skill codeeagle명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | codeeagle |
| description | Query and analyze the codebase using CodeEagle's knowledge graph. Provides structured code data (symbols, interfaces, edges), impact analysis, design review, and general Q&A — all grounded in an indexed knowledge graph. Use this FIRST before reading source files. |
| allowed-tools | Bash(codeeagle *) |
Use CodeEagle to understand the codebase without reading source files directly. Pick the right command based on what you need:
| Need | Command |
|---|---|
| Function signatures, types in a file | codeeagle query symbols --file <path> |
| Interface definition + implementors | codeeagle query interface --name <name> |
| Function call graph (who calls what) | codeeagle query edges --node <name> --type Calls |
| What a function depends on | codeeagle query edges --node <name> --type Calls --direction out |
| Who calls a function | codeeagle query edges --node <name> --type Calls --direction in |
| Cross-service API dependencies | codeeagle query edges --node <name> --type Consumes |
| Import-to-manifest dep tracing | codeeagle query edges --node <name> --type DependsOn |
| Service endpoints |
codeeagle query edges --node <name> --type Exposes| Test coverage for a file/function | codeeagle query edges --node <name> --type Tests |
| All relationships for a symbol | codeeagle query edges --node <name> |
| Search nodes by type/name/package | codeeagle query --type X --name Y |
| Find unused functions/methods | codeeagle query unused |
| Test coverage report by file/function | codeeagle query coverage [--level function] |
| Semantic search ("find code that does X") | codeeagle rag "<query>" |
| Find code by meaning, not exact name | codeeagle rag "<query>" --type Function |
| Impact analysis ("what breaks if I change X?") | codeeagle agent plan "<question>" |
| Design patterns, API consistency | codeeagle agent design "<question>" |
| General "how does X work?" questions | codeeagle agent ask "<question>" |
File, TestFile, Package, Service, Function, TestFunction, Method, Struct, Class,
Interface, Enum, Variable, Constant, Type, Module, Dependency, APIEndpoint,
Document, Directory, Topic, Person, DTO, AIGuideline, DBModel, DomainModel, ViewModel
| Edge | Meaning | Example |
|---|---|---|
Calls | Function/method calls another | extract() -> extractImports() |
Contains | Parent contains child | Service -> File -> Function |
Imports | File/package imports dependency | parser.go -> go/ast |
DependsOn | Dependency relationship | import node -> manifest dep, service -> service |
Implements | Type implements interface | GoParser -> Parser (Go structural, Java/TS/C# nominal, Python Protocol) |
Tests | Test covers source | parser_test.go -> parser.go, TestParseFile -> ParseFile |
Exposes | Service exposes endpoint | backend -> GET /api/users |
Consumes | API call targets endpoint | fetch /api/users -> GET /api/users |
Documents | Doc describes code entity | README -> Service |
HasTopic | Document has extracted topic | CHANGELOG.txt -> authentication |
AppearsIn | Person appears in image | Dad -> photo.jpg |
codeeagle query symbols --file <path>
Returns all functions, structs, interfaces, methods with signatures, line numbers, and export status. Use this instead of reading a source file.
codeeagle query interface --name <name>
codeeagle query interface --name "Store"
Returns the interface location, signature, and all types that implement it.
codeeagle query edges --node <name-or-id>
codeeagle query edges --node "RunAll" --type Calls
codeeagle query edges --node "RunAll" --type Calls --direction out
Returns all incoming/outgoing relationships for a node. Filter by --type and --direction.
codeeagle query edges --node "extractFunctionCalls" --type Calls --direction out
codeeagle query edges --node "extractFunctionCalls" --type Calls --direction in
Outgoing = what this function calls. Incoming = who calls this function.
codeeagle query edges --node "github.com/dgraph-io/badger/v4" --type DependsOn
Shows import -> manifest dep links (kind=import_to_manifest).
codeeagle query --type APIEndpoint
codeeagle query edges --node "GET /api/users" --type Consumes --direction in
codeeagle query unused
codeeagle query unused --type Function --language go
codeeagle query unused --include-exported --package mypackage
Finds functions/methods with no incoming Calls edges. Test functions, init(), and main() are excluded.
By default excludes exported functions (they may be called externally). Use --include-exported to include them.
codeeagle query coverage
codeeagle query coverage --level function
codeeagle query coverage --language go --package parser
Reports which files (default) or functions have test coverage via EdgeTests edges. Shows per-package coverage percentages.
codeeagle query --type Function --name "New*" --package embedded
codeeagle query --type Struct --language go
codeeagle query --type Dependency --name "axios"
codeeagle query --type Service
codeeagle query --type TestFile
codeeagle query --type TestFunction --language rust
codeeagle query --type Document --name "*.txt"
codeeagle query --type Document --name "*.docx"
codeeagle query --type Document --name "*.pdf"
codeeagle query --type Document --name "*.xlsx"
codeeagle query --type Directory
codeeagle query --type Topic
codeeagle query edges --node "authentication" --type HasTopic
codeeagle query --type Person
codeeagle query edges --node "Dad" --type AppearsIn
Non-code files are automatically indexed as Document nodes, including:
dslipak/pdf (pure Go)When a docs LLM provider is available (Ollama or Vertex AI), topics are extracted
and linked via HasTopic edges. Directory hierarchy is represented as Directory
nodes with Contains edges.
codeeagle rag "<natural language query>"
codeeagle rag "authentication middleware" --limit 10
codeeagle rag "database connection" --type Function,Struct
codeeagle rag "error handling patterns" --json --package api
codeeagle rag "API endpoint routing" --edges --language go
codeeagle rag "parser" --no-docs
Finds code entities semantically related to your query using hybrid ranking:
vector similarity + keyword matching + graph centrality (well-connected nodes
rank higher) + code entity boost (functions, structs rank above docs).
Results are deduplicated by node. Requires a vector index (codeeagle sync
or codeeagle vectorindex).
Flags: --limit N, --type T, --package P, --language L, --json, --edges, --min-score S, --no-docs
Use --no-docs to exclude Document/AIGuideline nodes and focus on code entities.
codeeagle agent plan "What would be affected if I change the Store interface?"
Use for: impact analysis, dependency mapping, scope estimation, risk assessment.
codeeagle agent design "Is this new endpoint consistent with existing API patterns?"
Use for: pattern recognition, API consistency, cross-service design checks.
codeeagle agent ask "How does the branch-aware store work?"
Use for: high-level understanding, "how does X work?" questions.
codeeagle query symbols --file <path> — get exact signatures in files you'll modifycodeeagle query interface --name <name> — understand contracts and implementorscodeeagle query edges --node <name> --type Calls — map the call graphcodeeagle query edges --node <name> --type DependsOn — trace dependency chainscodeeagle query edges --node <name> --type Tests — find existing tests for a symbolcodeeagle query coverage --level function --package <pkg> — check test coverage gapscodeeagle agent plan "<what you plan to change>" — assess impact and riskcodeeagle init) with an indexed graph (codeeagle sync)codeeagle query and codeeagle rag commands are read-only and safe to run in parallel. When you need multiple pieces of information, launch them as parallel Bash calls in a single message rather than sequentially. For example, query symbols for 3 files simultaneously, or run rag and query edges at the same time.rag are instant; AI agents take 10-20 secondsrag for natural language search ("find code that handles X"); use query for exact lookups--type Calls --direction out to see what a function depends on--type Calls --direction in to find all callers of a function--type DependsOn to trace imports through to manifest dependencies--type Tests to find which tests cover a given file or functionquery unused to find dead code; query coverage for test gaps--json for machine-readable output