QuestDB

Investigate actionable QuestDB pull request findings, trace root causes and affected callers, and test a proposed fix against existing contracts. An independent reviewer checks the design before production edits and reviews the combined result before completion.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating the cause behind a PR finding
• Checking how a proposed fix affects callers and contracts
• Planning and validating a regression-tested change

Validate actionable findings from a QuestDB pull request review one at a time. Reproduce user-visible problems with regression tests where practical, make a focused and performant fix, run tests, and require an independent review before proceeding to the next finding.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Verify a pasted QuestDB review finding against the current code
• Reproduce a reported bug with a regression test
• Apply a focused fix and run relevant tests

Review a QuestDB pull request or local Git range for reachable bugs, compatibility issues, test gaps, and performance problems. The review checks surrounding code and callers, verifies evidence for each finding, and reports only issues that meet its admission criteria.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a QuestDB pull request before merge
• Checking a local commit range for regressions
• Assessing test coverage for changed behavior

Check a pull request’s CI status, summarize failed tests and build checks, and trace failures to the proposed changes. The skill can update test expectations when the cause and intended behavior are clear, and presents uncertain failures for discussion.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Summarizing failed checks on a pull request
• Finding test names and failure messages
• Updating an assertion after an intentional output change

Turn the latest review-pr report in the conversation into a change request on the pull request for the checked-out branch. It tags the PR author, requests changes, and removes the READY label when present; it does not conduct a new review.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Posting an existing review as a change request
• Marking a reviewed PR as changes requested
• Removing the READY label after rejecting a PR

Posts the latest review report as an approval on the pull request for the checked-out branch, then adds the “QUEUED FOR MERGE” label. It first checks that the review meets the stated approval criteria.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Approving a reviewed pull request
• Adding the merge queue label after approval
• Posting a review report to its pull request

Validate actionable QuestDB pull request findings against the code, trace their causes, and fix confirmed issues with regression tests and independent review. It helps preserve legitimate behavior while checking the combined changes before completion.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking whether a pasted PR review finding is real
• Reproducing a reported bug with a regression test
• Applying a focused fix and reviewing its impact

Debug failing QuestDB WAL fuzz tests involving column conversions and Parquet partitions. Use seeds and failure logs to trace column and partition history, compare WAL results with a non-WAL baseline, and add temporary state logging without changing the fuzz sequence.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reproducing a WAL fuzz failure from its seeds
• Tracing a column conversion mismatch
• Investigating Parquet and native partition differences

Investigate failing QuestDB WAL/O3 tests on the lazy geometry branch, focusing on composite partitions made of multiple pieces. Use seeds, logs, and partition invariants to trace the failure and build a deterministic reproducer when possible.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Tracing a failing WAL/O3 test
• Replaying a failure with fixed random seeds
• Building a deterministic partition reproducer

Review a GitHub pull request or local Git range against QuestDB standards. Trace changed behavior into surrounding code and callers, check tests and realistic user impact, and report verified issues at an appropriate severity while keeping speculative concerns out of the findings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review a QuestDB pull request before merging
• Inspect a local Git range, including working tree changes
• Trace a changed method's callers for regressions

Review a QuestDB GitHub pull request or local Git range for correctness, performance, tests, and coding standards. Select review depth from levels 0–3, trace affected callers, and report only findings supported by evidence with an appropriate severity.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a QuestDB GitHub pull request
• Checking a local Git range before merging
• Assessing whether a code change has effective test coverage