code-review
Review changes in clickhouse-java for correctness, compatibility, API stability, and missing tests. Use when reviewing pull requests, commits, diffs, patches, or when the user asks for a code review.
Review changes in clickhouse-java for correctness, compatibility, API stability, and missing tests. Use when reviewing pull requests, commits, diffs, patches, or when the user asks for a code review.
Validate changes before submitting a pull request. Run comprehensive checks including lint, tests, alignment review, and RFC analysis. Use before creating a PR, when asked if code is ready for review, or before pushing for PR.
Review code changes for bugs and alignment with OpenEnv principles and RFCs. Use when reviewing PRs, checking code before commit, or when asked to review changes. Implements two-tier review model.
Write failing tests from requirements. Invoke for each todo before /implement.
Validate documentation traceability between code annotations (@implements), feature registry, business rules, and use cases. Detect ID collisions, undocumented features, broken cross-references, and namespace violations.
Service management for E2E testing in EdgeQuake. Start, stop, and monitor PostgreSQL, backend API, and frontend services. Includes health checks and logging utilities for interactive testing workflows.
Capture EdgeQuake WebUI routes with Playwright and write artifacts immediately (screenshots + per-page request JSON + capture index). Use when adding/updating Playwright E2E capture specs or when asked to automate UI screenshot collection.
Verify a Zotero translator after every addition or modification, and before submitting a PR. Runs linting, tests, and metadata updates.
Create or update test cases for a Zotero translator by running it against live URLs and capturing the output.
Validate inference generates correct text
Validate all intermediate calculations during inference are correct using source of truth values
่ฟ่ก Phase 2 ๅทฅไฝๆตใๆง่ก่ๆฌๆซๆ็ผบๅคฑ็ๅค่ฏญ่จ่ฏๆก๏ผๅนถๆๆณจๅ่กจ่กฅๅ จๅฏ็จ่ฏญ่จ๏ผๅฆ en-USใzh-TWใvi-VNใja-JP๏ผ๏ผๆๅไฟฎๅค็ธๅ ณๆต่ฏใ
่ฟ่ก้กน็ฎๆต่ฏ๏ผๆถต็ Python ๅ็ซฏใVue ๅ็ซฏๅๅค่ฏญ่จๆ ก้ช๏ผ
Code style guidelines for NeMo-RL (Python and shell). Covers naming, indentation, comments, docstrings, reflection avoidance, and uv usage. Auto-invoked during code review.
Configuration conventions for NeMo-RL. YAML is the single source of truth for defaults. Covers TypedDict usage, exemplar YAML updates, and forbidden default patterns. Auto-invoked during code review.
ไปฃ็ ๅฎกๆฅๅ่ดจ้ๅๆๆ่ฝใ็จไบๅฎกๆฅไปฃ็ ใๅ็ฐๆฝๅจ้ฎ้ขใๆไพๆน่ฟๅปบ่ฎฎใๅฝ็จๆท่ฏทๆฑไปฃ็ ๅฎกๆฅใไปฃ็ ่ดจ้ๅๆๆๆไฝณๅฎ่ทตๅปบ่ฎฎๆถไฝฟ็จใ
Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.
Testing patterns and principles. Unit, integration, mocking strategies.
Web application testing principles. E2E, Playwright, deep audit strategies.