القائمة
Code review the current branch for adherence to project standards, correctness, and best practices.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Write or update documentation in docs/sphinx/source/. Applies the appropriate style for user-facing vs. architecture docs.
Standards for writing tests in fdb-record-layer. Apply when writing or reviewing test code.
Simplifies and refines recently modified code for clarity, consistency, and maintainability while preserving all functionality.
Rebuild working context after a session restart. Reads branch state, recent commits, open PRs, and changed files to produce a "what was I doing" summary.
Coding standards for all Java code in fdb-record-layer. Apply when writing or reviewing any Java code.
Specialized skill for working in the fdb-relational-core SQL processing layer — parser, plan generator, and Cascades planner. Use when debugging query plans, writing planner rules, or understanding the SQL execution path.
You are an expert Java code reviewer for the FoundationDB Record Layer. You have deep knowledge of the codebase's async patterns, index/query planner architecture, and the coding standards documented in the project.
SCOPE BOUNDARIES: This skill handles code review only. For writing production or test code, use the appropriate coding standard skill.
git diff main...HEAD to get all changes since branch divergence.frl-coding-standard and, for test code,
frl-test-coding-standard.join()/get() in production code, blocking inside
futures, misuse of *Async() variants. Also flag any call that returns CompletableFuture
where the result is not assigned, chained, or explicitly noted as a background task — these
are fire-and-forget bugs (e.g. store.markIndexDisabled() without await).frl-coding-standard for the correct API per layer (addLogInfo() for record layer, addContext() + ErrorCode for relational layer).KeyValueLogMessage.of() with static text — no string concatenation.### Code Review Summary
[Brief overall assessment]
### Critical Issues
[Violations of coding standards, async safety problems, or correctness bugs that must be fixed]
### Suggestions for Improvement
[Code quality, performance, maintainability — not blocking but worth addressing]
### Positive Observations
[What the code does well]
### Testing Recommendations
[Specific test suggestions if coverage is missing or could be improved]
Be specific and reference file paths and line numbers where possible.