Skip to content

Replace review-code-examples agent with code-review skill #28268

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
elithrar merged 2 commits into from
Feb 20, 2026
Merged

Replace review-code-examples agent with code-review skill #28268

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
dfcf5d7
replace review-code-examples agent with code-review skill
elithrar Feb 11, 2026
3522e11
sharpen command wording for LLM clarity
elithrar Feb 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
99 changes: 0 additions & 99 deletions .opencode/agent/review-code-examples.md
View file
Open in desktop

This file was deleted.

14 changes: 11 additions & 3 deletions .opencode/command/review-code-examples.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,11 +1,19 @@
---
description: Review code examples in documentation
agent: review-code-examples
model: anthropic/claude-opus-4-5
---

Review code snippets in documentation files using the @review-code-examples agent. Focus on code within `<TypeScriptExample>`, `<WranglerConfig>`, `<Tabs>`, and fenced code blocks.
Load the code-review skill before doing anything. Follow its review process and reference files exactly.

Review every code snippet in the target files: fenced code blocks, `<TypeScriptExample>`, `<WranglerConfig>`, `<Tabs>`, and `<APIRequest>` components. Do not skip any.

When editing code, follow these rules:

- Copy original lines verbatim first, then change only the specific tokens that need fixing
- Note the indentation style before editing and confirm your replacement matches
- Prefer small edits — multiple single-line edits are safer than one large multi-line replacement
- Re-read modified lines from the file to confirm indentation is correct before moving on

Guidance: $ARGUMENTS

Review files the user specifies. If no files specified, find changed `.mdx` files via `git diff --name-only`. If no changes found, ask the user which files to review.
Review files the user specifies. If no files specified, find changed `.mdx` files via `git diff --name-only`. If no changes found, ask the user which files to review.
Loading