gitnexus 1.1.0 → 1.1.2

package/skills/impact-analysis.md

@@ -1,117 +1,117 @@
----
-name: gitnexus-impact-analysis
-description: Analyze blast radius before making code changes
----
-
-# Impact Analysis
-
-## Quick Start
-```
-0. READ gitnexus://repos                                    → Discover indexed repos
-1. If "Index is stale" → gitnexus_analyze({repo: "my-app"})
-2. gitnexus_impact({target, direction: "upstream", repo: "my-app"}) → What depends on this
-3. READ gitnexus://repo/my-app/clusters                     → Check affected areas
-4. READ gitnexus://repo/my-app/processes                    → Affected execution flows
-```
-
-## When to Use
-- "Is it safe to change this function?"
-- "What will break if I modify X?"
-- "Show me the blast radius"
-- "Who uses this code?"
-
-## Understanding Output
-
-| Depth | Risk Level | Meaning |
-|-------|-----------|---------|
-| d=1 | WILL BREAK | Direct callers/importers |
-| d=2 | LIKELY AFFECTED | Indirect dependencies |
-| d=3 | MAY NEED TESTING | Transitive effects |
-
-## Workflow Checklist
-```
-Impact Analysis:
-- [ ] READ gitnexus://repos to find the right repo
-- [ ] gitnexus_impact(target, "upstream", repo) to find dependents
-- [ ] READ gitnexus://repo/{name}/clusters to understand affected areas
-- [ ] Check high-confidence (>0.8) dependencies first
-- [ ] Count affected clusters (cross-cutting = higher risk)
-- [ ] If >10 processes affected, consider splitting change
-```
-
-## Resource Reference
-
-### gitnexus://repo/{name}/clusters
-Check which clusters might be affected:
-```yaml
-clusters:
-  - name: Auth
-    symbols: 47
-  - name: API
-    symbols: 32
-```
-
-### gitnexus://repo/{name}/processes
-Find which processes touch the target:
-```yaml
-processes:
-  - name: LoginFlow
-    type: cross_community
-    steps: 5
-```
-
-## Tool Reference
-
-### gitnexus_impact
-Analyze blast radius:
-```
-gitnexus_impact({
-  target: "validateUser",
-  direction: "upstream",
-  minConfidence: 0.8,
-  maxDepth: 3,
-  repo: "my-app"
-})
-
-→ d=1 (WILL BREAK):
-  - loginHandler (src/auth/login.ts:42) [CALLS, 100%]
-  - apiMiddleware (src/api/middleware.ts:15) [CALLS, 100%]
-
-→ d=2 (LIKELY AFFECTED):
-  - authRouter (src/routes/auth.ts:22) [CALLS, 95%]
-
-→ Affected Processes: LoginFlow, TokenRefresh
-→ Risk: MEDIUM (3 processes)
-```
-
-## Risk Assessment
-
-| Affected | Risk |
-|----------|------|
-| <5 symbols, 1 cluster | LOW |
-| 5-15 symbols, 1-2 clusters | MEDIUM |
-| >15 symbols or 3+ clusters | HIGH |
-| Critical path (auth, payments) | CRITICAL |
-
-## Pre-Change Checklist
-```
-Before Committing:
-- [ ] Run impact analysis
-- [ ] Review all d=1 (WILL BREAK) items
-- [ ] Verify test coverage for affected processes
-- [ ] If risk > MEDIUM, get code review
-- [ ] If cross-cluster, coordinate with other teams
-```
-
-## Example: "What breaks if I change validateUser?"
-
-```
-1. gitnexus_impact({target: "validateUser", direction: "upstream", repo: "my-app"})
-   → d=1: loginHandler, apiMiddleware
-   → d=2: authRouter, sessionManager
-
-2. READ gitnexus://repo/my-app/clusters
-   → Auth and API clusters affected
-
-3. Decision: 2 direct callers, 2 clusters = MEDIUM risk
-```
+---
+name: gitnexus-impact-analysis
+description: Analyze blast radius before making code changes
+---
+
+# Impact Analysis
+
+## Quick Start
+```
+0. READ gitnexus://repos                                    → Discover indexed repos
+1. If "Index is stale" → gitnexus_analyze({repo: "my-app"})
+2. gitnexus_impact({target, direction: "upstream", repo: "my-app"}) → What depends on this
+3. READ gitnexus://repo/my-app/clusters                     → Check affected areas
+4. READ gitnexus://repo/my-app/processes                    → Affected execution flows
+```
+
+## When to Use
+- "Is it safe to change this function?"
+- "What will break if I modify X?"
+- "Show me the blast radius"
+- "Who uses this code?"
+
+## Understanding Output
+
+| Depth | Risk Level | Meaning |
+|-------|-----------|---------|
+| d=1 | WILL BREAK | Direct callers/importers |
+| d=2 | LIKELY AFFECTED | Indirect dependencies |
+| d=3 | MAY NEED TESTING | Transitive effects |
+
+## Workflow Checklist
+```
+Impact Analysis:
+- [ ] READ gitnexus://repos to find the right repo
+- [ ] gitnexus_impact(target, "upstream", repo) to find dependents
+- [ ] READ gitnexus://repo/{name}/clusters to understand affected areas
+- [ ] Check high-confidence (>0.8) dependencies first
+- [ ] Count affected clusters (cross-cutting = higher risk)
+- [ ] If >10 processes affected, consider splitting change
+```
+
+## Resource Reference
+
+### gitnexus://repo/{name}/clusters
+Check which clusters might be affected:
+```yaml
+clusters:
+  - name: Auth
+    symbols: 47
+  - name: API
+    symbols: 32
+```
+
+### gitnexus://repo/{name}/processes
+Find which processes touch the target:
+```yaml
+processes:
+  - name: LoginFlow
+    type: cross_community
+    steps: 5
+```
+
+## Tool Reference
+
+### gitnexus_impact
+Analyze blast radius:
+```
+gitnexus_impact({
+  target: "validateUser",
+  direction: "upstream",
+  minConfidence: 0.8,
+  maxDepth: 3,
+  repo: "my-app"
+})
+
+→ d=1 (WILL BREAK):
+  - loginHandler (src/auth/login.ts:42) [CALLS, 100%]
+  - apiMiddleware (src/api/middleware.ts:15) [CALLS, 100%]
+
+→ d=2 (LIKELY AFFECTED):
+  - authRouter (src/routes/auth.ts:22) [CALLS, 95%]
+
+→ Affected Processes: LoginFlow, TokenRefresh
+→ Risk: MEDIUM (3 processes)
+```
+
+## Risk Assessment
+
+| Affected | Risk |
+|----------|------|
+| <5 symbols, 1 cluster | LOW |
+| 5-15 symbols, 1-2 clusters | MEDIUM |
+| >15 symbols or 3+ clusters | HIGH |
+| Critical path (auth, payments) | CRITICAL |
+
+## Pre-Change Checklist
+```
+Before Committing:
+- [ ] Run impact analysis
+- [ ] Review all d=1 (WILL BREAK) items
+- [ ] Verify test coverage for affected processes
+- [ ] If risk > MEDIUM, get code review
+- [ ] If cross-cluster, coordinate with other teams
+```
+
+## Example: "What breaks if I change validateUser?"
+
+```
+1. gitnexus_impact({target: "validateUser", direction: "upstream", repo: "my-app"})
+   → d=1: loginHandler, apiMiddleware
+   → d=2: authRouter, sessionManager
+
+2. READ gitnexus://repo/my-app/clusters
+   → Auth and API clusters affected
+
+3. Decision: 2 direct callers, 2 clusters = MEDIUM risk
+```

