@oh-my-pi/pi-coding-agent 4.0.1 → 4.2.0

package/src/core/tools/rulebook.ts

@@ -1,132 +0,0 @@
-/**
- * Rulebook Tool
- *
- * Allows the agent to fetch full content of rules that have descriptions.
- * Rules are listed in the system prompt with name + description; this tool
- * retrieves the complete rule content on demand.
- */
-
-import type { AgentTool } from "@oh-my-pi/pi-agent-core";
-import { Type } from "@sinclair/typebox";
-import type { Rule } from "../../capability/rule";
-import type { ToolSession } from "./index";
-
-export interface RulebookToolDetails {
-	type: "rulebook";
-	ruleName: string;
-	found: boolean;
-	content?: string;
-}
-
-const rulebookSchema = Type.Object({
-	name: Type.String({ description: "The name of the rule to fetch" }),
-});
-
-/**
- * Create a rulebook tool with access to discovered rules.
- * Returns null if no rules available.
- */
-export function createRulebookTool(session: ToolSession): AgentTool<typeof rulebookSchema> | null {
-	const rules = session.rulebookRules;
-	if (!rules || rules.length === 0) {
-		return null;
-	}
-
-	// Build lookup map for O(1) access
-	const ruleMap = new Map<string, Rule>();
-	for (const rule of rules) {
-		ruleMap.set(rule.name, rule);
-	}
-
-	const ruleNames = rules.map((r) => r.name);
-
-	return {
-		name: "rulebook",
-		label: "Rulebook",
-		description: `Fetch the full content of a project rule by name. Use this when a rule listed in <available_rules> is relevant to your current task. Available: ${
-			ruleNames.join(", ") || "(none)"
-		}`,
-		parameters: rulebookSchema,
-		execute: async (_toolCallId: string, { name }: { name: string }) => {
-			const rule = ruleMap.get(name);
-
-			if (!rule) {
-				const available = ruleNames.join(", ");
-				return {
-					content: [{ type: "text", text: `Rule "${name}" not found. Available rules: ${available || "(none)"}` }],
-					details: {
-						type: "rulebook",
-						ruleName: name,
-						found: false,
-					} satisfies RulebookToolDetails,
-				};
-			}
-
-			return {
-				content: [{ type: "text", text: `# Rule: ${rule.name}\n\n${rule.content}` }],
-				details: {
-					type: "rulebook",
-					ruleName: name,
-					found: true,
-					content: rule.content,
-				} satisfies RulebookToolDetails,
-			};
-		},
-	};
-}
-
-/**
- * Filter rules to only those suitable for the rulebook (have descriptions, no TTSR trigger).
- */
-export function filterRulebookRules(rules: Rule[]): Rule[] {
-	return rules.filter((rule) => {
-		// Exclude TTSR rules (handled separately by streaming)
-		if (rule.ttsrTrigger) return false;
-		// Exclude always-apply rules (already in context)
-		if (rule.alwaysApply) return false;
-		// Must have a description for agent to know when to fetch
-		if (!rule.description) return false;
-		return true;
-	});
-}
-
-/**
- * Format rules for inclusion in the system prompt.
- * Lists rule names and descriptions so the agent knows what's available.
- */
-export function formatRulesForPrompt(rules: Rule[]): string {
-	if (rules.length === 0) {
-		return "";
-	}
-
-	const lines = [
-		"\n\n## Available Rules",
-		"",
-		"The following project rules are available. Use the `rulebook` tool to fetch a rule's full content when it's relevant to your task.",
-		"",
-		"<available_rules>",
-	];
-
-	for (const rule of rules) {
-		lines.push("  <rule>");
-		lines.push(`    <name>${escapeXml(rule.name)}</name>`);
-		lines.push(`    <description>${escapeXml(rule.description || "")}</description>`);
-		if (rule.globs && rule.globs.length > 0) {
-			lines.push(`    <globs>${escapeXml(rule.globs.join(", "))}</globs>`);
-		}
-		lines.push("  </rule>");
-	}
-
-	lines.push("</available_rules>");
-
-	return lines.join("\n");
-}
-
-function escapeXml(str: string): string {
-	return str
-		.replace(/&/g, "&amp;")
-		.replace(/</g, "&lt;")
-		.replace(/>/g, "&gt;")
-		.replace(/"/g, "&quot;")
-		.replace(/'/g, "&apos;");
-}

package/src/prompts/system-prompt.md

@@ -1,43 +0,0 @@
-You are a senior software engineer with deep expertise in debugging, refactoring, and system design. You read files, execute commands, edit code, and write new files to complete coding tasks.
-
-<critical>
-Keep working until the user's task is fully resolved. Use tools to verify—never guess.
-</critical>
-
-<environment>
-{{environmentInfo}}
-</environment>
-
-<tools>
-{{toolsList}}
-</tools>
-{{antiBashSection}}
-<guidelines>
-{{guidelines}}
-</guidelines>
-
-<instructions>
-## Execution
-- Before each tool call, state the action in one sentence.
-- After each result, verify relevance; iterate if results conflict or are insufficient.
-- Plan multi-step work with update_plan when available; skip for simple tasks.
-- On sandbox/permission failures, request approval and retry.
-
-## Verification
-- Ground answers with tools when deterministic info is needed.
-- Ask for missing parameters instead of assuming.
-- Follow project testing guidance; suggest validation if not run.
-
-## Communication
-- Concise, scannable responses; file paths in backticks.
-- Brief progress updates on long tasks; heads-up before large changes.
-- Short bullets for lists; avoid dumping large files.
-
-## Project Integration
-- Follow AGENTS.md by scope: nearest file applies, deeper overrides higher.
-- Resolve blockers before yielding.
-</instructions>
-
-<critical>
-Complete the full user request before ending your turn. This matters.
-</critical>

package/src/prompts/title-system.md

@@ -1,8 +0,0 @@
-Generate a very short title (3-6 words) for a coding session based on the user's first message. The title should capture the main task or topic. Output ONLY the title, nothing else. No quotes, no punctuation at the end.
-
-Examples:
-- "Fix TypeScript compilation errors"
-- "Add user authentication"
-- "Refactor database queries"
-- "Debug payment webhook"
-- "Update React components"