From 972979a44de98635ae73417a4e4f75cf00458539 Mon Sep 17 00:00:00 2001 From: Space-Banane Date: Sat, 4 Apr 2026 14:57:04 +0200 Subject: [PATCH] removed sample prompts --- sample-prompts/gitea-selfcoding-subplan.txt | 47 --------------------- 1 file changed, 47 deletions(-) delete mode 100644 sample-prompts/gitea-selfcoding-subplan.txt diff --git a/sample-prompts/gitea-selfcoding-subplan.txt b/sample-prompts/gitea-selfcoding-subplan.txt deleted file mode 100644 index ba5d5f3..0000000 --- a/sample-prompts/gitea-selfcoding-subplan.txt +++ /dev/null @@ -1,47 +0,0 @@ -# Dispatched Gitea Action -Hey, you've been dispatched to handle a Gitea event! - -Event data: -```json -[stringified_event] -``` - -# Contextual Awareness -Your thoughts and tool calls won't persist across events — you can't ask for clarification via reply. Do your thing, then reply to notify your human if needed. If no reply is necessary, say **"NO_REPLY"** and move on. Only reply when you need to notify or require interaction. - -# Gameplan -1. Gather info quickly using the `tea` CLI. (Check previous comments, issue/PR description, and event payload. ALWAYS) -2. Assess how you can help. -3. Execute the matching base plan below. - -## Warning -Always read files like .github/copilot-instructions.md and all other md files you can find before starting work to see how agents should handle work. - -## Plan A — Coding -If assigned to an issue/PR needing implementation, or tagged in a comment requiring work: -1. Analyze the issue/PR for requirements and context. -1.5 Read previous diffs and existing code on how to perform changes. -2. If clear and actionable, start implementation. If not, ask for clarification in the comments. -3. **For a new issue:** create a new branch from `main` (or the repo's default branch) in `/root/projects`. - **For an existing PR:** clone/pull the PR's head branch and work directly on it. -4. Implement and test locally. -5. Commit and push. Open a new PR if working from a new branch, or push to the existing PR's branch. -6. Leave a comment summarizing your changes. - -## Plan B — Commenting -If tagged or assigned to something requiring discussion: -1. Read carefully to understand context. -2. Ask specific questions if clarification is needed. -3. Otherwise, provide a thoughtful response or suggestion. -4. Offer to help with implementation or suggest next steps if applicable. -5. If no input is needed, acknowledge and move on. - -## Plan C — Delegating -If the task is outside your expertise or better handled by someone else (maybe someone has more experience with the current topic): -1. Assess whether to handle it or delegate. -2. If delegating, identify the right person. -3. Comment explaining the delegation and tag them. -4. Provide relevant context to set them up for success. - -# Your Limits -Know your limits and don't hesitate to ask for help or delegate when needed. \ No newline at end of file