get-shit-done-cc 1.9.1 → 1.9.2

package/commands/gsd/query-intel.md

@@ -1,128 +0,0 @@
----
-name: gsd:query-intel
-description: Query codebase intelligence graph for dependencies and hotspots
-argument-hint: "<dependents|hotspots> [file-path]"
-allowed-tools:
-  - Bash
----
-
-<objective>
-Query the codebase intelligence graph database for relationship information.
-
-**Query types:**
-- `dependents <file>` — What files depend on this file? (blast radius)
-- `hotspots` — Which files have the most dependents? (change carefully)
-
-Output: Formatted query results from graph.db
-</objective>
-
-<context>
-This command exposes the graph query capabilities built by Phase 4 (Semantic Intelligence).
-
-**Use for:**
-- Checking blast radius before refactoring a core file
-- Identifying high-impact files that need careful changes
-- Understanding dependency relationships in the codebase
-
-**Requires:** `.planning/intel/graph.db` (created by `/gsd:analyze-codebase` with entity generation)
-
-If graph.db doesn't exist, the command will return an error suggesting to run analyze-codebase first.
-</context>
-
-<process>
-
-## Step 1: Parse arguments
-
-Extract query type and optional file path from arguments.
-
-**Arguments:** $ARGUMENTS
-
-**Expected formats:**
-- `dependents src/lib/db.ts` — query what depends on this file
-- `hotspots` — query most-depended-on files
-- `hotspots 10` — query top 10 hotspots (default: 5)
-
-## Step 2: Convert file path to entity ID
-
-For `dependents` queries, convert the file path to entity ID format:
-- `src/lib/db.ts` → `src-lib-db`
-- Replace `/` with `-`, remove extension
-
-```bash
-# Example conversion
-FILE_PATH="src/lib/db.ts"
-ENTITY_ID=$(echo "$FILE_PATH" | sed 's/\.[^.]*$//' | tr '/' '-')
-```
-
-## Step 3: Execute query
-
-Run the appropriate query against the graph database:
-
-**For dependents:**
-```bash
-echo '{"action":"query","type":"dependents","target":"'$ENTITY_ID'","limit":20}' | node hooks/gsd-intel-index.js
-```
-
-**For hotspots:**
-```bash
-echo '{"action":"query","type":"hotspots","limit":5}' | node hooks/gsd-intel-index.js
-```
-
-## Step 4: Format and present results
-
-Parse the JSON response and present in readable format.
-
-**For dependents:**
-```
-## Files that depend on {file-path}
-
-Found {count} dependents:
-
-1. src/api/users.ts
-2. src/api/auth.ts
-3. src/services/payment.ts
-...
-
-**Blast radius:** {count} files would be affected by changes.
-```
-
-**For hotspots:**
-```
-## Dependency Hotspots
-
-These files have the most dependents — change carefully:
-
-| Rank | File | Dependents |
-|------|------|------------|
-| 1 | src/lib/db.ts | 42 |
-| 2 | src/types/user.ts | 35 |
-| 3 | src/utils/format.ts | 28 |
-```
-
-## Step 5: Handle errors
-
-**If graph.db doesn't exist:**
-```
-No graph database found at .planning/intel/graph.db
-
-Run /gsd:analyze-codebase first to build the dependency graph.
-```
-
-**If entity not found:**
-```
-No entity found for: {file-path}
-
-The file may not be indexed yet. Try:
-- /gsd:analyze-codebase to rebuild the index
-- Check the file path is correct
-```
-
-</process>
-
-<success_criteria>
-- [ ] Query type parsed from arguments
-- [ ] File path converted to entity ID (for dependents)
-- [ ] Query executed against graph.db
-- [ ] Results formatted in readable markdown
-- [ ] Errors handled gracefully with helpful messages
-</success_criteria>

package/get-shit-done/templates/entity.md

