version unknown

continue-pr-auto

clickhouse@clickhouse⭐ 50.9k stars· last commit 3d ago· 6073 open issues

Unattended variant of continue-pr for automation (driven by utils/continue-all-prs.sh). Resolves conflicts - reworking stale features to reconcile with current master when a mechanical merge is not enough - fixes CI, addresses feedback, and pushes without ever asking the user. For interactive use, prefer continue-pr.

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

7.2/10
Verified
Oct 8, 2026

// RATINGS

⭐GitHub Stars
⭐⭐⭐⭐⭐ 50.9k on GitHubGitHub ↗

Very popular

🟢ProSkills ScoreAI Verified
7.2/10
📍

Not yet listed on ClawHub or SkillsMP

// README

Website Apache 2.0 License

How To Install (Linux, macOS, FreeBSD)

curl https://clickhouse.com/ | sh

Or skip the install: try ClickHouse Cloud for free and start querying in minutes.

Useful Links

  • Official website has a quick high-level overview of ClickHouse on the main page.
  • ClickHouse Cloud ClickHouse as a service, built by the creators and maintainers.
  • Tutorial shows how to set up and query a small ClickHouse cluster.
  • Documentation provides more in-depth information.
  • YouTube channel has a lot of content about ClickHouse in video format.
  • Slack and Telegram allow chatting with ClickHouse users in real-time.
  • Blog contains various ClickHouse-related articles, as well as announcements and reports about events.
  • X and LinkedIn for short news.
  • Code Browser (github.dev) with syntax highlighting, powered by github.dev.
  • Contact us to discuss your use case with a ClickHouse expert.

Monthly Release & Community Call

The ClickHouse 26.9 Release Call took place on September 17, 2026 — watch the recording and the slides.

The ClickHouse 26.8 Release Call took place on August 27, 2026 — watch the recording and the slides.

The ClickHouse 26.7 Release Call took place on July 23, 2026 — watch the recording and the slides.

The ClickHouse 26.6 special "10 Year Anniversary" Release Call — recording and slides.

Watch all release presentations and videos at ClickHouse Theater and YouTube Playlist.

Upcoming Events

Keep an eye out for upcoming meetups and events around the world. Want to speak? Apply here You can also peruse ClickHouse Events for a list of all upcoming trainings, meetups, speaking engagements, etc.

Upcoming meetups

Recent meetups

Recent Recordings

  • Recent Meetup Videos: Meetup Playlist Whenever possible recordings of the ClickHouse Community Meetups are edited and presented as individual talks.

Interested in joining ClickHouse and making it your full-time job?

ClickHouse is a nice DBMS, and it's a good place to work.

Check out our current openings here: https://clickhouse.com/company/careers

Email: [email protected]!

