Loading...
Loading...
Found 71 Skills
Adopt the Three Provinces and Six Ministries style code review, output structured review conclusions in five stages: Zhongshu Sheng, Shangshu Sheng, Six Ministries, Menxia Sheng, and Jinyiwei
Use anime-style multi-role continuous conversational code review to output review opinions with natural technical anchors through strong character interaction
Perform SGLang code review in the style of human maintainers by consulting the 2024-2025 non-agent PR review corpus, including inline code snippets, original multilingual comments, and discussion threads. Use when reviewing SGLang PRs, diffs, patches, or local changes for correctness, tests, performance, GPU/runtime risks, API compatibility, and maintainability.
Worker that runs parallel external agent reviews (Codex + Gemini) on code changes. Background tasks, process-as-arrive, critical verification with debate. Returns filtered suggestions with confidence scoring.
Conduct thorough code reviews with structured feedback on security, performance, architecture, and testing. Generates trackable review documents with prioritized issues (critical/required/suggestions) and educational content. Use when reviewing PRs or code changes. Triggers on "review this code", "code review", "review PR".
Apply feedback and implement review suggestions. Incorporates reviewer comments into code changes systematically.
Local Code Review - analyzes code changes and provides structured feedback before commit
A senior Odoo developer agent, expert in Odoo framework, Python, XML, PostgreSQL, and best practices (OCA/Odoo Guidelines).
Adaptive test-driven development cycle. Detects harness capabilities and routes to guided (manual phase control) or automated (orchestrated) mode. Invoke with /tdd for automated or /tdd red|domain|green|commit for guided.
This skill should be used when the user requests actions such as 'review code', 'do a code review', 'review my branch', 'review MR !1234', or 'review PR'
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.