@oomfware/cgr 0.1.5 → 0.1.6

package/README.md

@@ -65,8 +65,8 @@ Use `npx @oomfware/cgr ask <repo> <question>` to ask questions about external re
 - `npx @oomfware/cgr ask -m sonnet github.com/shadcn-ui/ui "How do I configure path aliases so components install to the right location?"`
 - `npx @oomfware/cgr ask github.com/facebook/react -w github.com/vercel/next.js "How does Next.js integrate with React's server components?"`
 
-cgr works best with detailed questions. Include file/folder paths when you know them, and reference
-details from previous answers in follow-ups.
+Broad questions work for getting oriented; detailed questions get precise answers. Include
+file/folder paths when you know them, and reference details from previous answers in follow-ups.
 
 Run `npx @oomfware/cgr --help` for more options.
 ```
@@ -92,8 +92,8 @@ Useful repositories:
 - `github.com/tailwindlabs/tailwindcss` for Tailwind internals, plugin API
 - `github.com/bluesky-social/atproto` for AT Protocol, Bluesky API
 
-cgr works best with detailed questions. Include file/folder paths when you know them, and reference
-details from previous answers in follow-ups.
+Broad questions work for getting oriented; detailed questions get precise answers. Include
+file/folder paths when you know them, and reference details from previous answers in follow-ups.
 
 Run `npx @oomfware/cgr --help` for more options.
 ```

package/dist/assets/system-prompt.md

@@ -41,35 +41,57 @@ citations only for general programming concepts unrelated to the codebase.
 
 Here are some ways to cite sources:
 
-1. Mention directories and key files inline—this is the baseline for any answer:
+1. Mention directories and key files inline, this is the baseline for any answer:
 
-   ```
-   The monorepo is organized into three tiers: services (`services/pds`, `services/bsky`)
-   provide runtime wrappers, business logic lives in `packages/pds` and `packages/bsky`,
-   and protocol infrastructure like `@atproto/lexicon` and `@atproto/xrpc` handles schema
-   validation and HTTP transport.
+   ```md
+   The monorepo is organized into three tiers: services (`services/pds`, `services/bsky`) provide
+   runtime wrappers, business logic lives in `packages/pds` and `packages/bsky`, and protocol
+   infrastructure like `@atproto/lexicon` and `@atproto/xrpc` handles schema validation and HTTP
+   transport.
    ```
 
 2. Reference file paths with line numbers in prose for specific claims:
 
-   ```
+   ```md
    As shown in `src/config/database.ts:12`, the connection pool defaults to 10.
    ```
 
-3. Add footnotes when making multiple claims that need sourcing:
+3. Reference files in section headers when covering multiple aspects:
+
+   ```md
+   ### Edge Case 5: Circular Peer Dependencies (`can-place-dep.js:370-371`, `place-dep.js:230-235`)
+
+   Arborist prevents infinite recursion when checking peer sets by tracking `peerPath`:
+
+       if (!peerEdge.peer || !peerEdge.to || peerPath.includes(peerEdge.to)) {
+         continue
+       }
+
+   And creates symbolic links when detecting nesting loops:
+
+       for (let p = target; p; p = p.resolveParent) {
+         if (p.matches(this.dep) && !p.isTop) {
+           this.placed = new Link({ parent: target, target: p });
 
+           return;
+         }
+       }
    ```
+
+4. Use footnotes when you have many citations to keep the prose flowing:
+
+   ```md
    The cache is invalidated whenever a user updates their profile. [^1]
 
-   [^1]: **`src/services/user.ts:89`** - updateProfile() calls cache.invalidate()
+   [^1]: `src/services/user.ts:89` - updateProfile() calls cache.invalidate()
    ```
 
-4. Include code snippets when they help illustrate the point:
+5. Include code snippets when they help illustrate the point:
 
-   ```
+   ```md
    Signals track dependencies automatically when accessed inside an effect:
 
-   **`packages/core/src/index.ts:152-158`**
+   `packages/core/src/index.ts:152-158`
 
        if (evalContext !== undefined) {
          let node = evalContext._sources;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@oomfware/cgr",
-  "version": "0.1.5",
+  "version": "0.1.6",
   "description": "ask questions about git repositories using Claude Code",
   "license": "0BSD",
   "repository": {

package/src/assets/system-prompt.md

@@ -41,35 +41,57 @@ citations only for general programming concepts unrelated to the codebase.
 
 Here are some ways to cite sources:
 
-1. Mention directories and key files inline—this is the baseline for any answer:
+1. Mention directories and key files inline, this is the baseline for any answer:
 
-   ```
-   The monorepo is organized into three tiers: services (`services/pds`, `services/bsky`)
-   provide runtime wrappers, business logic lives in `packages/pds` and `packages/bsky`,
-   and protocol infrastructure like `@atproto/lexicon` and `@atproto/xrpc` handles schema
-   validation and HTTP transport.
+   ```md
+   The monorepo is organized into three tiers: services (`services/pds`, `services/bsky`) provide
+   runtime wrappers, business logic lives in `packages/pds` and `packages/bsky`, and protocol
+   infrastructure like `@atproto/lexicon` and `@atproto/xrpc` handles schema validation and HTTP
+   transport.
    ```
 
 2. Reference file paths with line numbers in prose for specific claims:
 
-   ```
+   ```md
    As shown in `src/config/database.ts:12`, the connection pool defaults to 10.
    ```
 
-3. Add footnotes when making multiple claims that need sourcing:
+3. Reference files in section headers when covering multiple aspects:
+
+   ```md
+   ### Edge Case 5: Circular Peer Dependencies (`can-place-dep.js:370-371`, `place-dep.js:230-235`)
+
+   Arborist prevents infinite recursion when checking peer sets by tracking `peerPath`:
+
+       if (!peerEdge.peer || !peerEdge.to || peerPath.includes(peerEdge.to)) {
+         continue
+       }
+
+   And creates symbolic links when detecting nesting loops:
+
+       for (let p = target; p; p = p.resolveParent) {
+         if (p.matches(this.dep) && !p.isTop) {
+           this.placed = new Link({ parent: target, target: p });
 
+           return;
+         }
+       }
    ```
+
+4. Use footnotes when you have many citations to keep the prose flowing:
+
+   ```md
    The cache is invalidated whenever a user updates their profile. [^1]
 
-   [^1]: **`src/services/user.ts:89`** - updateProfile() calls cache.invalidate()
+   [^1]: `src/services/user.ts:89` - updateProfile() calls cache.invalidate()
    ```
 
-4. Include code snippets when they help illustrate the point:
+5. Include code snippets when they help illustrate the point:
 
-   ```
+   ```md
    Signals track dependencies automatically when accessed inside an effect:
 
-   **`packages/core/src/index.ts:152-158`**
+   `packages/core/src/index.ts:152-158`
 
        if (evalContext !== undefined) {
          let node = evalContext._sources;

package/src/commands/clean.ts

@@ -229,9 +229,7 @@ export const handler = async (args: Args): Promise<void> => {
 	const usePadding = maxNameLen + 2 + maxSizeLen + 6 <= termWidth;
 
 	const formatChoice = (name: string, size: number): string =>
-		usePadding
-			? `${name.padEnd(maxNameLen)}  ${formatSize(size)}`
-			: `${name} (${formatSize(size)})`;
+		usePadding ? `${name.padEnd(maxNameLen)}  ${formatSize(size)}` : `${name} (${formatSize(size)})`;
 
 	const choices: Choice[] = repos.map((repo) => ({
 		name: formatChoice(repo.displayPath, repo.size),