You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,9 @@ We love contributions big and small. PostHog Code is the IDE for understanding h
9
9
3. Create a branch (`feat/my-change`, `fix/that-bug`)
10
10
4. Make your changes and open a pull request
11
11
12
-
We recommend creating an issue first if one doesn't already exist so we can align on the approach before you invest time.
12
+
Issues labeled [`good first issue`](https://github.com/PostHog/code/issues?q=sort%3Aupdated-desc%20is%3Aissue%20is%3Aopen%20label%3A%22good%20first%20issue%22) are a great place to start!
13
+
14
+
If an issue does not yet exist for your change, please create one first so we can align on the approach before you invest time.
'Fast agent for exploring and understanding codebases. Use this when you need to find files by pattern (eg. "src/components/**/*.tsx"), search for code or keywords (eg. "where is the auth middleware?"), or answer questions about how the codebase works (eg. "how does the session service handle reconnects?"). When calling this agent, specify a thoroughness level: "quick" for targeted lookups, "medium" for broader exploration, or "very thorough" for comprehensive analysis across multiple locations.',
188
+
model: "haiku",
189
+
prompt: `You are a fast, read-only codebase exploration agent.
190
+
191
+
Your job is to find files, search code, read the most relevant sources, and report findings clearly.
192
+
193
+
Rules:
194
+
- Never create, modify, delete, move, or copy files.
195
+
- Never use shell redirection or any command that changes system state.
196
+
- Use Glob for broad file pattern matching.
197
+
- Use Grep for searching file contents.
198
+
- Use Read when you know the exact file path to inspect.
199
+
- Use Bash only for safe read-only commands like ls, git status, git log, git diff, find, cat, head, and tail.
200
+
- Adapt your search approach based on the thoroughness level specified by the caller.
201
+
- Return file paths as absolute paths in your final response.
202
+
- Avoid using emojis.
203
+
- Wherever possible, spawn multiple parallel tool calls for grepping and reading files.
204
+
- Search efficiently, then read only the most relevant files.
205
+
- Return findings directly in your final response — do not create files.`,
0 commit comments