@@ -1,173 +0,0 @@
-# Entity Template
-
-Template for `.planning/codebase/{entity-slug}.md` - file-level intelligence documentation.
-
----
-
-## File Template
-
-```markdown
----
-path: {path}
-type: {type}
-updated: {updated}
-status: {status}
----
-
-# {filename}
-
-## Purpose
-
-{purpose}
-
-## Exports
-
-{exports}
-
-## Dependencies
-
-{dependencies}
-
-## Used By
-
-{used_by}
-
-## Notes
-
-{notes}
-```
-
----
-
-## Field Reference
-
-### Frontmatter
-
-| Field | Values | Description |
-|-------|--------|-------------|
-| `path` | Absolute path | Full path to the file |
-| `type` | module, component, util, config, test, api, hook | Primary classification |
-| `updated` | YYYY-MM-DD | Last time this entity was updated |
-| `status` | active, deprecated, stub | Current state |
-
-### Sections
-
-**Purpose** (required)
-1-3 sentences covering:
-- What this file does
-- Why it exists
-- Who/what uses it (high-level)
-
-**Exports** (required for modules with exports)
-List each export with signature and description:
-```markdown
-- `functionName(arg: Type): ReturnType` - What it does
-- `ClassName` - What it represents
-- `CONSTANT_NAME` - What value it holds
-```
-
-For files without exports (config, tests), write "None" or describe what the file defines.
-
-**Dependencies** (required)
-Internal dependencies use wiki-links (slugified paths):
-```markdown
-- [[src-lib-db]] - Database client
-- [[src-types-user]] - User type definitions
-```
-
-External dependencies use plain text:
-```markdown
-- react - Component framework
-- jose - JWT handling
-```
-
-**Used By** (grows over time)
-Files that import this one, using wiki-links:
-```markdown
-- [[src-app-api-auth-route]]
-- [[src-components-dashboard]]
-```
-
-Initially may be empty or incomplete. Updated as Claude encounters imports.
-
-**Notes** (optional)
-Patterns, gotchas, or context:
-```markdown
-- Uses singleton pattern for connection pooling
-- WARNING: Must call `init()` before any other method
-- Related: See [[src-lib-cache]] for caching layer
-```
-
----
-
-## Slug Convention
-
-Entity slugs are derived from file paths:
-- `src/lib/db.ts` becomes `src-lib-db`
-- `src/app/api/auth/route.ts` becomes `src-app-api-auth-route`
-
-Rule: Replace `/` and `.` with `-`, drop file extension.
-
----
-
-## Example
-
-```markdown
----
-path: /project/src/lib/auth.ts
-type: util
-updated: 2025-01-15
-status: active
----
-
-# auth.ts
-
-## Purpose
-
-JWT token management using jose library. Handles token creation, verification, and refresh rotation. Used by all protected API routes via middleware.
-
-## Exports
-
-- `createAccessToken(userId: string): Promise<string>` - Creates 15-min access token
-- `createRefreshToken(userId: string): Promise<string>` - Creates 7-day refresh token
-- `verifyToken(token: string): Promise<TokenPayload>` - Validates and decodes token
-- `rotateRefresh(oldToken: string): Promise<TokenPair>` - Issues new token pair
-
-## Dependencies
-
-- [[src-lib-db]] - Stores refresh tokens for revocation
-- [[src-types-auth]] - TokenPayload, TokenPair types
-- jose - JWT signing and verification
-- bcrypt - Password hashing
-
-## Used By
-
-- [[src-middleware]]
-- [[src-app-api-auth-login-route]]
-- [[src-app-api-auth-logout-route]]
-- [[src-app-api-auth-refresh-route]]
-
-## Notes
-
-- Access tokens are stateless; refresh tokens stored in DB for revocation
-- Uses RS256 algorithm with keys from environment
-- WARNING: Never log token values, even in debug mode
-```
-
----
-
-## Guidelines
-
-**When to create/update:**
-- After modifying a file during plan execution
-- When encountering a file that lacks documentation
-- When relationships change (new imports, exports)
-
-**Minimal viable entity:**
-At minimum, an entity needs frontmatter + Purpose. Other sections can be "TBD" if unknown.
-
-**Accuracy over completeness:**
-Better to have partial accurate info than complete guesses. Mark unknowns explicitly.
-
-**Link discovery:**
-The hook that processes entities extracts all `[[wiki-links]]` to build the relationship graph. Ensure links use correct slug format.