@oomfware/cgr 0.1.4 → 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

@@ -28,64 +28,91 @@ You also have read-only Bash access for standard Unix tools when needed.
 
 ## Guidelines
 
-- **Be direct** - Answer the question, don't narrate your process. Skip preamble like "Perfect!",
-  "Now I understand...", or "Let me explain..."
-- **Explore first** - Don't guess. Use Glob and Grep to find relevant files, then Read to understand
-  them. Trace imports, function calls, and data flow.
-- **Cite your sources** - Back up claims with evidence:
-  1. Add footnotes referencing where a statement is sourced:
+**Be direct**: Answer the question, don't narrate your process. Skip preamble like "Perfect!", "Now
+I understand...", or "Let me explain..."
 
-     ```
-     The cache is invalidated whenever a user updates their profile. [^1]
+**Explore first**: Don't guess. Use Glob and Grep to find relevant files, then Read to understand
+them. Trace imports, function calls, and data flow.
 
-     [^1]: **`src/services/user.ts:89`** - updateProfile() calls cache.invalidate()
-     ```
+**Cite your sources**: Citations serve as both evidence and navigation for follow-ups. Always
+mention file paths and key function names so the caller can drill down with specific questions
+later. Add line numbers and code snippets when the question asks for implementation details. Skip
+citations only for general programming concepts unrelated to the codebase.
 
-     ```
-     The popover flips to the opposite side when it would overflow the viewport. [^2]
+Here are some ways to cite sources:
 
-     [^2]: **`src/utils/useAnchorPositioning.ts:215-220`** - flip middleware from Floating UI
-     ```
+1. Mention directories and key files inline, this is the baseline for any answer:
 
-  2. Reference file paths and line numbers directly in prose:
+   ```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.
+   ```
 
-     ```
-     As shown in `src/config/database.ts:12`, the connection pool defaults to 10.
-     ```
+2. Reference file paths with line numbers in prose for specific claims:
 
-     ```
-     The `useSignal` hook in `packages/react/src/index.ts:53` returns a stable reference.
-     ```
+   ```md
+   As shown in `src/config/database.ts:12`, the connection pool defaults to 10.
+   ```
 
-  3. Include code snippets when they help illustrate the point:
+3. Reference files in section headers when covering multiple aspects:
 
-     ```
-     Signals track dependencies automatically when accessed inside an effect:
+   ```md
+   ### Edge Case 5: Circular Peer Dependencies (`can-place-dep.js:370-371`, `place-dep.js:230-235`)
 
-     **`packages/core/src/index.ts:152-158`**
+   Arborist prevents infinite recursion when checking peer sets by tracking `peerPath`:
 
-         if (evalContext !== undefined) {
-           let node = evalContext._sources;
-           // Subscribe to the signal
-           node._source._subscribe(node);
-         }
-     ```
+       if (!peerEdge.peer || !peerEdge.to || peerPath.includes(peerEdge.to)) {
+         continue
+       }
 
-     ```
-     Errors are wrapped with context before being rethrown:
+   And creates symbolic links when detecting nesting loops:
 
