gitnexus 1.1.1 → 1.1.2

package/skills/exploring.md

@@ -1,126 +1,126 @@
----
-name: gitnexus-exploring
-description: Navigate unfamiliar code using GitNexus knowledge graph
----
-
-# Exploring Codebases
-
-## Quick Start
-```
-0. READ gitnexus://repos            → Discover indexed repos (use repo param if multiple)
-1. If "Index is stale" → gitnexus_analyze({repo: "my-app"})
-2. READ gitnexus://repo/{name}/context        → Get codebase overview (~150 tokens)
-3. READ gitnexus://repo/{name}/clusters       → See all functional clusters
-4. READ gitnexus://repo/{name}/cluster/{name} → Deep dive on specific cluster
-```
-
-## When to Use
-- "How does authentication work?"
-- "What's the project structure?"
-- "Show me the main components"
-- "Where is the database logic?"
-
-## Workflow Checklist
-```
-Exploration Progress:
-- [ ] READ gitnexus://repos to discover available repos
-- [ ] READ gitnexus://repo/{name}/context for codebase overview
-- [ ] READ gitnexus://repo/{name}/clusters to list all clusters
-- [ ] Identify the relevant cluster by name
-- [ ] READ gitnexus://repo/{name}/cluster/{name} for cluster details
-- [ ] Use gitnexus_explore for specific symbols
-```
-
-## Resource Reference
-
-### gitnexus://repos
-Discover all indexed repositories. **Read first.**
-```yaml
-repos:
-  - name: "my-app"
-    path: "/home/user/my-app"
-    files: 42
-    symbols: 918
-```
-
-### gitnexus://repo/{name}/context
-Codebase overview for a specific repo.
-```yaml
-project: my-app
-stats:
-  files: 42
-  symbols: 918
-  clusters: 12
-  processes: 45
-tools_available: [list_repos, search, explore, impact, overview, cypher]
-```
-
-### gitnexus://repo/{name}/clusters
-All functional clusters with cohesion scores.
-```yaml
-clusters:
-  - name: "Auth"
-    symbols: 47
-    cohesion: 92%
-  - name: "Database"
-    symbols: 32
-    cohesion: 88%
-```
-
-### gitnexus://repo/{name}/cluster/{clusterName}
-Members of a specific cluster.
-```yaml
-name: Auth
-symbols: 47
-cohesion: 92%
-members:
-  - name: validateUser
-    type: Function
-    file: src/auth/validator.ts
-```
-
-### gitnexus://repo/{name}/process/{processName}
-Full execution trace.
-```yaml
-name: LoginFlow
-type: cross_community
-steps:
-  1: handleLogin (src/auth/handler.ts)
-  2: validateUser (src/auth/validator.ts)
-  3: createSession (src/auth/session.ts)
-```
-
-## Tool Reference (When Resources Aren't Enough)
-
-### gitnexus_explore
-For detailed symbol context with callers/callees:
-```
-gitnexus_explore({name: "validateUser", type: "symbol", repo: "my-app"})
-→ Callers: loginHandler, apiMiddleware
-→ Callees: checkToken, getUserById
-```
-
-### gitnexus_search
-For finding code by query:
-```
-gitnexus_search({query: "payment validation", depth: "full", repo: "my-app"})
-```
-
-## Example: "How does payment processing work?"
-
-```
-1. READ gitnexus://repos
-   → Repos: my-app (918 symbols)
-
-2. READ gitnexus://repo/my-app/context
-   → 918 symbols, 12 clusters
-
-3. READ gitnexus://repo/my-app/clusters
-   → Clusters: Auth, Payment, Database, API...
-
-4. READ gitnexus://repo/my-app/cluster/Payment
-   → Members: processPayment, validateCard, PaymentService
-
-5. READ gitnexus://repo/my-app/process/CheckoutFlow
-   → handleCheckout → validateCart → processPayment → sendConfirmation
-```
+---
+name: gitnexus-exploring
+description: Navigate unfamiliar code using GitNexus knowledge graph
+---
+
+# Exploring Codebases
+
+## Quick Start
+```
+0. READ gitnexus://repos            → Discover indexed repos (use repo param if multiple)
+1. If "Index is stale" → gitnexus_analyze({repo: "my-app"})
+2. READ gitnexus://repo/{name}/context        → Get codebase overview (~150 tokens)
+3. READ gitnexus://repo/{name}/clusters       → See all functional clusters
+4. READ gitnexus://repo/{name}/cluster/{name} → Deep dive on specific cluster
+```
+
+## When to Use
+- "How does authentication work?"
+- "What's the project structure?"
+- "Show me the main components"
+- "Where is the database logic?"
+
+## Workflow Checklist
+```
+Exploration Progress:
+- [ ] READ gitnexus://repos to discover available repos
+- [ ] READ gitnexus://repo/{name}/context for codebase overview
+- [ ] READ gitnexus://repo/{name}/clusters to list all clusters
+- [ ] Identify the relevant cluster by name
+- [ ] READ gitnexus://repo/{name}/cluster/{name} for cluster details
+- [ ] Use gitnexus_explore for specific symbols
+```
+
+## Resource Reference
+
+### gitnexus://repos
+Discover all indexed repositories. **Read first.**
+```yaml
+repos:
+  - name: "my-app"
+    path: "/home/user/my-app"
+    files: 42
+    symbols: 918
+```
+
+### gitnexus://repo/{name}/context
+Codebase overview for a specific repo.
+```yaml
+project: my-app
+stats:
+  files: 42
+  symbols: 918
+  clusters: 12
+  processes: 45
+tools_available: [list_repos, search, explore, impact, overview, cypher]
+```
+
+### gitnexus://repo/{name}/clusters
+All functional clusters with cohesion scores.
+```yaml
+clusters:
+  - name: "Auth"
+    symbols: 47
+    cohesion: 92%
+  - name: "Database"
+    symbols: 32
+    cohesion: 88%
+```
+
+### gitnexus://repo/{name}/cluster/{clusterName}
+Members of a specific cluster.
+```yaml
+name: Auth
+symbols: 47
+cohesion: 92%
+members:
+  - name: validateUser
+    type: Function
+    file: src/auth/validator.ts
+```
+
+### gitnexus://repo/{name}/process/{processName}
+Full execution trace.
+```yaml
+name: LoginFlow
+type: cross_community
+steps:
+  1: handleLogin (src/auth/handler.ts)
+  2: validateUser (src/auth/validator.ts)
+  3: createSession (src/auth/session.ts)
+```
+
+## Tool Reference (When Resources Aren't Enough)
+
+### gitnexus_explore
+For detailed symbol context with callers/callees:
+```
+gitnexus_explore({name: "validateUser", type: "symbol", repo: "my-app"})
+→ Callers: loginHandler, apiMiddleware
+→ Callees: checkToken, getUserById
+```
+
+### gitnexus_search
+For finding code by query:
+```
+gitnexus_search({query: "payment validation", depth: "full", repo: "my-app"})
+```
+
+## Example: "How does payment processing work?"
+
+```
+1. READ gitnexus://repos
+   → Repos: my-app (918 symbols)
+
+2. READ gitnexus://repo/my-app/context
+   → 918 symbols, 12 clusters
+
+3. READ gitnexus://repo/my-app/clusters
+   → Clusters: Auth, Payment, Database, API...
+
+4. READ gitnexus://repo/my-app/cluster/Payment
+   → Members: processPayment, validateCard, PaymentService
+
+5. READ gitnexus://repo/my-app/process/CheckoutFlow
+   → handleCheckout → validateCart → processPayment → sendConfirmation
+```

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
+```