[Doc]: fixing typos in various files (#271)

Author: didier-durand

.agents/base2/scout.ts

@@ -28,7 +28,7 @@ You spawn agents to help you gather information and answer the user's question.
 
 Then answer the question to the best of your ability.
 
-You cannot use any other tools beyond the ones provided to you. (No abiltity to read files, write files, or run terminal commands, etc.)
+You cannot use any other tools beyond the ones provided to you. (No ability to read files, write files, or run terminal commands, etc.)
 
 Note: No need to spawn multiple file-explorer agents, but you can spawn multiple web-researcher or docs-researcher agents.
 

.agents/types/agent-definition.ts

@@ -95,7 +95,7 @@ export interface AgentDefinition {
 
   /** How the agent should output a response to its parent (defaults to 'last_message')
    *
-   * last_message: The last message from the agent, typcically after using tools.
+   * last_message: The last message from the agent, typically after using tools.
    *
    * all_messages: All messages from the agent, including tool calls and results.
    *

README.md

@@ -60,7 +60,7 @@ You can write agent definition files that give you maximum control over agent be
 
 Implement your workflows by specifying tools, which agents can be spawned, and prompts. We even have TypeScript generators for more programmatic control.
 
-For example, here's a `git-committer` agent that creates git commits based on the current git state. Notice that it runs `git diff` and `git log` to analyze changes, but then hands control over to the LLM to craft a meaningful commit messagea and perform the actual commit.
+For example, here's a `git-committer` agent that creates git commits based on the current git state. Notice that it runs `git diff` and `git log` to analyze changes, but then hands control over to the LLM to craft a meaningful commit message and perform the actual commit.
 
 ```typescript
 export default {

backend/src/system-prompt/prompts.ts

@@ -85,7 +85,7 @@ If the user sends you the url to a page that is helpful now or could be helpful
 const initPrompt = `
 User has typed "init". Trigger initialization flow:
 
-First, read knowldge.md and ${codebuffConfigFile} top level directory.
+First, read knowledge.md and ${codebuffConfigFile} top level directory.
 
 Knowledge file:
 - If it does not exist, create a new one with updated information.

backend/src/system-prompt/truncate-file-tree.ts

@@ -274,7 +274,7 @@ function pruneFileTokenScores(
       }
     }
 
-    // Note: The below function can take a while, so we optmized to have few loop iterations.
+    // Note: The below function can take a while, so we optimized to have few loop iterations.
     printedTree = printFileTreeWithTokens(fileTree, pruned)
     totalTokens = countTokensJson(printedTree)
     index += batchSize

backend/src/tools/definitions/tool/create-plan.ts

@@ -22,7 +22,7 @@ For a technical plan, act as an expert architect engineer and provide direction
 - Just show the changes needed.
 
 What to include in the plan:
-- Include key snippets of code -- not full files of it. Use psuedo code. For example, include interfaces between modules, function signatures, and other code that is not immediately obvious should be written out explicitly. Function and method bodies could be written out in psuedo code.
+- Include key snippets of code -- not full files of it. Use pseudo code. For example, include interfaces between modules, function signatures, and other code that is not immediately obvious should be written out explicitly. Function and method bodies could be written out in psuedo code.
 - Do not waste time on much background information, focus on the exact steps of the implementation.
 - Do not wrap the path content in markdown code blocks, e.g. \`\`\`.
 

backend/src/tools/definitions/tool/write-file.ts

@@ -54,7 +54,7 @@ Notes for editing a file:
 - If you don't use any placeholder comments, the entire file will be replaced. E.g. don't write out a single function without using placeholder comments unless you want to replace the entire file with that function.
 - When editing a file, try not to change any user code that doesn't need to be changed. In particular, you must preserve pre-existing user comments exactly as they are.
 - You can also use this tool to create new files.
-- After you have written out a write_file block, the changes will be applied immediately. You can assume that the changes went through as intended. However, note that there are sometimes mistakes in the processs of applying the edits you described in the write_file block, e.g. sometimes large portions of the file are deleted. If you notice that the changes did not go through as intended, based on further updates to the file, you can write out a new write_file block to fix the mistake.
+- After you have written out a write_file block, the changes will be applied immediately. You can assume that the changes went through as intended. However, note that there are sometimes mistakes in the process of applying the edits you described in the write_file block, e.g. sometimes large portions of the file are deleted. If you notice that the changes did not go through as intended, based on further updates to the file, you can write out a new write_file block to fix the mistake.
 
 Examples:
 ${getToolCallString(toolName, {

common/src/templates/initial-agents-dir/types/agent-definition.ts

@@ -95,7 +95,7 @@ export interface AgentDefinition {
 
   /** How the agent should output a response to its parent (defaults to 'last_message')
    *
-   * last_message: The last message from the agent, typcically after using tools.
+   * last_message: The last message from the agent, typically after using tools.
    *
    * all_messages: All messages from the agent, including tool calls and results.
    *

common/src/util/agent-id-parsing.ts

@@ -80,7 +80,7 @@ export function parseAgentId(fullAgentId: string): {
 }
 
 /**
- * Parse publishded agent ID to extract publisher, agent name, and optionally version
+ * Parse published agent ID to extract publisher, agent name, and optionally version
  *
  * If the agent ID is not in the publisher/agent format, return null
  */

knowledge.md

@@ -194,7 +194,7 @@ mock.module('../services/api-client', () => ({
 
 - Easier to restore original functionality with `mock.restore()`
 - Clearer test isolation
-- Doesn't interfere with global state (mock.module carrries over from test file to test file, which is super bad and unintutitve.)
+- Doesn't interfere with global state (mock.module carries over from test file to test file, which is super bad and unintuitive.)
 - Simpler debugging when mocks fail
 
 ### Test Setup Patterns