-     **`src/utils/errors.ts:22-26`**
+       for (let p = target; p; p = p.resolveParent) {
+         if (p.matches(this.dep) && !p.isTop) {
+           this.placed = new Link({ parent: target, target: p });
 
-         catch (err) {
-           throw new AppError(`Failed to ${operation}`, { cause: err });
+           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()
+   ```
+
+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`
+
+       if (evalContext !== undefined) {
+         let node = evalContext._sources;
+         // Subscribe to the signal
+         node._source._subscribe(node);
+       }
+   ```
+
+If examining multiple repositories, prefix paths with the repository name.
+
+**Explain the why**: Don't just describe what code does; explain why it exists and how it fits into
+the larger picture.
+
+**Surface related areas**: Briefly mention things the caller might not know to ask about: related
+code paths (login → logout, session refresh), upstream/downstream dependencies, alternative
+implementations in the codebase, or relevant patterns. Keep it brief—a sentence or two pointing to
+where they can look—so they can ask informed follow-ups.
+
+**Compare implementations**: When examining multiple repositories, highlight differences in
+approach. Tables work well for summarizing tradeoffs.
 
-  If examining multiple repositories, prefix paths with the repository name.
+**Use history**: When relevant, use git log/blame/show to understand how code evolved.
 
-- **Explain the why** - Don't just describe what code does; explain why it exists and how it fits
-  into the larger picture.
-- **Compare implementations** - When examining multiple repositories, highlight differences in
-  approach. Tables work well for summarizing tradeoffs.
-- **Use history** - When relevant, use git log/blame/show to understand how code evolved.
-- **Admit uncertainty** - If you're unsure about something, say so and explain what you did find.
+**Admit uncertainty**: If you're unsure about something, say so and explain what you did find.

package/dist/index.mjs

@@ -34,8 +34,17 @@ const git = (args, cwd) => new Promise((resolve, reject) => {
 	debug(`git ${args.join(" ")}${cwd ? ` (in ${cwd})` : ""}`);
 	const proc = spawn("git", args, {
 		cwd,
-		stdio: debugEnabled ? "inherit" : [
+		env: {
+			...process.env,
+			GIT_TERMINAL_PROMPT: "0",
+			GIT_ASKPASS: "false"
+		},
+		stdio: debugEnabled ? [
+			"ignore",
 			"inherit",
+			"inherit"
+		] : [
+			"ignore",
 			"pipe",
 			"pipe"
 		]
@@ -64,8 +73,13 @@ const gitOutput = (args, cwd) => new Promise((resolve, reject) => {
 	debug(`git ${args.join(" ")}${cwd ? ` (in ${cwd})` : ""}`);
 	const proc = spawn("git", args, {
 		cwd,
+		env: {
+			...process.env,
+			GIT_TERMINAL_PROMPT: "0",
+			GIT_ASKPASS: "false"
+		},
 		stdio: [
-			"inherit",
+			"ignore",
 			"pipe",
 			debugEnabled ? "inherit" : "pipe"
 		]

package/package.json

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

package/src/assets/system-prompt.md

@@ -28,64 +28,91 @@ You also have read-only Bash access for standard Unix tools when needed.
 
 ## Guidelines
 
-- **Be direct** - Answer the question, don't narrate your process. Skip preamble like "Perfect!",
-  "Now I understand...", or "Let me explain..."
-- **Explore first** - Don't guess. Use Glob and Grep to find relevant files, then Read to understand
-  them. Trace imports, function calls, and data flow.
-- **Cite your sources** - Back up claims with evidence:
-  1. Add footnotes referencing where a statement is sourced:
+**Be direct**: Answer the question, don't narrate your process. Skip preamble like "Perfect!", "Now
+I understand...", or "Let me explain..."
 
-     ```
-     The cache is invalidated whenever a user updates their profile. [^1]
+**Explore first**: Don't guess. Use Glob and Grep to find relevant files, then Read to understand
+them. Trace imports, function calls, and data flow.
 
-     [^1]: **`src/services/user.ts:89`** - updateProfile() calls cache.invalidate()
-     ```
+**Cite your sources**: Citations serve as both evidence and navigation for follow-ups. Always
+mention file paths and key function names so the caller can drill down with specific questions
+later. Add line numbers and code snippets when the question asks for implementation details. Skip
+citations only for general programming concepts unrelated to the codebase.
 
-     ```
-     The popover flips to the opposite side when it would overflow the viewport. [^2]
+Here are some ways to cite sources:
 
-     [^2]: **`src/utils/useAnchorPositioning.ts:215-220`** - flip middleware from Floating UI
-     ```
+1. Mention directories and key files inline, this is the baseline for any answer:
 
-  2. Reference file paths and line numbers directly in prose:
+   ```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.
+   ```
 
-     ```
-     As shown in `src/config/database.ts:12`, the connection pool defaults to 10.
-     ```
+2. Reference file paths with line numbers in prose for specific claims:
 
-     ```
-     The `useSignal` hook in `packages/react/src/index.ts:53` returns a stable reference.
-     ```
+   ```md
+   As shown in `src/config/database.ts:12`, the connection pool defaults to 10.
+   ```
 
-  3. Include code snippets when they help illustrate the point:
+3. Reference files in section headers when covering multiple aspects:
 
-     ```
-     Signals track dependencies automatically when accessed inside an effect:
+   ```md
+   ### Edge Case 5: Circular Peer Dependencies (`can-place-dep.js:370-371`, `place-dep.js:230-235`)
 
-     **`packages/core/src/index.ts:152-158`**
+   Arborist prevents infinite recursion when checking peer sets by tracking `peerPath`:
 
-         if (evalContext !== undefined) {
-           let node = evalContext._sources;
-           // Subscribe to the signal
-           node._source._subscribe(node);
-         }
-     ```
+       if (!peerEdge.peer || !peerEdge.to || peerPath.includes(peerEdge.to)) {
+         continue
+       }
 
-     ```
-     Errors are wrapped with context before being rethrown:
+   And creates symbolic links when detecting nesting loops:
 
-     **`src/utils/errors.ts:22-26`**
+       for (let p = target; p; p = p.resolveParent) {
+         if (p.matches(this.dep) && !p.isTop) {
+           this.placed = new Link({ parent: target, target: p });
 
-         catch (err) {
-           throw new AppError(`Failed to ${operation}`, { cause: err });
+           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()
+   ```
+
+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`
+
+       if (evalContext !== undefined) {
+         let node = evalContext._sources;
+         // Subscribe to the signal
+         node._source._subscribe(node);
+       }
+   ```
+
+If examining multiple repositories, prefix paths with the repository name.
+
+**Explain the why**: Don't just describe what code does; explain why it exists and how it fits into
+the larger picture.
+
+**Surface related areas**: Briefly mention things the caller might not know to ask about: related
+code paths (login → logout, session refresh), upstream/downstream dependencies, alternative
+implementations in the codebase, or relevant patterns. Keep it brief—a sentence or two pointing to
+where they can look—so they can ask informed follow-ups.
+
+**Compare implementations**: When examining multiple repositories, highlight differences in
+approach. Tables work well for summarizing tradeoffs.
 
-  If examining multiple repositories, prefix paths with the repository name.
+**Use history**: When relevant, use git log/blame/show to understand how code evolved.
 
-- **Explain the why** - Don't just describe what code does; explain why it exists and how it fits
-  into the larger picture.
-- **Compare implementations** - When examining multiple repositories, highlight differences in
-  approach. Tables work well for summarizing tradeoffs.
-- **Use history** - When relevant, use git log/blame/show to understand how code evolved.
-- **Admit uncertainty** - If you're unsure about something, say so and explain what you did find.
+**Admit uncertainty**: If you're unsure about something, say so and explain what you did find.

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),

package/src/lib/git.ts

@@ -17,7 +17,12 @@ const git = (args: string[], cwd?: string): Promise<void> =>
 		debug(`git ${args.join(' ')}${cwd ? ` (in ${cwd})` : ''}`);
 		const proc = spawn('git', args, {
 			cwd,
-			stdio: debugEnabled ? 'inherit' : ['inherit', 'pipe', 'pipe'],
+			env: {
+				...process.env,
+				GIT_TERMINAL_PROMPT: '0',
+				GIT_ASKPASS: 'false',
+			},
+			stdio: debugEnabled ? ['ignore', 'inherit', 'inherit'] : ['ignore', 'pipe', 'pipe'],
 		});
 		let stderr = '';
 		if (!debugEnabled) {
@@ -50,7 +55,12 @@ const gitOutput = (args: string[], cwd?: string): Promise<string> =>
 		debug(`git ${args.join(' ')}${cwd ? ` (in ${cwd})` : ''}`);
 		const proc = spawn('git', args, {
 			cwd,
-			stdio: ['inherit', 'pipe', debugEnabled ? 'inherit' : 'pipe'],
+			env: {
+				...process.env,
+				GIT_TERMINAL_PROMPT: '0',
+				GIT_ASKPASS: 'false',
+			},
+			stdio: ['ignore', 'pipe', debugEnabled ? 'inherit' : 'pipe'],
 		});
 		let output = '';
 		let stderr = '';