Remove PR creation instructions from kelos-self-update TaskSpawner

[kelos-bot]

Summary

• Remove PR creation instructions from kelos-self-update TaskSpawner prompt template
• Replace with issue-only directives, matching the pattern established for other non-worker TaskSpawners

Why

Issue #441 established the policy that non-worker TaskSpawners should not create PRs. PR #445 implemented this for kelos-fake-user, kelos-fake-strategist, and kelos-triage, but missed kelos-self-update. This PR completes that work.

Test plan

• Verified the change matches the pattern used in PR Restrict PR creation to axon-workers TaskSpawner only #445 for other TaskSpawners
• No code changes — prompt-only modification in a TaskSpawner definition

Fixes #465

🤖 Generated with Claude Code

---

Summary by cubic

Removed PR creation instructions from the kelos-self-update TaskSpawner and replaced them with issue-only guidance, so it opens issues instead of PRs. Fixes #465 by aligning with the established policy for non-worker TaskSpawners.

^{Written for commit d083df4. Summary will update on new commits.}

[cubic-dev-ai]

1 issue found across 1 file

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="self-development/kelos-self-update.yaml">

<violation number="1" location="self-development/kelos-self-update.yaml:72">
P2: The README still describes `kelos-self-update` as creating PRs (line 38: `→ PR or Issue`, line 211: "Creates a PR for code changes or an issue if discussion is needed"). Update both to reflect the new issue-only behavior, matching the pattern of other non-worker TaskSpawners.

(Based on your team's feedback about keeping documentation and config updated with changes.) [FEEDBACK_USED]</violation>
</file>

---

Since this is your first cubic review, here's how it works:

• cubic automatically reviews your code and comments on bugs and improvements
• Teach cubic by replying to its comments. cubic learns from your replies and gets better over time
• Add one-off context when rerunning by tagging @cubic-dev-ai with guidance or docs links (including llms.txt)
• Ask questions if you need clarification on any suggestion

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

P2: The README still describes kelos-self-update as creating PRs (line 38: → PR or Issue, line 211: "Creates a PR for code changes or an issue if discussion is needed"). Update both to reflect the new issue-only behavior, matching the pattern of other non-worker TaskSpawners.

(Based on your team's feedback about keeping documentation and config updated with changes.)

View Feedback

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At self-development/kelos-self-update.yaml, line 72:

<comment>The README still describes `kelos-self-update` as creating PRs (line 38: `→ PR or Issue`, line 211: "Creates a PR for code changes or an issue if discussion is needed"). Update both to reflect the new issue-only behavior, matching the pattern of other non-worker TaskSpawners.

(Based on your team's feedback about keeping documentation and config updated with changes.) </comment>

<file context>
@@ -65,17 +65,11 @@ spec:
         ```
         gh issue create --title "<title>" --body "<description>" --label generated-by-kelos --label kelos/needs-input
         ```
+      - Do NOT create PRs. Only create issues
 
       Constraints:
</file context>