[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ACAVYCQRSR6XD5R145S50T":3,"skill-same:01M6ACAVYCQRSR6XD5R145S50T":117},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M6ACAVYCQRSR6XD5R145S50T","review-pr",null,"Review Apache ShardingSphere or user-authorized downstream pull requests and PR discussions from public or authorized repository evidence. Use for code-correctness or mergeability decisions, CI-focused review, root-cause and regression analysis, complete consolidated findings, copy-ready committer feedback, challenged findings, multi-round review, and formal review of local implementation candidates in the repository completion loop.","apache\u002Fshardingsphere","apache","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F47359?v=4","01M6AC83E6K4FDKK7HZ8WNMQKE","The Apache Software Foundation","01M6ACA8B7ZSJJ37TC5EJ9GQFT",20830,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fapache\u002Fshardingsphere\u002Fblob\u002Fmaster\u002F.codex\u002Fskills\u002Freview-pr\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,9,35,36,37],"review pr","review","pr","for","complete","local","committer","ready","evidence","use","feedback","regression","loop","analysis","ci","repository","pull","code","pull requests","2026-11-10 10:12:30",false,"---\nname: review-pr\ndescription: >-\n  Review Apache ShardingSphere or user-authorized downstream pull requests and PR\n  discussions from public or authorized repository evidence. Use for code-correctness or\n  mergeability decisions, CI-focused review, root-cause and regression analysis, complete\n  consolidated findings, copy-ready committer feedback, challenged findings, multi-round\n  review, and formal review of local implementation candidates in the repository completion loop.\n---\n\n# Review PR\n\n## Purpose and Modes\n\nJudge the latest reviewed scope from root cause, behavior, contracts, tests, and\npublic or user-authorized repository evidence. Select one output mode:\n\n- `Formal Review Mode`: return one formal result for a public PR review, authorized local-candidate review, code-readiness judgment, mergeability decision, or CI review.\n- `PR Discussion Reply Mode`: return a copy-ready committer reply only when the user explicitly requests a review-thread response, author or maintainer objection reply, or challenged-finding reply. Do not add a formal verdict unless requested.\n\nUse Formal Review Mode for every explicit code or PR review and every Formal Review required by the repository completion route.\nIdentify a local candidate and its local-only delta in `### Coverage`; do not create a separate local-preflight result format or describe local-only work as the public PR state.\n\n## Review Focus\n\nReview focus is independent from output mode.\n\n| Focus | Use when | CI behavior |\n|---|---|---|\n| `Code Correctness Review` | Default review of code, tests, behavior, scope, or regression risk | Do not query, wait for, or report GitHub Actions, checks, workflow runs, or Actions logs |\n| `Mergeability Review` | The user asks whether the PR can be merged, approved, or landed | Review code and required CI or checks |\n| `CI Review` | The user asks about checks, Actions, logs, or CI failures | Treat CI evidence as the primary target |\n\nExplicit user scope wins. Formal Review of a local candidate uses `Code Correctness Review` unless the user explicitly requests CI.\n\nIn Code Correctness Review, unreviewed CI is not an evidence gap. Runtime facts\nmay still be required from code, official specifications, public reproductions,\nor local verification. If such a decisive fact is unavailable, identify that\nfact—not CI—as the incomplete reason.\n\n## Canonical Assessment\n\nResolve one review basis before discovery: the effective candidate, applicable requirements, accepted behavior and project commitments, selected review focus, and admissible evidence. Run the Review Workflow against that basis and produce one mode-independent assessment:\nconfirmed findings consolidated by fix boundary, needs-discussion conditions,\nincomplete-evidence gaps, and Completion Gate state.\n\nRecord each applicable requirement's source, content version, scope and valid exceptions in readable basis source material; a task-only requirement applies only to its authorized task candidate and must not become a universal repository or public-PR rule.\nReconstruct those requirements from original user requests and maintained contracts before checking the author's proposed solution, distinguishing author choices and unverified assumptions from confirmed constraints.\nDo not promote an unverified inference into a requirement for a new interface, SPI, behavior, or test.\nPreserve later user approvals with their actual provenance instead of treating approval of an implementation choice as proof of an original version requirement or of its necessity.\nKeep effective content and delta identity separate from Git revision lineage so equal local and public candidates retain one code-correctness basis.\n\nOutput mode must not affect candidate discovery, proof, classification,\ncoverage, or convergence. Never use a previous Formal Review result as\nevidence or as a conclusion to match. Treat previous public findings only as\nhypotheses whose cited facts must be reverified.\n\nCompleted coordinated reviews with the same effective candidate, requirements, focus, and evidence must produce the same canonical overall assessment.\nIndividual independent assessments may discover different candidates; the coordinator verifies and adjudicates their cumulative findings under Independent Review Coordination.\nPublic-PR and local-candidate reviews may resolve different candidates, but they must apply the same code-correctness judgment and Formal Review result mapping. A changed focus, requirement,\nor external fact changes the review basis and may legitimately change the\nassessment. Mergeability or CI evidence may add external-state findings or\ngaps, but it must not change code-correctness findings derived from an otherwise\nunchanged basis.\n\n## Core Contracts\n\n1. Review only. Do not modify PR code, post comments, submit reviews, resolve\n   threads, rerun workflows, or change remote state without explicit authority.\n2. Public-PR Formal Review scope is the latest target PR head and the complete GitHub changed-file list; use local triple-dot semantics when reproducing it. Local-candidate Formal Review scope follows `Local Candidate Scope` below. A discussion reply starts from the latest head, thread context, and affected behavior; expand to complete scope only when the claim depends on it.\n3. Public community conclusions use only public evidence and sanitized\n   verification summaries. Private-repository conclusions may use authorized\n   repository evidence but must remain within the user-authorized task and\n   target repository.\n4. Reconstruct `trigger -> failing path -> observed result -> expected\n   behavior` before judging the patch. A fallback, default, null check,\n   try-catch, or swallowed error is not a root-cause repair unless it fixes the\n   owning contract.\n5. Treat every concern as a candidate until it passes the Finding Proof Gate.\n6. Do not turn uncertainty, inaccessible evidence, tool failure, skipped\n   verification, or uninspected counter-evidence into a blocker.\n7. In Formal Review, complete the required review and do not stop at the first blocker.\n   Consolidate findings by independent fix boundary and return the complete current-head set once after the Completion Gate.\n   Before that gate, publish only an explicitly requested status, narrow review or early high-risk blocker, or the qualified negative result defined in the Formal Decision Contract.\n8. Follow `AGENTS.md` for repository authority, evidence, scope, safety, and sensitive data, and follow the applicable canonical references below for implementation, testing, contract, non-regression, and verification criteria.\n\n## Repository Code Policy References\n\nStandalone review is read-only and does not activate `code-implementation` or acquire write authority. Before judging the effective candidate, read [implementation rules](..\u002Fcode-implementation\u002Freferences\u002Frules\u002Fimplementation.md), [non-regression rules](..\u002Fcode-implementation\u002Freferences\u002Frules\u002Fnon-regression.md), and [verification rules](..\u002Fcode-implementation\u002Freferences\u002Fverification.md) through EOF. Also read [testing rules](..\u002Fcode-implementation\u002Freferences\u002Frules\u002Ftesting.md) when tests or coverage matter, and [artifact removal and contract impact rules](..\u002Fcode-implementation\u002Freferences\u002Frules\u002Fartifact-removal-and-contract-impact.md) when their trigger matches. Reuse an exact reference already read by the outer implementation workflow.\nBefore judging reviewed code or Maven POM changes, read [coding standards](..\u002Fcoding-standards\u002FSKILL.md) through EOF and use its Implementation Guidance Mode.\n\n## Problem and Project Commitment Gate\n\nComplete this gate before implementation-detail discovery; it establishes the review basis but does not waive the Finding Proof, Mandatory Style Verification, Completion, or convergence gates.\n\n1. Reconstruct the problem and expected behavior from the PR, linked issue when present, official documentation, maintained contracts, current code, and tests.\n2. For a defect, trace the failing path to the violated contract and its maintained owner; for another PR type, establish the goal and responsibilities it must preserve.\n3. Trace the patch's actual mechanism and compare it with a repair or reuse path in that owner; record why the chosen boundary addresses the cause or accepted goal and what remains outside scope.\n4. Verify outcome-sensitive assumptions about external calls, dependency versions, configuration and lifecycle, including side effects and resource cost on already-correct supported paths, before accepting the direction.\n5. Classify the requested outcome as preserving an accepted contract or adding a project commitment such as new semantics, configuration, API or SPI, compatibility, topology, database, dialect, or cross-module support.\n6. For Apache ShardingSphere, establish that ShardingSphere owns the behavior and that official project positioning, maintained contracts, or an explicit public maintainer decision accepts every new commitment; for an authorized downstream repository, apply equivalent target-project evidence available within the user-authorized repository boundary.\n7. Identify the narrowest accepted user-visible behavior and compare it with the patch's public contract, shared abstractions, compatibility surface, documentation, and tests.\n8. Check whether the change creates precedent or consistency pressure beyond the accepted behavior; an exact existing behavior or special case does not authorize broader generalization.\n\nAn open or labeled issue, popularity, contributor effort, available code, passing tests, or a small diff do not establish project acceptance.\nWhen evidence disproves the problem, expected behavior, applicable project ownership, or an asserted accepted commitment, or when a new commitment still requires a maintainer decision, record a `Needs Discussion` condition.\nWhen the behavior is accepted but the patch adds unsupported generalization, public surface, parallel models, or abstractions without a real stable boundary, treat the excess as a finding candidate under the implementation rules; patch size or novelty alone is not evidence of overdesign.\nWhen a decisive acceptance or ownership fact is unavailable after every admissible route, apply the Review Incomplete Proof Gate instead of converting uncertainty into `Needs Discussion`.\n\n## Scope and Evidence\n\nRead [evidence-access.md](references\u002Fevidence-access.md) and complete its GitHub Access Preflight before any GitHub request. It owns public-read selection, current-head identity, authoritative file scope, local-style evidence, failure attribution, CI, external behavior, and evidence hygiene. Apply its Local Style Verification Evidence to every public-PR or PR-backed local-candidate Formal Review.\n\nFor public-PR or PR-backed local-candidate formal reviews, establish the latest public head and base, authoritative files and requirements, relevant public discussion, and any authorized local delta.\nStandalone candidates follow `Local Candidate Scope`.\nFor discussion replies, establish the complete current thread and affected paths; obtain the full file list when scope or readiness is disputed.\nEarlier findings do not prove current-head readiness.\n\nTreat AI-assistance disclosure only as an explicit mergeability or policy-compliance concern. Apply `AI_POLICY.md` only when public evidence establishes material AI assistance; never infer it from code, prose, metadata, or a classifier.\n\n## Mandatory Style Verification Gate\n\nApply this gate to every Formal Review of a public PR and every PR-backed local candidate.\nThis gate is local candidate verification rather than a GitHub CI query, so every Review Focus must complete it even when Code Correctness Review does not read GitHub Actions, checks, workflow runs, or Actions logs.\n\n1. Derive the applicable PR-impact files and their owning Maven modules from the authoritative changed-file list for the effective candidate.\n2. Treat production and test Java files as applicable to both Checkstyle and Spotless unless repository configuration proves that a check does not govern a file.\n3. Run both checks against the latest public PR head or an accurate PR-backed local candidate that contains the latest public head and only its authorized local delta.\n4. Invalidate Checkstyle and Spotless evidence only where checked files, effective configuration, tool identity and inputs or applicable coverage changed.\n   Existing runs satisfy step 3 only after proof that the current accurate candidate contains the latest public head and that checked files, effective configuration, tool identity and inputs, and the complete applicable scope are unchanged.\n5. Use a whole-repository check, complete affected-module checks, or an exact-file check only when the command output and file inventory prove that the selected scope covers every applicable PR-impact file.\n6. Expand verification to the complete rule impact, normally the whole repository, when the PR changes global Checkstyle or Spotless configuration, a parent POM, or another cross-module style rule.\n7. Treat an exit code of zero as passing evidence only when the output also proves that every applicable PR-impact file was selected; a successful command that matched no intended file is not evidence.\n8. Do not use passing CI, required checks, commit statuses or a PR comment summary to satisfy or waive this gate.\n   An older local result counts only when the unchanged-input and current-candidate coverage proof above is complete.\n9. Do not run `spotless:apply` or another file-modifying formatter during review.\n\nMap the gate result before applying the remaining Formal Decision Contract.\n\n- If Checkstyle or Spotless fails on an applicable PR-impact file, return `Not Mergeable` with `Feedback Mode: Change Request`.\n- A style-check failure result must include `Feedback Mode: Change Request` and the blocking-issue count in `### Result`, then identify each failed check and affected PR-impact file in `### Blocking Issues`.\n- A style-check failure result must also include `### Coverage` with the effective candidate SHA, authoritative files accounted for, failed command, exit code, and affected PR-impact file.\n- If environment, dependency, candidate-materialization, tool, or coverage-proof failure leaves any applicable PR-impact file unverified, apply the Formal Decision Contract's qualified negative rule; otherwise return `Review Incomplete`.\n- If a module-scoped command fails only on unchanged files, narrow the check reliably or compare the base and effective candidate before attribution; do not classify the PR from that module failure alone.\n- If a check has no applicable PR-impact file, record `Not Applicable` and the repository-configuration basis in `### Coverage`.\n- Only successful current-candidate evidence for both checks, or an explicit not-applicable determination for either check, permits the remaining Formal Decision Contract to select `Mergeable`.\n\n## Finding Proof Gate\n\nA candidate may become a blocking issue only when all five conditions hold:\n\n1. `Evidence`: current code, diff, contract, test, log, CI, public reproduction,\n   official documentation, or generated artifact directly supports the claim.\n2. `Full path`: trace the relevant production or test entry path end to end;\n   inspect setup, wrappers, earlier calls, generators, and consuming runtime.\n3. `Counter-evidence`: check the strongest evidence that could disprove the\n   finding, especially author or maintainer replies and version-specific facts.\n4. `Necessity`: the requested change is required for safety, correctness, or an applicable repository design or contract rule in the selected focus, not merely cleaner or preferable.\n5. `Scope`: this PR causes the problem, exposes it through behavior it owns, or\n   must address it to satisfy the linked issue.\n\nClassify failed candidates as an incomplete-evidence gap, non-blocking\nobservation, clarification question, pre-existing issue, or no issue. Do not\npublish non-blocking observations unless they materially help the user.\n\n## Review Incomplete Proof Gate\n\n`Review Incomplete` is a terminal evidence classification, not a fallback for unfinished analysis.\nClassify a gap as incomplete only when a specific outcome-sensitive decisive fact remains unavailable after every admissible evidence route has been attempted; if relevant local or public evidence exists or another allowed route remains, continue the review and classify the candidate.\nAfter authoritative scope is established, record each incomplete gap in the ledger with the missing fact, unavailable-evidence proof, affected full path, strongest alternatives checked, outcome impact, scope proof, and affected files, then run `scripts\u002Fmanage_review_ledger.py validate-incomplete --ledger \u003Cledger>` before selecting the result.\nIf authoritative scope cannot be established, state the exact unavailable scope fact and attempted routes in `### Required Evidence`; do not fabricate ledger scope.\n\n## Behavior Clusters and Risk Triage\n\nMap every substantive file to the smallest meaningful behavior cluster and identify each cluster's root cause, owner, entry paths, consumers, contracts, project-commitment delta, changed decisions, and validation points. Account explicitly for churn-only files.\n\nTriage functional boundaries, ownership and shared contracts, compatibility and rollback, test validity, concurrency and performance, security and operations, dependencies, packaging, and generated artifacts. Read only the triggered sections of [high-risk-review.md](references\u002Fhigh-risk-review.md). Also read [sql-parser-review.md](references\u002Fsql-parser-review.md) for SQL grammar, visitors, parser tests, syntax documentation, dialect behavior, or parser baselines.\n\n## Independent Review Coordination\n\nRead [review-coordination.md](references\u002Freview-coordination.md) through EOF for every top-level Formal Review, discussion reply that makes or changes an overall readiness conclusion, and assigned independent assessment.\nThat reference owns reviewer roles, cross-round confirmation, session records and review-material lifecycle; the single-assessment rules remain below.\n\n## Review Workflow\n\nApply this workflow to the canonical review basis without letting output mode or a previous result influence the assessment:\n\nStart every Formal Review round with fresh coverage of the complete effective candidate and its affected behavior and contracts, preserving the original task baseline and attributed scope.\nReuse only facts and verification results whose current-candidate validity is established; do not inherit reviewed-file statuses, discovery passes, proof conclusions, or convergence results.\nBefore repeating evidence acquisition, consult the current ledger's sources, block coverage, candidate findings and verification material, and reuse facts only while their supporting inputs and applicable coverage remain valid.\nAll three discovery lenses may share the same current source material, but each must still cover the complete candidate and sharing material does not replace the convergence pass.\n\n1. Complete `Repository Code Policy References`, then establish the authoritative effective-candidate scope and applicable requirements.\n2. Complete the Problem and Project Commitment Gate and establish the accepted behavior boundary.\n3. Confirm the selected review focus and admissible evidence.\n4. Build behavior clusters and complete the mandatory risk triage.\n5. Discover candidates across the complete scope through three lenses: root cause and behavior; blast radius and contracts; tests, runtime, and operations.\n6. Apply the Finding Proof Gate to every candidate. Keep discovery notes\n   private and classify every candidate before publication.\n7. Complete the Mandatory Style Verification Gate for a public PR or PR-backed local candidate.\n8. Consolidate findings by independent fix boundary and identify any gap that could change the blocker set.\n9. Run a convergence pass across the complete candidate and its affected behavior and contracts, including the latest delta.\n   If it finds a new independent candidate, return to step 6; otherwise freeze the assessment after the Completion Gate.\n\nIf an outcome-sensitive decisive fact passes the Review Incomplete Proof Gate, apply the Formal Decision Contract to the proven findings and remaining gap.\nOtherwise continue the review or request a split; do not produce a complete verdict from a partial review.\n\n## Completion Gate and Scripts\n\nApply the Completion Gate to every Formal Review and to a discussion reply that makes or changes an overall readiness conclusion.\n\n- Complete behavior-cluster mapping and risk triage for every authoritative file, including churn-only files.\n- Finish all three discovery lenses and classify every candidate.\n- Before accepting a behavior conclusion, identify the premises whose failure would change that conclusion and verify them against current behavior and the strongest applicable counter-evidence.\n- When such a premise remains unverified and admissible evidence is available, continue the review instead of treating the absence of a proven blocker as evidence for acceptance.\n- Complete the Mandatory Style Verification Gate against the latest effective candidate for every public PR or PR-backed local candidate.\n- Leave no unresolved gap that could change the blocker set and require a latest-candidate convergence pass with zero new independent candidates.\n- Use `scripts\u002Fbuild_review_inventory.py --format json` when local refs are available; its Markdown is only a bounded summary.\n- Use `scripts\u002Fmanage_review_ledger.py` for each independent assessment; it accounts for review state but does not judge correctness.\n- Initialize a new ledger for each round that requires one, from the full current inventory with pending file statuses and no inherited review passes.\n- Use the existing private system temporary directory and record the exact ledger path returned by initialization for this review.\n- Initialize with `--review-basis \u003CJSON>` containing the selected focus and readable sources identified by role and origin, so the ledger binds their actual content versions to the effective candidate, original baseline and authoritative files.\n- Record each substantive changed block's behavior, applicable risk axes and requirement origins, strongest counter-evidence and current source anchors with `mark-file --coverage \u003CJSON>`, and attach finding anchors with `add-finding --anchors \u003CJSON>`.\n- Record each evidenced `Needs Discussion` condition as a `confirmed` ledger issue about the project commitment or required decision, using `origin`, `evidence`, `full_path`, `necessity` and `scope_proof` to prove that requirement and `fix_boundary` for its specific decision boundary; do not invent a code defect.\n- For each newly introduced local override, compatibility exception or parallel mechanism, use the existing basis sources and block `requirements`, `counter_evidence` and `anchors` to record its constraint origins, verified limits of direct reuse and necessity conclusion separately from behavior correctness.\n- Keep author-only choices and unverified assumptions as `evidence` sources.\n- Record partial coverage with pending files and keep unproved findings as candidates; recording evidence does not establish a completed review.\n- Rebuild ledgers with an older schema or stale inputs without inheriting their completion state.\n- Validate the current basis and coverage before selecting a result; a passing ledger proves mechanical coverage and evidence freshness, while the reviewer must still establish semantic proof under the existing gates.\n- For a standalone local candidate with index or working-tree changes, provide the same exact task-path file to both scripts with `--candidate-files \u003Cpath>`. The scripts resolve those paths from the computed merge-base through the working tree, include matching untracked files, and fail when a listed path is unchanged.\n- Mutate one ledger sequentially; do not run ledger commands concurrently.\n- Batch related updates to one reviewer ledger with `scripts\u002Fmanage_review_ledger.py batch --ledger \u003Cledger> --operations \u003CJSON>`, where the JSON is a nonempty ordered array of argument arrays for `mark-file`, `add-finding` and `add-pass`, using their existing flags and input files without `--ledger`.\n- Each batch applies the existing operations in order and writes once only after all per-operation checks and both freshness checks pass.\n- Batch freshness checks verify the current basis and captured source anchors before applying operations and again before writing; any failed operation or freshness check leaves the original ledger unchanged.\n- Batching does not replace final ledger or session validation.\n\nUse these JSON shapes in local files passed to the arguments, replacing the example values with current evidence and block IDs from the initialized ledger:\nSources use `rule`, `requirement` or `evidence` roles; `--anchors` takes an anchor-array file shaped like `anchors` below.\nFor actual-value naming findings, pass `--rule java-testing.actual-value-naming --applicability \u003CJSON>` with one list entry per affected variable containing `variable`, `operation`, `role`, `declaration`, `operation_call`, and `use`.\nThe last three fields are zero-based indices into the finding's existing `anchors`, locating the declaration, tested call, and use or assertion in current candidate code lines; retain the complete test-method context needed to determine their roles.\nUse `actual-value`, `setup`, `expected`, or `unknown` for `role`; confirmation requires complete evidence with `actual-value`, while candidate and withdrawn findings may retain missing or contrary evidence.\nThese checks validate the recorded premises and their consistency, not Java semantics; derive applicability from the governing test rule and the complete method.\n\n```json\n{\"focus\": \"Code Correctness Review\", \"sources\": [{\"role\": \"rule\", \"origin\": \"CODE_OF_CONDUCT.md\", \"path\": \"CODE_OF_CONDUCT.md\"}]}\n```\n\n```json\n[\n  {\n    \"block\": \"\u003Cblock ID>\", \"behavior\": \"\u003Cverified behavior>\", \"risk_axes\": [\"contracts\"],\n    \"requirements\": [\"CODE_OF_CONDUCT.md\"], \"counter_evidence\": \"\u003Ccontrary scenario checked and result>\",\n    \"anchors\": [{\"side\": \"candidate\", \"path\": \"\u003Cchanged repository-relative path>\", \"start_line\": 1, \"end_line\": 2}]\n  }\n]\n```\n\nUse `base` for original content and `candidate` for effective content; text blocks need an anchor overlapping their changed lines, whole-object binary, mode or rename changes omit the line bounds, and `source` anchors require the declared source's matching origin and path.\n\nIf the gate cannot pass because a gap satisfies the Review Incomplete Proof Gate, apply the Formal Decision Contract's qualified negative rule before selecting the incomplete result.\nWhen no qualified negative result applies, return `Review Incomplete` in Formal Review and state the incomplete evidence without a formal verdict in a discussion reply.\nWhen confirmed blockers coexist with a proven gap that could hide more blockers, list them as confirmed partial facts but do not present them as the complete change-request set.\n\n## Formal Decision Contract\n\nIn Formal Review Mode, when a concrete failure prevents completing the required review or the current basis reaches its confirmation limit, automatically publish `Not Mergeable` if at least one current-candidate finding passes the Finding Proof Gate and substantive coordinator review.\nThe coordinator must verify candidate identity, source versions, the full failing path and strongest counter-evidence; unresolved facts or differences must not be capable of invalidating that finding.\nThis qualified negative result also applies when local Git objects, ledgers or session validation are unavailable but admissible immutable evidence independently proves the finding.\nUse the existing feedback-mode rules for the proven findings, including `Needs Discussion` for an evidenced required maintainer decision.\nA candidate, disputed, withdrawn or stale finding, a tool failure, or non-convergence alone cannot justify this result.\nThe exception permits a qualified negative report while full coverage or confirmation remains unfinished; it does not permit `Mergeable`, an exhaustive finding-set claim, a successful ledger or session-validation claim, or coding-task completion.\n\nFor a complete result, evaluate the Completion Gate and Independent Review Coordination, then apply the following mapping:\n\n1. If the gate fails because a gap satisfies the Review Incomplete Proof Gate and no qualified negative result applies, use `Review Incomplete`.\n2. If the Mandatory Style Verification Gate is incomplete for any applicable PR-impact file and no qualified negative result applies, use `Review Incomplete`.\n3. If Checkstyle or Spotless fails on an applicable PR-impact file, use `Not Mergeable` with `Feedback Mode: Change Request`.\n4. If admissible evidence disproves the problem model, expected behavior, ownership, protocol or SQL semantics, compatibility assumption, accepted project commitment, or solution direction, or establishes that a new project commitment still requires a maintainer decision, use `Not Mergeable` with `Feedback Mode: Needs Discussion`.\n5. If at least one candidate passes the Finding Proof Gate, use `Not Mergeable`\n   with `Feedback Mode: Change Request`.\n6. Otherwise use `Mergeable` for the selected focus.\n\n`Mergeable` in Code Correctness Review means code-scope readiness only. Required\npending CI prevents Mergeable in Mergeability Review. A relevant CI failure is\na blocker when attributable to the PR and an incomplete gap when attribution is\nunclear.\n\n## Local Candidate Scope\n\n- First classify the local candidate as standalone or as targeting an existing public PR.\n- For a standalone local candidate, use the active task's original working-tree baseline plus only its attributed local commits, index changes, and working-tree changes as the effective candidate. Use the frozen task boundary and task-delta audit as authoritative scope, exclude unrelated local changes, and do not require a public head, GitHub metadata, or public lineage.\n- Record the current round's authorized files and change intents separately from the full cumulative task-owned candidate and affected behavior and contracts to review.\n  A narrow fix authorization limits writes without shrinking that review scope or treating earlier task-owned changes as unrelated existing code.\n- For a local candidate targeting an existing PR, use the latest public PR head plus authorized local commits, index changes, and working-tree changes as the effective candidate. Verify with read-only Git that local `HEAD` equals or descends from the public head; if that relationship cannot be established, record the unavailable lineage as an incomplete gap, and if the refs prove divergence, resolve the correct review basis before selecting a verdict.\n- Review a PR-backed local candidate from the public PR merge-base through the working tree, use the union of GitHub files and the authorized local delta, and exclude unrelated local changes.\n- Apply Code Correctness Review through the canonical assessment, including the same proof and completion gates, triggered high-risk criteria, convergence loop, and Formal Decision Contract.\n- In `### Coverage`, identify whether the candidate is standalone or PR-backed and record its baseline and attributed local delta. For a PR-backed candidate, identify authorized local changes separately from the public PR and never present them as the public PR state.\n- Keep this Skill review-only. The outer active implementation loop fixes safe in-scope findings and reruns Formal Review; scope expansion, architecture choices, and high-risk actions return to their existing authorization gates. This Skill never activates that loop.\n\n## Multi-Round and Challenged Findings\n\nRead [review-corrections.md](references\u002Freview-corrections.md) for previous feedback, finding-fix commits, challenged findings, or a disputed overall readiness conclusion.\nRe-evaluate the latest head, test prior findings against challenger evidence, withdraw unsupported blockers, and classify later findings under that reference.\n\n## Output Contract\n\nReturn every review output as one complete copy-ready Markdown report in a fenced block labelled `markdown`, in both output modes and every review round.\nKeep the selected mode's complete result inside that block, including corrections, findings, evidence, and coverage, without requiring a separate user request.\nThe outer completion workflow adds its required task status and evidence without repeating the complete review report.\n\nUse the user's language for formal results. Draft GitHub-facing discussion\nreplies in English unless the user requests another language. Use stable labels,\nrepository-relative file references with line numbers, public anchors, and\nsanitized command summaries. Never include internal drafts, reasoning traces,\nprivate context, local absolute paths, temporary paths, credentials, raw long\nlogs, or emojis.\n\n### Formal Review\n\nUse this format for both public-PR and local-candidate reviews.\n\nBegin the Formal Review with `### Summary` before `### Result`, explaining the concrete problem or goal motivating the PR, the affected scenario or impact, the actual change mechanism, the direction assessment and material limits in two to four concise sentences.\nExplain how the mechanism addresses that purpose, and distinguish verified effects from intended benefits that the evidence does not establish.\nKeep a required `### Correction` first, then give the current summary and result using only verified facts.\n\n- `Mergeable`: `### Result` with exactly one `Review Result: Mergeable` line and a concise reason; `### Evidence`; `### Coverage`.\n- `Not Mergeable`: `### Result` with exactly one `Review Result: Not Mergeable` line, one `Feedback Mode`, a `Blocking Issues: N` line, and a concise reason; `### Blocking Issues`; `### Coverage`.\n- `Review Incomplete`: `### Result` with exactly one `Review Result: Review Incomplete` line and a concise reason; `### Confirmed Issues` when any are already proven; `### Verified Facts`; `### Required Evidence`; `### Coverage`.\n\nFor a qualified negative result, use the `Not Mergeable` structure with `Review Status: Not Converged` and `Confirmed Blocking Issues: N` in place of `Blocking Issues: N`.\nState that the findings are a confirmed subset, and report the actual completed and unreviewed coverage, unresolved differences, failed or unavailable checks, and the reason confirmation could not finish.\n\nFor each reported issue, prefix its title with `[P0]`, `[P1]`, or `[P2]` according to the proven impact and urgency.\n\n- P0 (urgent): Critical failures requiring immediate action, such as severe data loss, critical security exposure, or widespread core-service outage.\n- P1 (high): Serious failures on supported paths that require prompt correction and do not meet P0.\n- P2 (normal): All other warranted issues, including ordinary or minor defects and violations of applicable coding standards.\n\nPriority expresses impact and urgency; determine proof, blocking status, feedback mode and overall result using the existing review gates.\n\nFor each blocking issue include:\n\n- `Evidence`: current public or sanitized verification anchor.\n- `Impact`: concrete failing behavior or contract.\n- `Required Change` for Change Request, or `Discussion Needed` for Needs\n  Discussion.\n\nDo not add patch-level changes after selecting Needs Discussion.\nDo not include placeholder headings.\nIn `### Coverage`, give a short verification summary, normally one to three lines, with the candidate type and baseline or head, reviewed scope, relevant check status, CI scope, and material gaps or failures.\nKeep the complete requirements and project-commitment basis, behavior clusters, discovery lenses, independent assessments and stages, adjudication and resolution of differences, file inventory, verification commands and exit codes, and `Not Applicable` checks with their bases in private review material.\nReport the failed-check evidence required by the Mandatory Style Verification Gate and every limitation needed to interpret the result; brevity never waives internal review or verification.\nFor a standalone local candidate, identify the task baseline and attributed local delta; for a PR-backed candidate, identify authorized local commits, index changes, or working-tree changes separately from the public PR state.\nIn Code Correctness Review, state that the result is code-scope only and CI was not reviewed while distinguishing the completed local style verification from CI.\n\n### PR Discussion Reply\n\nReturn only the copy-ready reply.\nState whether the finding is retained, withdrawn, or needs clarification, then give the public evidence and minimum next action.\nDo not force a formal verdict.\n\n### Correction\n\nBegin with `### Correction`, then `Previous Finding or Conclusion`, `Current Status` (`Retained`, `Withdrawn`, or `Changed to Review Incomplete`), and `Reason`.\nFollow with the applicable current result while keeping exactly one formal `Review Result` line when a formal result is requested.\n","# Review PR\n\n## Purpose and Modes\n\nJudge the latest reviewed scope from root cause, behavior, contracts, tests, and\npublic or user-authorized repository evidence. Select one output mode:\n\n- `Formal Review Mode`: return one formal result for a public PR review, authorized local-candidate review, code-readiness judgment, mergeability decision, or CI review.\n- `PR Discussion Reply Mode`: return a copy-ready committer reply only when the user explicitly requests a review-thread response, author or maintainer objection reply, or challenged-finding reply. Do not add a formal verdict unless requested.\n\nUse Formal Review Mode for every explicit code or PR review and every Formal Review required by the repository completion route.\nIdentify a local candidate and its local-only delta in `### Coverage`; do not create a separate local-preflight result format or describe local-only work as the public PR state.\n\n## Review Focus\n\nReview focus is independent from output mode.\n\n| Focus | Use when | CI behavior |\n|---|---|---|\n| `Code Correctness Review` | Default review of code, tests, behavior, scope, or regression risk | Do not query, wait for, or report GitHub Actions, checks, workflow runs, or Actions logs |\n| `Mergeability Review` | The user asks whether the PR can be merged, approved, or landed | Review code and required CI or checks |\n| `CI Review` | The user asks about checks, Actions, logs, or CI failures | Treat CI evidence as the primary target |\n\nExplicit user scope wins. Formal Review of a local candidate uses `Code Correctness Review` unless the user explicitly requests CI.\n\nIn Code Correctness Review, unreviewed CI is not an evidence gap. Runtime facts\nmay still be required from code, official specifications, public reproductions,\nor local verification. If such a decisive fact is unavailable, identify that\nfact—not CI—as the incomplete reason.\n\n## Canonical Assessment\n\nResolve one review basis before discovery: the effective candidate, applicable requirements, accepted behavior and project commitments, selected review focus, and admissible evidence. Run the Review Workflow against that basis and produce one mode-independent assessment:\nconfirmed findings consolidated by fix boundary, needs-discussion conditions,\nincomplete-evidence gaps, and Completion Gate state.\n\nRecord each applicable requirement's source, content version, scope and valid exceptions in readable basis source material; a task-only requirement applies only to its authorized task candidate and must not become a universal repository or public-PR rule.\nReconstruct those requirements from original user requests and maintained contracts before checking the author's proposed solution, distinguishing author choices and unverified assumptions from confirmed constraints.\nDo not promote an unverified inference into a requirement for a new interface, SPI, behavior, or test.\nPreserve later user approvals with their actual provenance instead of treating approval of an implementation choice as proof of an original version requirement or of its necessity.\nKeep effective content and delta identity separate from Git revision lineage so equal local and public candidates retain one code-correctness basis.\n\nOutput mode must not affect candidate discovery, proof, classification,\ncoverage, or convergence. Never use a previous Formal Review result as\nevidence or as a conclusion to match. Treat previous public findings only as\nhypotheses whose cited facts must be reverified.\n\nCompleted coordinated reviews with the same effective candidate, requirements, focus, and evidence must produce the same canonical overall assessment.\nIndividual independent assessments may discover different candidates; the coordinator verifies and adjudicates their cumulative findings under Independent Review Coordination.\nPublic-PR and local-candidate reviews may resolve different candidates, but they must apply the same code-correctness judgment and Formal Review result mapping. A changed focus, requirement,\nor external fact changes the review basis and may legitimately change the\nassessment. Mergeability or CI evidence may add external-state findings or\ngaps, but it must not change code-correctness findings derived from an otherwise\nunchanged basis.\n\n## Core Contracts\n\n1. Review only. Do not modify PR code, post comments, submit reviews, resolve\n   threads, rerun workflows, or change remote state without explicit authority.\n2. Public-PR Formal Review scope is the latest target PR head and the complete GitHub changed-file list; use local triple-dot semantics when reproducing it. Local-candidate Formal Review scope follows `Local Candidate Scope` below. A discussion reply starts from the latest head, thread context, and affected behavior; expand to complete scope only when the claim depends on it.\n3. Public community conclusions use only public evidence and sanitized\n   verification summaries. Private-repository conclusions may use authorized\n   repository evidence but must remain within the user-authorized task and\n   target repository.\n4. Reconstruct `trigger -> failing path -> observed result -> expected\n   behavior` before judging the patch. A fallback, default, null check,\n   try-catch, or swallowed error is not a root-cause repair unless it fixes the\n   owning contract.\n5. Treat every concern as a candidate until it passes the Finding Proof Gate.\n6. Do not turn uncertainty, inaccessible evidence, tool failure, skipped\n   verification, or uninspected counter-evidence into a blocker.\n7. In Formal Review, complete the required review and do not stop at the first blocker.\n   Consolidate findings by independent fix boundary and return the complete current-head set once after the Completion Gate.\n   Before that gate, publish only an explicitly requested status, narrow review or early high-risk blocker, or the qualified negative result defined in the Formal Decision Contract.\n8. Follow `AGENTS.md` for repository authority, evidence, scope, safety, and sensitive data, and follow the applicable canonical references below for implementation, testing, contract, non-regression, and verification criteria.\n\n## Repository Code Policy References\n\nStandalone review is read-only and does not activate `code-implementation` or acquire write authority. Before judging the effective candidate, read [implementation rules](..\u002Fcode-implementation\u002Freferences\u002Frules\u002Fimplementation.md), [non-regression rules](..\u002Fcode-implementation\u002Freferences\u002Frules\u002Fnon-regression.md), and [verification rules](..\u002Fcode-implementation\u002Freferences\u002Fverification.md) through EOF. Also read [testing rules](..\u002Fcode-implementation\u002Freferences\u002Frules\u002Ftesting.md) when tests or coverage matter, and [artifact removal and contract impact rules](..\u002Fcode-implementation\u002Freferences\u002Frules\u002Fartifact-removal-and-contract-impact.md) when their trigger matches. Reuse an exact reference already read by the outer implementation workflow.\nBefore judging reviewed code or Maven POM changes, read [coding standards](..\u002Fcoding-standards\u002FSKILL.md) through EOF and use its Implementation Guidance Mode.\n\n## Problem and Project Commitment Gate\n\nComplete this gate before implementation-detail discovery; it establishes the review basis but does not waive the Finding Proof, Mandatory Style Verification, Completion, or convergence gates.\n\n1. Reconstruct the problem and expected behavior from the PR, linked issue when present, official documentation, maintained contracts, current code, and tests.\n2. For a defect, trace the failing path to the violated contract and its maintained owner; for another PR type, establish the goal and responsibilities it must preserve.\n3. Trace the patch's actual mechanism and compare it with a repair or reuse path in that owner; record why the chosen boundary addresses the cause or accepted goal and what remains outside scope.\n4. Verify outcome-sensitive assumptions about external calls, dependency versions, configuration and lifecycle, including side effects and resource cost on already-correct supported paths, before accepting the direction.\n5. Classify the requested outcome as preserving an accepted contract or adding a project commitment such as new semantics, configuration, API or SPI, compatibility, topology, database, dialect, or cross-module support.\n6. For Apache ShardingSphere, establish that ShardingSphere owns the behavior and that official project positioning, maintained contracts, or an explicit public maintainer decision accepts every new commitment; for an authorized downstream repository, apply equivalent target-project evidence available within the user-authorized repository boundary.\n7. Identify the narrowest accepted user-visible behavior and compare it with the patch's public contract, shared abstractions, compatibility surface, documentation, and tests.\n8. Check whether the change creates precedent or consistency pressure beyond the accepted behavior; an exact existing behavior or special case does not authorize broader generalization.\n\nAn open or labeled issue, popularity, contributor effort, available code, passing tests, or a small diff do not establish project acceptance.\nWhen evidence disproves the problem, expected behavior, applicable project ownership, or an asserted accepted commitment, or when a new commitment still requires a maintainer decision, record a `Needs Discussion` condition.\nWhen the behavior is accepted but the patch adds unsupported generalization, public surface, parallel models, or abstractions without a real stable boundary, treat the excess as a finding candidate under the implementation rules; patch size or novelty alone is not evidence of overdesign.\nWhen a decisive acceptance or ownership fact is unavailable after every admissible route, apply the Review Incomplete Proof Gate instead of converting uncertainty into `Needs Discussion`.\n\n## Scope and Evidence\n\nRead [evidence-access.md](references\u002Fevidence-access.md) and complete its GitHub Access Preflight before any GitHub request. It owns public-read selection, current-head identity, authoritative file scope, local-style evidence, failure attribution, CI, external behavior, and evidence hygiene. Apply its Local Style Verification Evidence to every public-PR or PR-backed local-candidate Formal Review.\n\nFor public-PR or PR-backed local-candidate formal reviews, establish the latest public head and base, authoritative files and requirements, relevant public discussion, and any authorized local delta.\nStandalone candidates follow `Local Candidate Scope`.\nFor discussion replies, establish the complete current thread and affected paths; obtain the full file list when scope or readiness is disputed.\nEarlier findings do not prove current-head readiness.\n\nTreat AI-assistance disclosure only as an explicit mergeability or policy-compliance concern. Apply `AI_POLICY.md` only when public evidence establishes material AI assistance; never infer it from code, prose, metadata, or a classifier.\n\n## Mandatory Style Verification Gate\n\nApply this gate to every Formal Review of a public PR and every PR-backed local candidate.\nThis gate is local candidate verification rather than a GitHub CI query, so every Review Focus must complete it even when Code Correctness Review does not read GitHub Actions, checks, workflow runs, or Actions logs.\n\n1. Derive the applicable PR-impact files and their owning Maven modules from the authoritative changed-file list for the effective candidate.\n2. Treat production and test Java files as applicable to both Checkstyle and Spotless unless repository configuration proves that a check does not govern a file.\n3. Run both checks against the latest public PR head or an accurate PR-backed local candidate that contains the latest public head and only its authorized local delta.\n4. Invalidate Checkstyle and Spotless evidence only where checked files, effective configuration, tool identity and inputs or applicable coverage changed.\n   Existing runs satisfy step 3 only after proof that the current accurate candidate contains the latest public head and that checked files, effective configuration, tool identity and inputs, and the complete applicable scope are unchanged.\n5. Use a whole-repository check, complete affected-module checks, or an exact-file check only when the command output and file inventory prove that the selected scope covers every applicable PR-impact file.\n6. Expand verification to the complete rule impact, normally the whole repository, when the PR changes global Checkstyle or Spotless configuration, a parent POM, or another cross-module style rule.\n7. Treat an exit code of zero as passing evidence only when the output also proves that every applicable PR-impact file was selected; a successful command that matched no intended file is not evidence.\n8. Do not use passing CI, required checks, commit statuses or a PR comment summary to satisfy or waive this gate.\n   An older local result counts only when the unchanged-input and current-candidate coverage proof above is complete.\n9. Do not run `spotless:apply` or another file-modifying formatter during review.\n\nMap the gate result before applying the remaining Formal Decision Contract.\n\n- If Checkstyle or Spotless fails on an applicable PR-impact file, return `Not Mergeable` with `Feedback Mode: Change Request`.\n- A style-check failure result must include `Feedback Mode: Change Request` and the blocking-issue count in `### Result`, then identify each failed check and affected PR-impact file in `### Blocking Issues`.\n- A style-check failure result must also include `### Coverage` with the effective candidate SHA, authoritative files accounted for, failed command, exit code, and affected PR-impact file.\n- If environment, dependency, candidate-materialization, tool, or coverage-proof failure leaves any applicable PR-impact file unverified, apply the Formal Decision Contract's qualified negative rule; otherwise return `Review Incomplete`.\n- If a module-scoped command fails only on unchanged files, narrow the check reliably or compare the base and effective candidate before attribution; do not classify the PR from that module failure alone.\n- If a check has no applicable PR-impact file, record `Not Applicable` and the repository-configuration basis in `### Coverage`.\n- Only successful current-candidate evidence for both checks, or an explicit not-applicable determination for either check, permits the remaining Formal Decision Contract to select `Mergeable`.\n\n## Finding Proof Gate\n\nA candidate may become a blocking issue only when all five conditions hold:\n\n1. `Evidence`: current code, diff, contract, test, log, CI, public reproduction,\n   official documentation, or generated artifact directly supports the claim.\n2. `Full path`: trace the relevant production or test entry path end to end;\n   inspect setup, wrappers, earlier calls, generators, and consuming runtime.\n3. `Counter-evidence`: check the strongest evidence that could disprove the\n   finding, especially author or maintainer replies and version-specific facts.\n4. `Necessity`: the requested change is required for safety, correctness, or an applicable repository design or contract rule in the selected focus, not merely cleaner or preferable.\n5. `Scope`: this PR causes the problem, exposes it through behavior it owns, or\n   must address it to satisfy the linked issue.\n\nClassify failed candidates as an incomplete-evidence gap, non-blocking\nobservation, clarification question, pre-existing issue, or no issue. Do not\npublish non-blocking observations unless they materially help the user.\n\n## Review Incomplete Proof Gate\n\n`Review Incomplete` is a terminal evidence classification, not a fallback for unfinished analysis.\nClassify a gap as incomplete only when a specific outcome-sensitive decisive fact remains unavailable after every admissible evidence route has been attempted; if relevant local or public evidence exists or another allowed route remains, continue the review and classify the candidate.\nAfter authoritative scope is established, record each incomplete gap in the ledger with the missing fact, unavailable-evidence proof, affected full path, strongest alternatives checked, outcome impact, scope proof, and affected files, then run `scripts\u002Fmanage_review_ledger.py validate-incomplete --ledger \u003Cledger>` before selecting the result.\nIf authoritative scope cannot be established, state the exact unavailable scope fact and attempted routes in `### Required Evidence`; do not fabricate ledger scope.\n\n## Behavior Clusters and Risk Triage\n\nMap every substantive file to the smallest meaningful behavior cluster and identify each cluster's root cause, owner, entry paths, consumers, contracts, project-commitment delta, changed decisions, and validation points. Account explicitly for churn-only files.\n\nTriage functional boundaries, ownership and shared contracts, compatibility and rollback, test validity, concurrency and performance, security and operations, dependencies, packaging, and generated artifacts. Read only the triggered sections of [high-risk-review.md](references\u002Fhigh-risk-review.md). Also read [sql-parser-review.md](references\u002Fsql-parser-review.md) for SQL grammar, visitors, parser tests, syntax documentation, dialect behavior, or parser baselines.\n\n## Independent Review Coordination\n\nRead [review-coordination.md](references\u002Freview-coordination.md) through EOF for every top-level Formal Review, discussion reply that makes or changes an overall readiness conclusion, and assigned independent assessment.\nThat reference owns reviewer roles, cross-round confirmation, session records and review-material lifecycle; the single-assessment rules remain below.\n\n## Review Workflow\n\nApply this workflow to the canonical review basis without letting output mode or a previous result influence the assessment:\n\nStart every Formal Review round with fresh coverage of the complete effective candidate and its affected behavior and contracts, preserving the original task baseline and attributed scope.\nReuse only facts and verification results whose current-candidate validity is established; do not inherit reviewed-file statuses, discovery passes, proof conclusions, or convergence results.\nBefore repeating evidence acquisition, consult the current ledger's sources, block coverage, candidate findings and verification material, and reuse facts only while their supporting inputs and applicable coverage remain valid.\nAll three discovery lenses may share the same current source material, but each must still cover the complete candidate and sharing material does not replace the convergence pass.\n\n1. Complete `Repository Code Policy References`, then establish the authoritative effective-candidate scope and applicable requirements.\n2. Complete the Problem and Project Commitment Gate and establish the accepted behavior boundary.\n3. Confirm the selected review focus and admissible evidence.\n4. Build behavior clusters and complete the mandatory risk triage.\n5. Discover candidates across the complete scope through three lenses: root cause and behavior; blast radius and contracts; tests, runtime, and operations.\n6. Apply the Finding Proof Gate to every candidate. Keep discovery notes\n   private and classify every candidate before publication.\n7. Complete the Mandatory Style Verification Gate for a public PR or PR-backed local candidate.\n8. Consolidate findings by independent fix boundary and identify any gap that could change the blocker set.\n9. Run a convergence pass across the complete candidate and its affected behavior and contracts, including the latest delta.\n   If it finds a new independent candidate, return to step 6; otherwise freeze the assessment after the Completion Gate.\n\nIf an outcome-sensitive decisive fact passes the Review Incomplete Proof Gate, apply the Formal Decision Contract to the proven findings and remaining gap.\nOtherwise continue the review or request a split; do not produce a complete verdict from a partial review.\n\n## Completion Gate and Scripts\n\nApply the Completion Gate to every Formal Review and to a discussion reply that makes or changes an overall readiness conclusion.\n\n- Complete behavior-cluster mapping and risk triage for every authoritative file, including churn-only files.\n- Finish all three discovery lenses and classify every candidate.\n- Before accepting a behavior conclusion, identify the premises whose failure would change that conclusion and verify them against current behavior and the strongest applicable counter-evidence.\n- When such a premise remains unverified and admissible evidence is available, continue the review instead of treating the absence of a proven blocker as evidence for acceptance.\n- Complete the Mandatory Style Verification Gate against the latest effective candidate for every public PR or PR-backed local candidate.\n- Leave no unresolved gap that could change the blocker set and require a latest-candidate convergence pass with zero new independent candidates.\n- Use `scripts\u002Fbuild_review_inventory.py --format json` when local refs are available; its Markdown is only a bounded summary.\n- Use `scripts\u002Fmanage_review_ledger.py` for each independent assessment; it accounts for review state but does not judge correctness.\n- Initialize a new ledger for each round that requires one, from the full current inventory with pending file statuses and no inherited review passes.\n- Use the existing private system temporary directory and record the exact ledger path returned by initialization for this review.\n- Initialize with `--review-basis \u003CJSON>` containing the selected focus and readable sources identified by role and origin, so the ledger binds their actual content versions to the effective candidate, original baseline and authoritative files.\n- Record each substantive changed block's behavior, applicable risk axes and requirement origins, strongest counter-evidence and current source anchors with `mark-file --coverage \u003CJSON>`, and attach finding anchors with `add-finding --anchors \u003CJSON>`.\n- Record each evidenced `Needs Discussion` condition as a `confirmed` ledger issue about the project commitment or required decision, using `origin`, `evidence`, `full_path`, `necessity` and `scope_proof` to prove that requirement and `fix_boundary` for its specific decision boundary; do not invent a code defect.\n- For each newly introduced local override, compatibility exception or parallel mechanism, use the existing basis sources and block `requirements`, `counter_evidence` and `anchors` to record its constraint origins, verified limits of direct reuse and necessity conclusion separately from behavior correctness.\n- Keep author-only choices and unverified assumptions as `evidence` sources.\n- Record partial coverage with pending files and keep unproved findings as candidates; recording evidence does not establish a completed review.\n- Rebuild ledgers with an older schema or stale inputs without inheriting their completion state.\n- Validate the current basis and coverage before selecting a result; a passing ledger proves mechanical coverage and evidence freshness, while the reviewer must still establish semantic proof under the existing gates.\n- For a standalone local candidate with index or working-tree changes, provide the same exact task-path file to both scripts with `--candidate-files \u003Cpath>`. The scripts resolve those paths from the computed merge-base through the working tree, include matching untracked files, and fail when a listed path is unchanged.\n- Mutate one ledger sequentially; do not run ledger commands concurrently.\n- Batch related updates to one reviewer ledger with `scripts\u002Fmanage_review_ledger.py batch --ledger \u003Cledger> --operations \u003CJSON>`, where the JSON is a nonempty ordered array of argument arrays for `mark-file`, `add-finding` and `add-pass`, using their existing flags and input files without `--ledger`.\n- Each batch applies the existing operations in order and writes once only after all per-operation checks and both freshness checks pass.\n- Batch freshness checks verify the current basis and captured source anchors before applying operations and again before writing; any failed operation or freshness check leaves the original ledger unchanged.\n- Batching does not replace final ledger or session validation.\n\nUse these JSON shapes in local files passed to the arguments, replacing the example values with current evidence and block IDs from the initialized ledger:\nSources use `rule`, `requirement` or `evidence` roles; `--anchors` takes an anchor-array file shaped like `anchors` below.\nFor actual-value naming findings, pass `--rule java-testing.actual-value-naming --applicability \u003CJSON>` with one list entry per affected variable containing `variable`, `operation`, `role`, `declaration`, `operation_call`, and `use`.\nThe last three fields are zero-based indices into the finding's existing `anchors`, locating the declaration, tested call, and use or assertion in current candidate code lines; retain the complete test-method context needed to determine their roles.\nUse `actual-value`, `setup`, `expected`, or `unknown` for `role`; confirmation requires complete evidence with `actual-value`, while candidate and withdrawn findings may retain missing or contrary evidence.\nThese checks validate the recorded premises and their consistency, not Java semantics; derive applicability from the governing test rule and the complete method.\n\n```json\n{\"focus\": \"Code Correctness Review\", \"sources\": [{\"role\": \"rule\", \"origin\": \"CODE_OF_CONDUCT.md\", \"path\": \"CODE_OF_CONDUCT.md\"}]}\n```\n\n```json\n[\n  {\n    \"block\": \"\u003Cblock ID>\", \"behavior\": \"\u003Cverified behavior>\", \"risk_axes\": [\"contracts\"],\n    \"requirements\": [\"CODE_OF_CONDUCT.md\"], \"counter_evidence\": \"\u003Ccontrary scenario checked and result>\",\n    \"anchors\": [{\"side\": \"candidate\", \"path\": \"\u003Cchanged repository-relative path>\", \"start_line\": 1, \"end_line\": 2}]\n  }\n]\n```\n\nUse `base` for original content and `candidate` for effective content; text blocks need an anchor overlapping their changed lines, whole-object binary, mode or rename changes omit the line bounds, and `source` anchors require the declared source's matching origin and path.\n\nIf the gate cannot pass because a gap satisfies the Review Incomplete Proof Gate, apply the Formal Decision Contract's qualified negative rule before selecting the incomplete result.\nWhen no qualified negative result applies, return `Review Incomplete` in Formal Review and state the incomplete evidence without a formal verdict in a discussion reply.\nWhen confirmed blockers coexist with a proven gap that could hide more blockers, list them as confirmed partial facts but do not present them as the complete change-request set.\n\n## Formal Decision Contract\n\nIn Formal Review Mode, when a concrete failure prevents completing the required review or the current basis reaches its confirmation limit, automatically publish `Not Mergeable` if at least one current-candidate finding passes the Finding Proof Gate and substantive coordinator review.\nThe coordinator must verify candidate identity, source versions, the full failing path and strongest counter-evidence; unresolved facts or differences must not be capable of invalidating that finding.\nThis qualified negative result also applies when local Git objects, ledgers or session validation are unavailable but admissible immutable evidence independently proves the finding.\nUse the existing feedback-mode rules for the proven findings, including `Needs Discussion` for an evidenced required maintainer decision.\nA candidate, disputed, withdrawn or stale finding, a tool failure, or non-convergence alone cannot justify this result.\nThe exception permits a qualified negative report while full coverage or confirmation remains unfinished; it does not permit `Mergeable`, an exhaustive finding-set claim, a successful ledger or session-validation claim, or coding-task completion.\n\nFor a complete result, evaluate the Completion Gate and Independent Review Coordination, then apply the following mapping:\n\n1. If the gate fails because a gap satisfies the Review Incomplete Proof Gate and no qualified negative result applies, use `Review Incomplete`.\n2. If the Mandatory Style Verification Gate is incomplete for any applicable PR-impact file and no qualified negative result applies, use `Review Incomplete`.\n3. If Checkstyle or Spotless fails on an applicable PR-impact file, use `Not Mergeable` with `Feedback Mode: Change Request`.\n4. If admissible evidence disproves the problem model, expected behavior, ownership, protocol or SQL semantics, compatibility assumption, accepted project commitment, or solution direction, or establishes that a new project commitment still requires a maintainer decision, use `Not Mergeable` with `Feedback Mode: Needs Discussion`.\n5. If at least one candidate passes the Finding Proof Gate, use `Not Mergeable`\n   with `Feedback Mode: Change Request`.\n6. Otherwise use `Mergeable` for the selected focus.\n\n`Mergeable` in Code Correctness Review means code-scope readiness only. Required\npending CI prevents Mergeable in Mergeability Review. A relevant CI failure is\na blocker when attributable to the PR and an incomplete gap when attribution is\nunclear.\n\n## Local Candidate Scope\n\n- First classify the local candidate as standalone or as targeting an existing public PR.\n- For a standalone local candidate, use the active task's original working-tree baseline plus only its attributed local commits, index changes, and working-tree changes as the effective candidate. Use the frozen task boundary and task-delta audit as authoritative scope, exclude unrelated local changes, and do not require a public head, GitHub metadata, or public lineage.\n- Record the current round's authorized files and change intents separately from the full cumulative task-owned candidate and affected behavior and contracts to review.\n  A narrow fix authorization limits writes without shrinking that review scope or treating earlier task-owned changes as unrelated existing code.\n- For a local candidate targeting an existing PR, use the latest public PR head plus authorized local commits, index changes, and working-tree changes as the effective candidate. Verify with read-only Git that local `HEAD` equals or descends from the public head; if that relationship cannot be established, record the unavailable lineage as an incomplete gap, and if the refs prove divergence, resolve the correct review basis before selecting a verdict.\n- Review a PR-backed local candidate from the public PR merge-base through the working tree, use the union of GitHub files and the authorized local delta, and exclude unrelated local changes.\n- Apply Code Correctness Review through the canonical assessment, including the same proof and completion gates, triggered high-risk criteria, convergence loop, and Formal Decision Contract.\n- In `### Coverage`, identify whether the candidate is standalone or PR-backed and record its baseline and attributed local delta. For a PR-backed candidate, identify authorized local changes separately from the public PR and never present them as the public PR state.\n- Keep this Skill review-only. The outer active implementation loop fixes safe in-scope findings and reruns Formal Review; scope expansion, architecture choices, and high-risk actions return to their existing authorization gates. This Skill never activates that loop.\n\n## Multi-Round and Challenged Findings\n\nRead [review-corrections.md](references\u002Freview-corrections.md) for previous feedback, finding-fix commits, challenged findings, or a disputed overall readiness conclusion.\nRe-evaluate the latest head, test prior findings against challenger evidence, withdraw unsupported blockers, and classify later findings under that reference.\n\n## Output Contract\n\nReturn every review output as one complete copy-ready Markdown report in a fenced block labelled `markdown`, in both output modes and every review round.\nKeep the selected mode's complete result inside that block, including corrections, findings, evidence, and coverage, without requiring a separate user request.\nThe outer completion workflow adds its required task status and evidence without repeating the complete review report.\n\nUse the user's language for formal results. Draft GitHub-facing discussion\nreplies in English unless the user requests another language. Use stable labels,\nrepository-relative file references with line numbers, public anchors, and\nsanitized command summaries. Never include internal drafts, reasoning traces,\nprivate context, local absolute paths, temporary paths, credentials, raw long\nlogs, or emojis.\n\n### Formal Review\n\nUse this format for both public-PR and local-candidate reviews.\n\nBegin the Formal Review with `### Summary` before `### Result`, explaining the concrete problem or goal motivating the PR, the affected scenario or impact, the actual change mechanism, the direction assessment and material limits in two to four concise sentences.\nExplain how the mechanism addresses that purpose, and distinguish verified effects from intended benefits that the evidence does not establish.\nKeep a required `### Correction` first, then give the current summary and result using only verified facts.\n\n- `Mergeable`: `### Result` with exactly one `Review Result: Mergeable` line and a concise reason; `### Evidence`; `### Coverage`.\n- `Not Mergeable`: `### Result` with exactly one `Review Result: Not Mergeable` line, one `Feedback Mode`, a `Blocking Issues: N` line, and a concise reason; `### Blocking Issues`; `### Coverage`.\n- `Review Incomplete`: `### Result` with exactly one `Review Result: Review Incomplete` line and a concise reason; `### Confirmed Issues` when any are already proven; `### Verified Facts`; `### Required Evidence`; `### Coverage`.\n\nFor a qualified negative result, use the `Not Mergeable` structure with `Review Status: Not Converged` and `Confirmed Blocking Issues: N` in place of `Blocking Issues: N`.\nState that the findings are a confirmed subset, and report the actual completed and unreviewed coverage, unresolved differences, failed or unavailable checks, and the reason confirmation could not finish.\n\nFor each reported issue, prefix its title with `[P0]`, `[P1]`, or `[P2]` according to the proven impact and urgency.\n\n- P0 (urgent): Critical failures requiring immediate action, such as severe data loss, critical security exposure, or widespread core-service outage.\n- P1 (high): Serious failures on supported paths that require prompt correction and do not meet P0.\n- P2 (normal): All other warranted issues, including ordinary or minor defects and violations of applicable coding standards.\n\nPriority expresses impact and urgency; determine proof, blocking status, feedback mode and overall result using the existing review gates.\n\nFor each blocking issue include:\n\n- `Evidence`: current public or sanitized verification anchor.\n- `Impact`: concrete failing behavior or contract.\n- `Required Change` for Change Request, or `Discussion Needed` for Needs\n  Discussion.\n\nDo not add patch-level changes after selecting Needs Discussion.\nDo not include placeholder headings.\nIn `### Coverage`, give a short verification summary, normally one to three lines, with the candidate type and baseline or head, reviewed scope, relevant check status, CI scope, and material gaps or failures.\nKeep the complete requirements and project-commitment basis, behavior clusters, discovery lenses, independent assessments and stages, adjudication and resolution of differences, file inventory, verification commands and exit codes, and `Not Applicable` checks with their bases in private review material.\nReport the failed-check evidence required by the Mandatory Style Verification Gate and every limitation needed to interpret the result; brevity never waives internal review or verification.\nFor a standalone local candidate, identify the task baseline and attributed local delta; for a PR-backed candidate, identify authorized local commits, index changes, or working-tree changes separately from the public PR state.\nIn Code Correctness Review, state that the result is code-scope only and CI was not reviewed while distinguishing the completed local style verification from CI.\n\n### PR Discussion Reply\n\nReturn only the copy-ready reply.\nState whether the finding is retained, withdrawn, or needs clarification, then give the public evidence and minimum next action.\nDo not force a formal verdict.\n\n### Correction\n\nBegin with `### Correction`, then `Previous Finding or Conclusion`, `Current Status` (`Retained`, `Withdrawn`, or `Changed to Review Incomplete`), and `Reason`.\nFollow with the applicable current result while keeping exactly one formal `Review Result` line when a formal result is requested.\n",{"name":5,"description":7},"master","e38d2e32b3fec5b37e713789c4fb3c7ea0d4ae7d",".codex\u002Fskills\u002Freview-pr",6909,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fshardingsphere","https:\u002F\u002Fgithub.com\u002Fapache","https:\u002F\u002Fwww.apache.org\u002F","2026-11-13 15:26:32",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add apache\u002Fshardingsphere --skill review-pr",{"tool":57,"command":58},"bunx","bunx skills add apache\u002Fshardingsphere --skill review-pr",{"tool":60,"command":61},"pnpm","pnpm dlx skills add apache\u002Fshardingsphere --skill review-pr","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fapache\u002Fshardingsphere\u002Fblob\u002Fmaster\u002F.codex\u002Fskills\u002Freview-pr\u002FSKILL.md",true,[65,71,75,79,83,87,91,97,101,105,109,113],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"agents\u002Fopenai.yaml","REFERENCE","参考文档",1150,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fshardingsphere\u002Fblob\u002Fmaster\u002F.codex\u002Fskills\u002Freview-pr\u002Fagents\u002Fopenai.yaml",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fevidence-access.md",11021,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fshardingsphere\u002Fblob\u002Fmaster\u002F.codex\u002Fskills\u002Freview-pr\u002Freferences\u002Fevidence-access.md",{"path":76,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fhigh-risk-review.md",6262,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fshardingsphere\u002Fblob\u002Fmaster\u002F.codex\u002Fskills\u002Freview-pr\u002Freferences\u002Fhigh-risk-review.md",{"path":80,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Freview-coordination.md",15175,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fshardingsphere\u002Fblob\u002Fmaster\u002F.codex\u002Fskills\u002Freview-pr\u002Freferences\u002Freview-coordination.md",{"path":84,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Freview-corrections.md",5331,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fshardingsphere\u002Fblob\u002Fmaster\u002F.codex\u002Fskills\u002Freview-pr\u002Freferences\u002Freview-corrections.md",{"path":88,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fsql-parser-review.md",3201,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fshardingsphere\u002Fblob\u002Fmaster\u002F.codex\u002Fskills\u002Freview-pr\u002Freferences\u002Fsql-parser-review.md",{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002Fbuild_review_inventory.py","SCRIPT","脚本",8005,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fshardingsphere\u002Fblob\u002Fmaster\u002F.codex\u002Fskills\u002Freview-pr\u002Fscripts\u002Fbuild_review_inventory.py",{"path":98,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":99,"sourceHtmlUrl":100},"scripts\u002Fmanage_review_ledger.py",66712,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fshardingsphere\u002Fblob\u002Fmaster\u002F.codex\u002Fskills\u002Freview-pr\u002Fscripts\u002Fmanage_review_ledger.py",{"path":102,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":103,"sourceHtmlUrl":104},"scripts\u002Fresolve_review_scope.py",5924,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fshardingsphere\u002Fblob\u002Fmaster\u002F.codex\u002Fskills\u002Freview-pr\u002Fscripts\u002Fresolve_review_scope.py",{"path":106,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":107,"sourceHtmlUrl":108},"tests\u002Ftest_build_review_inventory.py",3210,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fshardingsphere\u002Fblob\u002Fmaster\u002F.codex\u002Fskills\u002Freview-pr\u002Ftests\u002Ftest_build_review_inventory.py",{"path":110,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":111,"sourceHtmlUrl":112},"tests\u002Ftest_manage_review_ledger.py",102416,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fshardingsphere\u002Fblob\u002Fmaster\u002F.codex\u002Fskills\u002Freview-pr\u002Ftests\u002Ftest_manage_review_ledger.py",{"path":114,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":115,"sourceHtmlUrl":116},"tests\u002Ftest_resolve_review_scope.py",4300,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fshardingsphere\u002Fblob\u002Fmaster\u002F.codex\u002Fskills\u002Freview-pr\u002Ftests\u002Ftest_resolve_review_scope.py",[118,143,174,196],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":38},"01M6ACARJQT4ESW4488DAETV2Q","gen-ut","Generate standard unit tests for one or more target classes in Apache ShardingSphere; cover requested behavior and every affected SUT-owned branch, enforce an explicitly requested numeric coverage target, and pass quality gates; perform explicit merge analysis, suitability filtering, and refactor optimization for parameterized tests.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fshardingsphere\u002Fblob\u002Fmaster\u002F.codex\u002Fskills\u002Fgen-ut\u002FSKILL.md",[],[125,126,127,128,129,22,130,131,132,133,134,135,136,137,138,32,139,140,9,141,142],"gen ut","ut","generate","coverage","standard","cover","more","affected","unit","tests","enforce","filtering","unit tests","branch","refactor","Optimization","quality gates","merge",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":154,"publishedAt":38},"01M6ACAM5EVNBXC2BQZGY023D1","coding-standards","Apply Apache ShardingSphere's written coding standards when explicitly requested, or when code-implementation routes task-changed production, test, script, build, generated, or Maven POM artifacts through repository standards. Also perform a standalone read-only compliance audit of a user-specified scope. Use CODE_OF_CONDUCT.md, applicable AGENTS.md rules, Checkstyle, Spotless, and other repository-defined standards, including naming and evidence-based defensive-code rules. Do not invoke independently for an ordinary implementation already governed by code-implementation, and do not independently audit architecture, runtime ownership, caches, or lifecycle.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fshardingsphere\u002Fblob\u002Fmaster\u002F.codex\u002Fskills\u002Fcoding-standards\u002FSKILL.md",[149],{"categoryNo":150,"categoryName":151,"taxonomyType":152,"taxonomyTypeDesc":153},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[155,156,157,158,159,160,161,162,163,164,165,166,167,168,169,34,170,36,171,172,173,9],"coding standards","coding","standards","pom","when","Compliance Audit","conduct","invoke","standalone","scope","checkstyle","do","only","generated","read","audit","artifacts","architecture","test",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":183,"publishedAt":38},"01M6ACAGSBYTZB9TDW4KD5776D","code-implementation","Implement, fix, refactor, or remove repository code under required scope, non-regression, verification, and review gates. Use whenever a task may change a production, test, script, or other implementation artifact, including build logic, generated source, and behavior-affecting configuration. Also use it alongside a specialized code-changing Skill. Do not use for read-only analysis or review, diagnosis-only work, or prose-only changes.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fshardingsphere\u002Fblob\u002Fmaster\u002F.codex\u002Fskills\u002Fcode-implementation\u002FSKILL.md",[180],{"categoryNo":181,"categoryName":182,"taxonomyType":152,"taxonomyTypeDesc":153},"01JBSEEDCAT000000000000030","开发工程师",[184,185,36,186,187,173,188,20,34,167,189,164,190,191,192,193,168,169,194,195,30,32],"implementation","code implementation","verification","change","implement","remove repository","diagnosis","artifact","remove","fix","specialized","work",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":202,"publishedAt":38},"01M6ACACEZ194A1CD28EH1QEDQ","analyze-issue","Used to analyze Apache ShardingSphere community issues. Emphasizes root-cause-first and evidence-first classification before conclusions, and produces copy-ready GitHub issue replies in the voice of an Apache ShardingSphere community maintainer.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fshardingsphere\u002Fblob\u002Fmaster\u002F.codex\u002Fskills\u002Fanalyze-issue\u002FSKILL.md",[],[203,204,205,206,207,208,209,210,211,26,27,212,213,214,9,215,216],"analyze issue","analyze","issue","root-cause","root","replies","copy","community","github issue","voice","classification","first","issues","github"]