@liendev/lien 0.15.1 → 0.17.0

package/CURSOR_RULES_TEMPLATE.md

@@ -15,14 +15,15 @@ You have access to Lien semantic search tools. USE THEM INSTEAD OF grep/ripgrep/
 | "Where is X implemented?" | `semantic_search` | grep |
 | "How does X work?" | `semantic_search` | reading random files |
 | "Find all Controllers" | `list_functions` | grep |
-| Edit a file | `get_file_context` FIRST | direct edit |
+| Edit a file | `get_files_context` FIRST | direct edit |
 | Find similar code | `find_similar` | manual search |
+| "What depends on this file?" | `get_dependents` | manual grep |
 
 ## Before ANY Code Change
 
 REQUIRED sequence:
 1. `semantic_search` → find relevant files
-2. `get_file_context` → understand the file + check `testAssociations`
+2. `get_files_context` → understand the file + check `testAssociations`
 3. Make changes
 4. Remind user to run affected tests
 
@@ -33,10 +34,13 @@ REQUIRED sequence:
 - NOT function names (use grep for exact names)
 - Returns relevance category: `highly_relevant`, `relevant`, `loosely_related`, `not_relevant`
 
-**`get_file_context({ filepath: "path/to/file.ts" })`**
+**`get_files_context({ filepaths: "path/to/file.ts" })`** or **`get_files_context({ filepaths: ["file1.ts", "file2.ts"] })`**
 - MANDATORY before editing any file
-- Returns `testAssociations`: which tests cover this file
+- Returns `testAssociations`: which tests import/cover this file (reverse dependency lookup)
 - Shows file dependencies and relationships
+- Accepts single filepath or array of filepaths for batch operations
+- Single file returns: `{ file: string, chunks: [], testAssociations: [] }`
+- Multiple files returns: `{ files: { [path]: { chunks: [], testAssociations: [] } } }`
 
 **`list_functions({ pattern: ".*Controller.*" })`**
 - Fast symbol lookup by naming pattern
@@ -47,11 +51,30 @@ REQUIRED sequence:
 - Find similar implementations for consistency
 - Use when refactoring or detecting duplication
 
+**`get_dependents({ filepath: "path/to/file.ts", depth: 1 })`**
+- Find all files that import/depend on a target file
+- Use for impact analysis: "What breaks if I change this?"
+- Returns risk level (low/medium/high/critical) based on:
+  - Dependency count (how many files import it)
+  - Complexity metrics (how complex the dependent code is)
+- Highlights top 5 most complex dependents when complexity data available
+
 ## Test Associations
 
-`get_file_context` returns `testAssociations` showing which tests cover the file.
-ALWAYS check this before modifying source code.
-After changes, remind the user: "This file is covered by [test files] - run these to verify."
+`get_files_context` returns `testAssociations` showing which tests import/cover the file.
+- Uses reverse dependency lookup to find test files that import the source file
+- Returns array of test file paths for each requested file
+- ALWAYS check this before modifying source code
+- After changes, remind the user: "This file is covered by [test files] - run these to verify."
+
+Example:
+```typescript
+get_files_context({ filepaths: "src/auth.ts" })
+// Returns: { file: "src/auth.ts", chunks: [...], testAssociations: ["src/__tests__/auth.test.ts"] }
+
+get_files_context({ filepaths: ["src/auth.ts", "src/user.ts"] })
+// Returns: { files: { "src/auth.ts": { chunks: [...], testAssociations: [...] }, ... } }
+```
 
 ## Workflow Patterns
 
@@ -59,19 +82,28 @@ After changes, remind the user: "This file is covered by [test files] - run thes
 ```
 1. semantic_search({ query: "X implementation" })
 2. Review results (check relevance scores)
-3. get_file_context({ filepath: "identified/file.ts" })
+3. get_files_context({ filepaths: "identified/file.ts" })
 4. Answer with specific code locations
 ```
 
 ### Pattern 2: Edit or Change Code
 ```
 1. semantic_search({ query: "area being modified" })
-2. get_file_context({ filepath: "target/file.ts" })
+2. get_files_context({ filepaths: "target/file.ts" })
 3. Check testAssociations in response
 4. Make changes
 5. Tell user which tests to run
 ```
 
+### Pattern 3: Impact Analysis Before Refactoring
+```
+1. get_dependents({ filepath: "target/file.ts" })
+2. Review risk level and dependent count
+3. Check highComplexityDependents (if any)
+4. Use get_files_context on high-risk dependents
+5. Plan refactoring strategy based on impact
+```
+
 ## Query Construction
 
 ### Good Queries (DO THIS)
@@ -107,4 +139,4 @@ For everything else: **Lien first.**
 
 ---
 
-REMINDER: semantic_search and get_file_context FIRST. grep is the fallback, not the default.
+REMINDER: semantic_search and get_files_context FIRST. grep is the fallback, not the default.