Update agent config based on PR review feedback

- Remove redundant git checkout from pr-responder setup step since
  kelos handles branch checkout automatically via the task template
  branch field
- Add explicit /kind label instruction to workers PR creation step
  to ensure generated PRs always include proper kind labels

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: gjkim42

self-development/kelos-pr-responder.yaml

@@ -66,16 +66,14 @@ spec:
       {{end}}
 
       Task:
-      - 0. Set up your working branch. Run this exactly:
+      - 0. Set up your working branch. Kelos has already checked out {{.Branch}} for you. Run this exactly:
         ```
         git fetch --unshallow || true
         if git remote get-url upstream >/dev/null 2>&1; then
           git fetch upstream main
-          git checkout {{.Branch}}
           git rebase upstream/main
         else
           git fetch origin main
-          git checkout {{.Branch}}
           git rebase origin/main
         fi
         ```

self-development/kelos-workers.yaml

@@ -113,7 +113,7 @@ spec:
         - Only implement what the issue explicitly asks for. If you discover related improvements, create separate issues for them.
       - 3b. Create a commit that fixes the issue.
       - 4b. Push your branch to origin kelos-task-{{.Number}}.
-      - 5b. Create a PR with labels "generated-by-kelos" and "ok-to-test" (use `gh pr create --label generated-by-kelos --label ok-to-test`), then /review it. If changes are needed, make them, commit and push, then /review again. Repeat until the review passes.
+      - 5b. Create a PR with labels "generated-by-kelos", "ok-to-test", and one `/kind` label (bug, cleanup, docs, or feature) matching the change type (use `gh pr create --label generated-by-kelos --label ok-to-test --label kind/<type>`), then /review it. If changes are needed, make them, commit and push, then /review again. Repeat until the review passes.
       - 6b. Update the PR title and description to reflect the final diff. The PR body MUST contain a standard closing keyword reference on its own line (e.g., `Fixes #{{.Number}}` or `Closes #{{.Number}}`). Do not embed the issue number in natural language.
       - 7b. Make sure the PR passes all CI tests.