// HOW IT'S BUILT

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • .claude/skills/continue-pr-auto/SKILL.md33 KB748b75bc720dtruncatedupstream ↗

    Showing the inlined prefix. The rest is in the upstream file.

    ---
    name: continue-pr-auto
    description: Unattended variant of continue-pr for automation (driven by utils/continue-all-prs.sh). Resolves conflicts - reworking stale features to reconcile with current master when a mechanical merge is not enough - fixes CI, addresses feedback, and pushes without ever asking the user. For interactive use, prefer continue-pr.
    argument-hint: <pr-number>
    disable-model-invocation: true
    allowed-tools: Agent, Task, Bash, Read, Write, Edit, Glob, Grep, WebFetch, WebSearch
    ---
    
    # Continue Work on a Pull Request (Unattended)
    
    Pick up an existing pull request, resolve conflicts, fix CI failures, address reviewer feedback, and push updates.
    
    This is the **unattended** variant used by automation (`utils/continue-all-prs.sh`). It must never wait for user input: resolve conflicts and address feedback with your best judgment and push, and when a branch is too stale for a mechanical merge, rework the feature to reconcile it with the latest master (step 3a). The only hard stop is a genuinely missing PR number. For interactive use where asking is acceptable, use `continue-pr` instead.
    
    ## Arguments
    
    - `$0` (required): PR number in the current repository (e.g., `12345`)
    
    ## Process
    
    ### 1. Parse arguments and fetch PR metadata
    
    Extract the PR number from `$0`. This skill runs unattended and must never stop to ask the user anything: if the PR number is not provided, stop with a clear error message instead of prompting.
    
    Validate that the PR number contains only digits. Reject any non-numeric input immediately — do not pass unvalidated input to shell commands or GraphQL queries.
    
    Determine which repository you are operating in — the public `ClickHouse/ClickHouse` or the private `ClickHouse/clickhouse-private`:
    
    ```bash
    gh repo view --json nameWithOwner --jq .nameWithOwner   # or: git remote get-url origin
    ```
    
    Remember it as `$REPO` and use it everywhere below instead of the literal `ClickHouse/ClickHouse` in `gh` commands, API URLs, and GraphQL `repository(owner:, name:)` arguments. The repository also decides whom to ask about unrelated CI failures (step 4): `@groeneai` in `ClickHouse/ClickHouse`, `@oranjeai` in `ClickHouse/clickhouse-private`.
    
    Fetch PR metadata using `gh` if available, otherwise use `WebFetch` on the GitHub API:
    
    ```bash
    GH_USER=$(gh api user --jq .login)
    gh pr view "$PR_NUMBER" --json number,title,body,headRefName,baseRefName,state,mergeable,mergeStateStatus,author,url,headRepository,headRepositoryOwner,isCrossRepository,maintainerCanModify,statusCheckRollup,reviews,comments,reviewRequests
    ```
    
    If `gh` is not available or not authenticated, use WebFetch to get the data. Append `?per_page=100` and follow the `Link` header for pagination (the `rel="next"` URL) to fetch all pages:
    - `https://api.github.com/repos/ClickHouse/ClickHouse/pulls/$PR_NUMBER`
    - `https://api.github.com/repos/ClickHouse/ClickHouse/pulls/$PR_NUMBER/reviews?per_page=100`
    - `https://api.github.com/repos/ClickHouse/ClickHouse/pulls/$PR_NUMBER/comments?per_page=100`
    
    Report the PR title, author, branch, and current state to the user.
    
    ### 1a. Verify "already integrated" claims before closing
    
    Treat closing a PR as already integrated or obsolete as a high-confidence decision. Verify both of these independently against freshly fetched refs:
    
    1. **Historical ancestry:** Resolve and print the exact base and PR-head OIDs, then check the candidate commit in this direction only:
       ```bash
       HEAD_REMOTE=origin
       if [ "$IS_CROSS_REPOSITORY" = "true" ]; then
           HEAD_REMOTE="pr-$AUTHOR_LOGIN"
           git remote add "$HEAD_REMOTE" "$FORK_URL" 2>/dev/null || git remote set-url "$HEAD_REMOTE" "$FORK_URL"
       fi
       git fetch origin "$BASE_BRANCH"
       git fetch "$HEAD_REMOTE" "$HEAD_BRANCH"
       git rev-parse "origin/$BASE_BRANCH" "$HEAD_REMOTE/$HEAD_BRANCH"
       git merge-base --is-ancestor "$CANDIDATE_COMMIT" "origin/$BASE_BRANCH"
       ```
       Derive `$IS_CROSS_REPOSITORY`, `$AUTHOR_LOGIN`, and `$FORK_URL` from the PR metadata as in step 2. Exit status `0` means the base contains the commit; any other status means it does not. Never check against `HEAD`, the PR branch, `--all`, or a worktree and describe that result as containment by the base branch. If this check is nonzero, do not claim the commit is in the base and do not close the PR as integrated.
    2. **Current effective state:** An ancestor commit may have been reverted or backed out later. Ancestry, `git branch --contains`, `git cherry`, and patch-equivalence results are historical evidence only; none proves that the change remains effective. Inspect all later base-branch commits touching the changed paths, search for explicit and manual reverts/backouts, compare the current base tree with the PR's intended effect, and run the reproducer or regression test against the current base when feasible. If the change was fully or partially reverted, count it as **not integrated**. If the current effect cannot be established confidently, leave the PR open for human review.
    
    Before posting a closure comment, state the fetched base OID and the evidence for both ancestry and the current effective state. Do not close from a remembered ref, a stale local branch, a matching subject, or a commit merely visible somewhere in the repository.
    
    ### 2. Check out the PR branch locally
    
    Determine whether the PR branch is in the main repository or in the author's fork.
    
    **If the branch is in the main repository (`ClickHouse/ClickHouse`):**
    ```bash
    HEAD_REMOTE=origin
    git fetch "$HEAD_REMOTE" "$HEAD_BRANCH"
    git checkout --detach "$HEAD_REMOTE/$HEAD_BRANCH"
    ```
    
    **If the branch is in the author's fork:**
    
    Derive the fork clone URL from the PR metadata (`headRepository.url` or `headRepository.owner.login` + `headRepository.name`) rather than hardcoding the repository name (forks can be renamed). Use a `pr-` prefixed remote name to avoid colliding with existing remotes like `origin`:
    
    ```bash
    REMOTE_NAME="pr-$AUTHOR_LOGIN"
    FORK_URL="https://github.com/$FORK_OWNER/$FORK_REPO.git"  # from headRepository in PR metadata
    git remote add "$REMOTE_NAME" "$FORK_URL" 2>/dev/null || git remote set-url "$REMOTE_NAME" "$FORK_URL"
    HEAD_REMOTE="$REMOTE_NAME"
    git fetch "$HEAD_REMOTE" "$HEAD_BRANCH"
    git checkout --detach "$HEAD_REMOTE/$HEAD_BRANCH"
    ```
    
    Immediately after either checkout completes, discard any state left by an
    earlier PR before recording the immutable baseline. The automation uses a
    dedicated worker worktree, so it must never preserve staged, unstaged, or
    untracked files from a previous session. This is the only authoritative record
    of the PR surface that existed when the worker began:
    
    ```bash
    git fetch origin "$BASE_BRANCH"
    # The automation may have already prepared a validated, conflict-free merge of
    # the base branch into the pull-request head in this worktree (the triage phase
    # of `utils/continue-all-prs.sh` records it). Keep that merge instead of
    # throwing it away and paying for a second merge and rebuild. Accept the
    # recorded commit only when it is exactly that merge: a two-parent commit whose
    # first parent is the current remote pull-request head and whose second parent
    # is the current base-branch head. Anything else - a stale marker from an
    # earlier pull request, a commit with a different shape - is ignored.
    VALIDATED_MERGE_FILE="$(pwd)/tmp/continue-all-prs/validated-base-merge"
    CHECKOUT_TARGET="$HEAD_REMOTE/$HEAD_BRANCH"
    if [ -s "$VALIDATED_MERGE_FILE" ]; then
        VALIDATED_MERGE=$(cat "$VALIDATED_MERGE_FILE")
        if git cat-file -e "${VALIDATED_MERGE}^{commit}" 2>/dev/null \
            && [ "$(git rev-parse "${VALIDATED_MERGE}^@")" = "$(git rev-parse "$HEAD_REMOTE/$HEAD_BRANCH" "origin/$BASE_BRANCH")" ]; then
            CHECKOUT_TARGET="$VALIDATED_MERGE"
        fi
    fi
    git reset --hard "$CHECKOUT_TARGET"
    git clean -ffdx -e build/ -e tmp/continue-all-prs/
    test -z "$(git status --porcelain)"
    mkdir -p tmp
    PR_BASELINE_DIR="$(pwd)/tmp/continue-pr-${PR_NUMBER}-baseline"
    rm -rf "$PR_BASELINE_DIR"
    mkdir -p "$PR_BASELINE_DIR"
    INITIAL_PR_HEAD=$(g
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/clickhouse-clickhouse-claude-skills-continue-pr-auto.md

// REPO STATS

50.9k stars
6073 open issues
Last commit: 3d ago