skills.rest
tusharg1993
tusharg1993COMMUNITY
Explore all skills by this author →
GitHub

bisect

Run git bisect against master CI binaries to locate the first bad commit.

Updated Mar 10, 2026
Search Tags:#regression#bisect#clickhouse#git-bisect#ci-binaries
One-click install
npx skills add https://github.com/tusharg1993/ClickHouse --skill bisect-tusharg1993
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bisect
Source: https://github.com/tusharg1993/ClickHouse/tree/main/.claude/skills/bisect
Command: npx skills add https://github.com/tusharg1993/ClickHouse --skill bisect-tusharg1993

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bisect a ClickHouse regression efficiently by orchestrating git bisect with pre-built master binaries downloaded from CI, avoiding full rebuilds at each step.

Core Features & Use Cases

  • Automates the end-to-end bisect workflow across commits to identify the introduction point of a regression.
  • Leverages CI artifacts to test candidate commits without building from source, and provides guidance for reporting findings.
  • Use Case: If a failure appears after a release, run this skill to pinpoint the exact commit that introduced the bug and generate a minimal repro.

Quick Start

Provide a repro SQL file and run the bisect workflow against master binaries to identify the first bad commit.

Frequently Asked Questions about bisect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the first bad commit for a ClickHouse regression?▼

To find the first bad commit in a ClickHouse regression, you can run an automated git bisect workflow against pre-built master CI binaries to efficiently narrow down the exact introduction point of the bug without rebuilding from source.

What is the best way to run git bisect without building ClickHouse from source at every step?▼

The best way to run git bisect without building from source is to leverage pre-built master CI binaries. This approach downloads binary artifacts to test candidate commits directly, avoiding full rebuilds during the regression investigation.

Do I need a repro SQL file to start bisecting a ClickHouse regression?▼

Yes, you need a repro SQL file to start bisecting a ClickHouse regression. The workflow requires a repro workflow and a git bisect run-compatible test to classify each candidate commit as good or bad.

Can I use CI binaries to automate locating the exact commit that introduced a bug?▼

Yes, you can use CI binaries to automate locating the exact commit that introduced a bug. The bisect workflow orchestrates git bisect by downloading binary artifacts to test candidate commits across ClickHouse releases.

What do I need to access before automating a git bisect for my regression investigation?▼

Before automating a git bisect for your regression investigation, you need access to binary artifacts from CI, a repro workflow, and a git bisect run-compatible test to classify each candidate commit accurately.

Related Skills

Explore More Software Engineering Skills→
ArabelaTsoArabelaTso
142

git-bisect-assistant

Automate git bisect to identify the first bad commit with retry logic.

Community
Intermediate
JansenAnalyticsJansenAnalytics
5

git-bisect-auto

Automate git bisect to locate the first bad commit.

Community
Advanced
codacy-open-source-projects-scanscodacy-open-source-projects-scans
1

bisect

Automate regression bisection in ClickHouse using CI artifact binaries.

Official
Advanced
erigontecherigontech
3.6k

erigon-build

Build the Erigon binary from source using make erigon.

Official
Advanced