docs(kilo-docs): label custom agents in navigation and related links - #14072
Open
emilieschario wants to merge 1 commit into
Open
docs(kilo-docs): label custom agents in navigation and related links#14072emilieschario wants to merge 1 commit into
emilieschario wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Docs-only terminology update. All route targets are preserved, the Files Reviewed (11 files)
Reviewed by deepseek-v4.1-flash · Input: 0 · Output: 0 · Cached: 0 Review guidance: REVIEW.md from base branch |
emilieschario
enabled auto-merge
September 12, 2026 16:31
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Use Custom Agents for the page title, sidebar entry, and selected related links; update the homepage labels to match current agent terminology.
Keep all route targets unchanged and preserve the custom-modes heading anchor. Organization dashboard labels and legacy migration instructions remain untouched. Avoid editing lines already covered by the earlier terminology PRs; remaining mixed descriptions can be handled separately.