[Docs] Daily documentation sync - 2026-06-18#11407
Conversation
LigiaZ
commented
Jun 18, 2026
LigiaZ
commented
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
| @@ -0,0 +1,3 @@ | |||
| Add the following section to the existing `packages/kilo-docs/code-with-ai/platforms/github.md` file, after the installation/setup instructions and before any troubleshooting section: | |||
There was a problem hiding this comment.
CRITICAL: File content is a leftover instruction prompt, not actual documentation
This new file's entire body is Add the following section to the existing ... file, after the installation/setup instructions and before any troubleshooting section: followed by a bare ---. That reads like a generation prompt that was written into the file instead of being executed against it. It is also self-contradictory: the diff is new file mode, yet the text references "the existing" file. If this merges, the published docs page will show this instruction text to readers.
This looks like the daily-sync automation misfired. Please replace the file body with the actual GitHub platform documentation section (or revert if nothing was intended to ship), and add a trailing newline.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
Code Review SummaryStatus: 7 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)CRITICAL
Other Observations (not in diff)
Files Reviewed (7 files)
Fix these issues in Kilo Cloud Previous Review Summaries (4 snapshots, latest commit 2b1248d)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 2b1248d)Status: 5 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)CRITICAL
Other Observations (not in diff)
Files Reviewed (5 files)
Fix these issues in Kilo Cloud Previous review (commit 5b4bf65)Status: 4 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)CRITICAL
Other Observations (not in diff)
Files Reviewed (4 files)
Fix these issues in Kilo Cloud Previous review (commit 0dce8b3)Status: 3 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)CRITICAL
Other Observations (not in diff)
Files Reviewed (3 files)
Fix these issues in Kilo Cloud Previous review (commit 35332db)Status: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)CRITICAL
Other Observations (not in diff)
Files Reviewed (1 file)
Reviewed by gpt-5.4-20260305 · 215,779 tokens Review guidance: REVIEW.md from base branch |
| @@ -0,0 +1,3 @@ | |||
| Add the following section to the existing BYOK documentation after the section explaining how to configure BYOK providers: | |||
There was a problem hiding this comment.
CRITICAL: File content is a leftover generation prompt ("Add the following section to the existing BYOK documentation...") plus a bare ---, not actual documentation. Also, this file lives at the repository root with a non-descriptive name (hasUserByokAvailable) rather than under packages/kilo-docs/. Publishing this would expose instruction text to readers. Replace with real BYOK docs content or remove the file.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| @@ -0,0 +1,3 @@ | |||
| Add the following section to the existing BYOK documentation after the section explaining how to configure BYOK providers: | |||
There was a problem hiding this comment.
CRITICAL: File content is a leftover generation prompt ("Add the following section to the existing BYOK documentation after the section explaining how to configure BYOK providers:") plus a bare ---, not actual documentation. The file is marked new file mode yet the prompt references "the existing" documentation, which is self-contradictory. Publishing this would expose instruction text to readers. Replace with real BYOK documentation content or remove the file.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| @@ -0,0 +1,3 @@ | |||
| Add the following section to the existing `packages/kilo-docs/getting-started/migrating.md` file: | |||
There was a problem hiding this comment.
CRITICAL: File content is a leftover generation prompt ("Add the following section to the existing ... file:") followed by an opening ```markdown fence with no content and no closing fence. This is not actual documentation — it's the instruction that was meant to produce the docs, mistakenly committed instead of the generated output. The file also has no trailing newline.
Recommend replacing this with the intended migrating.md content (or removing the file) before merge.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
…ion model deny lists
| @@ -0,0 +1,10 @@ | |||
| ```markdown | |||
There was a problem hiding this comment.
CRITICAL: This new docs file is in the wrong location and still contains fenced prompt-style content
packages/kilo-docs/pages/collaborate/enterprise/model-access-controls.md already exists and is the page wired into the docs site, but this PR adds a second file at packages/kilo-docs/collaborate/enterprise/model-access-controls.md outside the pages/ tree. That means /docs/collaborate/enterprise/model-access-controls will keep serving the existing page and ignore this new content entirely. The opening ```markdown fence at line 1 would also prevent frontmatter parsing if this content were moved into pages/, so the generated output still needs cleanup before it can replace the real doc.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| @@ -0,0 +1,12 @@ | |||
| ### File 1: `packages/kilo-docs/src/content/docs/code-with-ai/platforms/kilo-console.md` | |||
There was a problem hiding this comment.
CRITICAL: Prompt scaffolding was committed instead of a publishable docs page
Because this file starts with a literal ### File 1: ... heading and an opening ```markdown fence, the --- block below it is not frontmatter anymore. The file also never closes that fence, so the title, description, and body would all render as code/prompt scaffolding instead of a real Kilo Console docs page.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| @@ -0,0 +1,12 @@ | |||
| ### File 1: `packages/kilo-docs/src/content/docs/code-with-ai/platforms/kilo-console.md` | |||
There was a problem hiding this comment.
CRITICAL: This route is publishing the wrong page content
setup-authentication.md contains the same scaffolded Kilo Console body as the other new file, including the ### File 1: ...kilo-console.md header and # Kilo Console heading. With the frontmatter fenced off as code and the page content targeting a different topic entirely, /getting-started/setup-authentication would publish unrelated Kilo Console text instead of authentication setup docs.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
1 participant