package/skills/refactoring.md

@@ -1,120 +1,120 @@
----
-name: gitnexus-refactoring
-description: Plan safe refactors using blast radius and dependency mapping
----
-
-# Refactoring with GitNexus
-
-## Quick Start
-```
-0. READ gitnexus://repos                                    → Discover indexed repos
-1. If "Index is stale" → gitnexus_analyze({repo: "my-app"})
-2. gitnexus_impact({target, direction: "upstream", repo: "my-app"}) → Map all dependents
-3. READ gitnexus://repo/my-app/schema                       → Understand graph structure
-4. gitnexus_cypher({query: "...", repo: "my-app"})           → Find all references
-```
-
-## When to Use
-- "Rename this function safely"
-- "Extract this into a module"
-- "Split this service"
-- "Refactor without breaking things"
-
-## Checklists
-
-### Rename Symbol
-```
-Rename Refactoring:
-- [ ] gitnexus_impact({target: oldName, direction: "upstream", repo: "my-app"}) — find all callers
-- [ ] gitnexus_search({query: oldName, repo: "my-app"}) — find string literals
-- [ ] Check for reflection/dynamic references
-- [ ] Update in order: interface → implementation → usages
-- [ ] Run tests for affected processes
-```
-
-### Extract Module
-```
-Extract Module:
-- [ ] gitnexus_explore({name: target, type: "symbol", repo: "my-app"}) — map dependencies
-- [ ] gitnexus_impact({target, direction: "upstream", repo: "my-app"}) — find callers
-- [ ] READ gitnexus://repo/my-app/cluster/{name} — check cohesion
-- [ ] Define new module interface
-- [ ] Update imports across affected files
-```
-
-### Split Function
-```
-Split Function:
-- [ ] gitnexus_explore({name: target, type: "symbol", repo: "my-app"}) — understand callees
-- [ ] Group related logic
-- [ ] gitnexus_impact — verify callers won't break
-- [ ] Create new functions
-- [ ] Update callers
-```
-
-## Resource Reference
-
-### gitnexus://repo/{name}/schema
-Graph structure for Cypher queries:
-```yaml
-nodes: [Function, Class, Method, Community, Process]
-relationships: [CALLS, IMPORTS, EXTENDS, MEMBER_OF]
-
-example_queries:
-  find_callers: |
-    MATCH (caller)-[:CodeRelation {type: 'CALLS'}]->(f:Function {name: "X"})
-    RETURN caller.name
-```
-
-### gitnexus://repo/{name}/cluster/{clusterName}
-Check if extraction preserves cohesion:
-```yaml
-name: Payment
-cohesion: 92%
-members: [processPayment, validateCard, PaymentService]
-```
-
-## Tool Reference
-
-### Finding all references
-```cypher
-MATCH (caller)-[:CodeRelation {type: 'CALLS'}]->(f:Function {name: "validateUser"})
-RETURN caller.name, caller.filePath
-ORDER BY caller.filePath
-```
-
-### Finding imports of a module
-```cypher
-MATCH (importer)-[:CodeRelation {type: 'IMPORTS'}]->(f:File {name: "utils.ts"})
-RETURN importer.name, importer.filePath
-```
-
-## Example: Safely Rename `validateUser` to `authenticateUser`
-
-```
-1. gitnexus_impact({target: "validateUser", direction: "upstream", repo: "my-app"})
-   → loginHandler, apiMiddleware, testUtils
-
-2. gitnexus_search({query: "validateUser", repo: "my-app"})
-   → Found in: config.json (dynamic reference!)
-
-3. READ gitnexus://repo/my-app/processes
-   → LoginFlow, TokenRefresh, APIGateway
-
-4. Plan update order:
-   1. Update declaration in auth.ts
-   2. Update config.json string reference
-   3. Update loginHandler
-   4. Update apiMiddleware
-   5. Run tests for LoginFlow, TokenRefresh
-```
-
-## Refactoring Safety Rules
-
-| Risk Factor | Mitigation |
-|-------------|------------|
-| Many callers (>5) | Update in small batches |
-| Cross-cluster | Coordinate with other teams |
-| String references | Search for dynamic usage |
-| Reflection | Check for dynamic invocation |
-| External exports | May break downstream repos |
+---
+name: gitnexus-refactoring
+description: Plan safe refactors using blast radius and dependency mapping
+---
+
+# Refactoring with GitNexus
+
+## Quick Start
+```
+0. READ gitnexus://repos                                    → Discover indexed repos
+1. If "Index is stale" → gitnexus_analyze({repo: "my-app"})
+2. gitnexus_impact({target, direction: "upstream", repo: "my-app"}) → Map all dependents
+3. READ gitnexus://repo/my-app/schema                       → Understand graph structure
+4. gitnexus_cypher({query: "...", repo: "my-app"})           → Find all references
+```
+
+## When to Use
+- "Rename this function safely"
+- "Extract this into a module"
+- "Split this service"
+- "Refactor without breaking things"
+
+## Checklists
+
+### Rename Symbol
+```
+Rename Refactoring:
+- [ ] gitnexus_impact({target: oldName, direction: "upstream", repo: "my-app"}) — find all callers
+- [ ] gitnexus_search({query: oldName, repo: "my-app"}) — find string literals
+- [ ] Check for reflection/dynamic references
+- [ ] Update in order: interface → implementation → usages
+- [ ] Run tests for affected processes
+```
+
+### Extract Module
+```
+Extract Module:
+- [ ] gitnexus_explore({name: target, type: "symbol", repo: "my-app"}) — map dependencies
+- [ ] gitnexus_impact({target, direction: "upstream", repo: "my-app"}) — find callers
+- [ ] READ gitnexus://repo/my-app/cluster/{name} — check cohesion
+- [ ] Define new module interface
+- [ ] Update imports across affected files
+```
+
+### Split Function
+```
+Split Function:
+- [ ] gitnexus_explore({name: target, type: "symbol", repo: "my-app"}) — understand callees
+- [ ] Group related logic
+- [ ] gitnexus_impact — verify callers won't break
+- [ ] Create new functions
+- [ ] Update callers
+```
+
+## Resource Reference
+
+### gitnexus://repo/{name}/schema
+Graph structure for Cypher queries:
+```yaml
+nodes: [Function, Class, Method, Community, Process]
+relationships: [CALLS, IMPORTS, EXTENDS, MEMBER_OF]
+
+example_queries:
+  find_callers: |
+    MATCH (caller)-[:CodeRelation {type: 'CALLS'}]->(f:Function {name: "X"})
+    RETURN caller.name
+```
+
+### gitnexus://repo/{name}/cluster/{clusterName}
+Check if extraction preserves cohesion:
+```yaml
+name: Payment
+cohesion: 92%
+members: [processPayment, validateCard, PaymentService]
+```
+
+## Tool Reference
+
+### Finding all references
+```cypher
+MATCH (caller)-[:CodeRelation {type: 'CALLS'}]->(f:Function {name: "validateUser"})
+RETURN caller.name, caller.filePath
+ORDER BY caller.filePath
+```
+
+### Finding imports of a module
+```cypher
+MATCH (importer)-[:CodeRelation {type: 'IMPORTS'}]->(f:File {name: "utils.ts"})
+RETURN importer.name, importer.filePath
+```
+
+## Example: Safely Rename `validateUser` to `authenticateUser`
+
+```
+1. gitnexus_impact({target: "validateUser", direction: "upstream", repo: "my-app"})
+   → loginHandler, apiMiddleware, testUtils
+
+2. gitnexus_search({query: "validateUser", repo: "my-app"})
+   → Found in: config.json (dynamic reference!)
+
+3. READ gitnexus://repo/my-app/processes
+   → LoginFlow, TokenRefresh, APIGateway
+
+4. Plan update order:
+   1. Update declaration in auth.ts
+   2. Update config.json string reference
+   3. Update loginHandler
+   4. Update apiMiddleware
+   5. Run tests for LoginFlow, TokenRefresh
+```
+
+## Refactoring Safety Rules
+
+| Risk Factor | Mitigation |
+|-------------|------------|
+| Many callers (>5) | Update in small batches |
+| Cross-cluster | Coordinate with other teams |
+| String references | Search for dynamic usage |
+| Reflection | Check for dynamic invocation |
+| External exports | May break downstream repos |