Review changed code for correctness, security, maintainability, and verification gaps. Use when code is ready for independent review or before handoff, staging, or merge.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Review the change in its repository context and report actionable findings, not a generic style checklist.
Inspect the request, applicable project guidance, working-tree state, staged and unstaged diffs, and relevant surrounding code. Use history when it helps explain local conventions or intent.
If the review target is ambiguous, state the assumed range or ask one focused question. Do not mix unrelated pre-existing code into the findings without labelling it.
Use judgement based on the change's risk. Consider:
Duplication, function length, and naming are signals rather than universal failures. Recommend refactoring only when it makes this code clearer or safer.
Lead with findings ordered by severity. For each one include:
Separate blocking defects from non-blocking suggestions. Avoid praise, restating the diff, or speculative concerns without a plausible failure mode. If no findings remain, say so and identify any important verification limits.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Applies local reliability, viewport, tab-safety, stale-ref, widget, and browser-boundary lessons to every agent-browser automation. Use alongside the upstream agent-browser skill whenever navigating, clicking, filling, testing, extracting, taking screenshots, or debugging any website with agent-browser.
The English summary is being prepared. Showing the original description.
Size the agent-browser Chromium window to fill its current screen, leaving a configurable bottom margin for the desktop panel. Use before any agent-browser automation that needs the full screen visible without elements overlapping or scrolling off (e.g. Xero, dense web apps).
The English summary is being prepared. Showing the original description.
Create Claude Code slash commands, OpenCode command files, Pi prompt templates, and Codex custom prompts that delegate to the right subagent or skill. Use when creating new commands, porting commands across agent platforms, or refactoring existing commands to follow platform conventions.
The English summary is being prepared. Showing the original description.
Adds or changes allowed commands in AI agent permission configs for OpenCode and Claude Code. Use when a command needs adding to an agent's allow list, when permission settings for existing commands need changing, when setting up a new AI tool that requires command permissions, or when the user asks to stop being prompted for a particular command.
The English summary is being prepared. Showing the original description.
Creates a Beads issue for a described problem or piece of work without doing the work itself. Use when the user invokes `/bc` or `$bc`, or asks to file, log, or record a bead for something. To also carry out the work, use the `bx` skill instead.
The English summary is being prepared. Showing the original description.
Stores a persistent memory or learning with `bd remember` so it survives across sessions. Use when the user invokes `/bdr` or `$bdr`, or asks to remember, note, or persist an insight in a Beads workspace.
The English summary is being prepared. Showing the original description.