@oomfware/cgr 0.1.3 → 0.1.5

package/dist/assets/system-prompt.md

@@ -28,62 +28,69 @@ You also have read-only Bash access for standard Unix tools when needed.
 
 ## Guidelines
 
-- **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:
+   ```
+   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.
-     ```
+   ```
+   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. Add footnotes when making multiple claims that need sourcing:
 
-     ```
-     Signals track dependencies automatically when accessed inside an effect:
+   ```
+   The cache is invalidated whenever a user updates their profile. [^1]
 
-     **`packages/core/src/index.ts:152-158`**
+   [^1]: **`src/services/user.ts:89`** - updateProfile() calls cache.invalidate()
+   ```
 
-         if (evalContext !== undefined) {
-           let node = evalContext._sources;
-           // Subscribe to the signal
-           node._source._subscribe(node);
-         }
-     ```
+4. Include code snippets when they help illustrate the point:
 
-     ```
-     Errors are wrapped with context before being rethrown:
+   ```
+   Signals track dependencies automatically when accessed inside an effect:
 
-     **`src/utils/errors.ts:22-26`**
+   **`packages/core/src/index.ts:152-158`**
 
-         catch (err) {
-           throw new AppError(`Failed to ${operation}`, { cause: err });
-         }
-     ```
+       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.
+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.
-- **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.
+**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.
+
+**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.

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"
 		]
@@ -382,7 +396,7 @@ const spawnClaude = (cwd, contextPrompt, args) => new Promise((resolve, reject)
 		"--append-system-prompt",
 		contextPrompt
 	];
-	console.error("spawning claude...");
+	console.error("summoning claude...");
 	const claude = spawn("claude", claudeArgs, {
 		cwd,
 		stdio: "inherit"
@@ -587,17 +601,25 @@ const handler = async (args) => {
 		console.log("no cached data found");
 		return;
 	}
+	const maxNameLen = Math.max(...repos.map((r) => r.displayPath.length), sessionsExist ? 10 : 0);
+	const maxSizeLen = Math.max(...repos.map((r) => formatSize(r.size).length), sessionsExist ? formatSize(sessionsSize).length : 0);
+	const termWidth = process.stdout.columns ?? 80;
+	const usePadding = maxNameLen + 2 + maxSizeLen + 6 <= termWidth;
+	const formatChoice = (name, size) => usePadding ? `${name.padEnd(maxNameLen)}  ${formatSize(size)}` : `${name} (${formatSize(size)})`;
 	const choices = repos.map((repo) => ({
-		name: `${repo.displayPath.padEnd(50)} ${formatSize(repo.size)}`,
-		value: repo.path
+		name: formatChoice(repo.displayPath, repo.size),
+		value: repo.path,
+		short: repo.displayPath
 	}));
 	if (sessionsExist && sessionsSize > 0) choices.push({
-		name: `${"(sessions)".padEnd(50)} ${formatSize(sessionsSize)}`,
-		value: sessionsDir
+		name: formatChoice("(sessions)", sessionsSize),
+		value: sessionsDir,
+		short: "(sessions)"
 	});
 	const selected = await checkbox({
 		message: "select items to remove",
-		choices
+		choices,
+		pageSize: 20
 	});
 	if (selected.length === 0) return;
 	let totalSize = 0;

package/package.json

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

package/src/assets/system-prompt.md

@@ -28,62 +28,69 @@ You also have read-only Bash access for standard Unix tools when needed.
 
 ## Guidelines
 
-- **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:
+   ```
+   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.
-     ```
+   ```
+   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. Add footnotes when making multiple claims that need sourcing:
 
-     ```
-     Signals track dependencies automatically when accessed inside an effect:
+   ```
+   The cache is invalidated whenever a user updates their profile. [^1]
 
-     **`packages/core/src/index.ts:152-158`**
+   [^1]: **`src/services/user.ts:89`** - updateProfile() calls cache.invalidate()
+   ```
 
-         if (evalContext !== undefined) {
-           let node = evalContext._sources;
-           // Subscribe to the signal
-           node._source._subscribe(node);
-         }
-     ```
+4. Include code snippets when they help illustrate the point:
 
-     ```
-     Errors are wrapped with context before being rethrown:
+   ```
+   Signals track dependencies automatically when accessed inside an effect:
 
-     **`src/utils/errors.ts:22-26`**
+   **`packages/core/src/index.ts:152-158`**
 
-         catch (err) {
-           throw new AppError(`Failed to ${operation}`, { cause: err });
-         }
-     ```
+       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.
+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.
-- **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.
+**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.
+
+**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.

package/src/commands/ask.ts

@@ -133,7 +133,7 @@ const spawnClaude = (cwd: string, contextPrompt: string, args: Args): Promise<nu
 			contextPrompt,
 		];
 
-		console.error('spawning claude...');
+		console.error('summoning claude...');
 		const claude = spawn('claude', claudeArgs, {
 			cwd,
 			stdio: 'inherit',

package/src/commands/clean.ts

@@ -21,6 +21,12 @@ export const schema = object({
 
 export type Args = InferValue<typeof schema>;
 
+type Choice = {
+	name: string;
+	value: string;
+	short: string;
+};
+
 /**
  * checks if a path exists.
  * @param path the path to check
@@ -209,21 +215,42 @@ export const handler = async (args: Args): Promise<void> => {
 	}
 
 	// build choices for checkbox
-	const choices: { name: string; value: string }[] = repos.map((repo) => ({
-		name: `${repo.displayPath.padEnd(50)} ${formatSize(repo.size)}`,
+	const maxNameLen = Math.max(
+		...repos.map((r) => r.displayPath.length),
+		sessionsExist ? '(sessions)'.length : 0,
+	);
+	const maxSizeLen = Math.max(
+		...repos.map((r) => formatSize(r.size).length),
+		sessionsExist ? formatSize(sessionsSize).length : 0,
+	);
+
+	// checkbox prefix is ~4 chars, leave some margin
+	const termWidth = process.stdout.columns ?? 80;
+	const usePadding = maxNameLen + 2 + maxSizeLen + 6 <= termWidth;
+
+	const formatChoice = (name: string, size: number): string =>
+		usePadding
+			? `${name.padEnd(maxNameLen)}  ${formatSize(size)}`
+			: `${name} (${formatSize(size)})`;
+
+	const choices: Choice[] = repos.map((repo) => ({
+		name: formatChoice(repo.displayPath, repo.size),
 		value: repo.path,
+		short: repo.displayPath,
 	}));
 
 	if (sessionsExist && sessionsSize > 0) {
 		choices.push({
-			name: `${'(sessions)'.padEnd(50)} ${formatSize(sessionsSize)}`,
+			name: formatChoice('(sessions)', sessionsSize),
 			value: sessionsDir,
+			short: '(sessions)',
 		});
 	}
 
 	const selected = await checkbox({
 		message: 'select items to remove',
 		choices,
+		pageSize: 20,
 	});
 
 	if (selected.length === 0) {

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 = '';