docs: trim AGENTS.md duplication into skills

.kilo/skills/gh-issues/SKILL.md

@@ -0,0 +1,68 @@
+---
+name: gh-issues
+description: Use when creating, triaging, or commenting on GitHub issues for the Kilo VS Code extension or JetBrains plugin via `gh`. Covers issue templates, project board assignment, title conventions, and required `gh` scopes.
+---
+
+# GitHub Issues
+
+Use this skill whenever you create or manage a GitHub issue with `gh` for either the VS Code extension or the JetBrains plugin.
+
+## Templates
+
+The repo defines issue templates in `.github/ISSUE_TEMPLATE/`. Pick the matching template instead of opening a blank issue:
+
+| Template | When to use |
+|---|---|
+| `Bug report` (`bug-report.yml`) | Reproducible defects with steps, expected, and actual behavior |
+| `Feature Request` (`feature-request.yml`) | New capabilities, enhancements, or behavior changes |
+| `Question` (`question.yml`) | Usage or design questions that aren't obviously bugs or feature requests |
+
+Pass the template title to `gh issue create --template`.
+
+## Title Conventions
+
+- Use a plain, descriptive title that reads cleanly as a standalone sentence.
+- Do not add platform-specific prefixes such as `[JetBrains]`, `[Jetbrains]`, `[JB]`, `[VS Code]`, `[VSCode]`, or similar. Routing happens through project boards, not the title.
+
+## Project Boards
+
+Every new issue must land on the correct project board:
+
+| Surface | Project | URL |
+|---|---|---|
+| VS Code extension | `VS Code Extension` | https://github.com/orgs/Kilo-Org/projects/25 |
+| JetBrains plugin | `Jetbrains Plugin` | https://github.com/orgs/Kilo-Org/projects/39 |
+
+Pass the project title to `gh issue create --project`.
+
+## Recipes
+
+Create a VS Code extension bug report and add it to the board:
+
+```bash
+gh issue create \
+  --template "Bug report" \
+  --project "VS Code Extension" \
+  --title "Sidebar chat fails to render after reload" \
+  --body "..."
+```
+
+Create a JetBrains feature request:
+
+```bash
+gh issue create \
+  --template "Feature Request" \
+  --project "Jetbrains Plugin" \
+  --title "Support Kotlin Multiplatform target detection" \
+  --body "..."
+```
+
+## Scope Errors
+
+If `gh` reports a missing scope when assigning a project, refresh the auth token and retry:
+
+```bash
+gh auth refresh -s project
+```
+
+After the refresh succeeds, re-run the original `gh issue create` command. Do not fall back to creating the issue without the project — the board assignment is required.

AGENTS.md

@@ -223,12 +223,7 @@ PR descriptions should be 2-3 lines covering **what** changed and **why**. Focus
 
 ## GitHub Issues
 
-- When creating a GitHub issue for the VS Code extension or JetBrains plugin, use the repo's existing issue templates in `.github/ISSUE_TEMPLATE/`. Pick the matching template (`Bug report`, `Feature Request`, or `Question`) instead of opening a blank issue.
-- Do not add platform-specific title prefixes such as `[JetBrains]`, `[Jetbrains]`, `[JB]`, `[VS Code]`, `[VSCode]`, or similar. Use a plain, descriptive title.
-- Always add VS Code extension issues to the GitHub project `VS Code Extension`: https://github.com/orgs/Kilo-Org/projects/25
-- Always add JetBrains plugin issues to the GitHub project `Jetbrains Plugin`: https://github.com/orgs/Kilo-Org/projects/39
-- When using `gh`, prefer `gh issue create --template "..." --project "..."` with the matching project title.
-- If project assignment fails because `gh` is missing the required scope, run `gh auth refresh -s project` and retry.
+When creating or managing GitHub issues for the VS Code extension or JetBrains plugin via `gh`, load `.kilo/skills/gh-issues/SKILL.md`. It covers templates, project boards (`VS Code Extension`, `Jetbrains Plugin`), title conventions, and the `gh auth refresh -s project` recovery path.
 
 ## Fork Merge Process
 
@@ -262,50 +257,13 @@ The goal is to keep our diff from upstream as small as possible, making regular
 
 ### Kilocode Change Markers
 
-To minimize merge conflicts when syncing with upstream, mark Kilo Code-specific changes in shared code with `kilocode_change` comments.
+When editing shared upstream files, mark Kilo-specific lines with `kilocode_change` comments so future merges can find them. The basic forms are:
 
-**Single line:**
+- Single line: `const value = 42 // kilocode_change`
+- Multi-line block: wrap with `// kilocode_change start` / `// kilocode_change end`
+- New file in a shared path: `// kilocode_change - new file` at the top
+- JSX/TSX: use `{/* kilocode_change */}` (and `{/* kilocode_change start */}` / `end`)
 
-```typescript
-const value = 42 // kilocode_change
-```
-
-**Multi-line:**
-
-```typescript
-// kilocode_change start
-const foo = 1
-const bar = 2
-// kilocode_change end
-```
-
-**New files:**
-
-```typescript
-// kilocode_change - new file
-```
-
-<!-- prettier-ignore -->
-**JSX/TSX (inside JSX templates):**
-
-<!-- prettier-ignore -->
-```tsx
-{/* kilocode_change */}
-```
-
-<!-- prettier-ignore -->
-```tsx
-{/* kilocode_change start */}
-<MyComponent />
-{/* kilocode_change end */}
-```
-
-#### When markers are NOT needed
-
-Code in these paths is Kilo Code-specific and does NOT need `kilocode_change` markers:
-
-- `packages/opencode/src/kilocode/` - All files in this directory
-- `packages/opencode/test/kilocode/` - All test files for kilocode
-- Any other path containing `kilocode` in filename or directory name
+Markers are NOT needed in paths that contain `kilocode` in the name (e.g. `packages/opencode/src/kilocode/`, `packages/opencode/test/kilocode/`) — these are entirely Kilo Code additions and won't conflict with upstream.
 
-These paths are entirely Kilo Code additions and won't conflict with upstream.
+For decision rules on when to keep changes inline vs. extract Kilo logic, marker placement guidance, and verification commands, load `.kilo/skills/kilocode-merge-minimizer/SKILL.md`.