continue

Resume interrupted code review workflows for the current Git branch.

3|1|Updated Feb 28, 2026

Search Tags:#automation #github #coderabbit #code-review #ci #pull-request #greptile

Ready to run

npx skills add https://github.com/auerbachb/claude-code-config --skill continue-auerbachb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: continue
Source: https://github.com/auerbachb/claude-code-config/tree/main/.claude/skills/continue
Command: npx skills add https://github.com/auerbachb/claude-code-config --skill continue-auerbachb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill detects and continues an interrupted or stalled pull request review workflow, removing manual bookkeeping and guesswork about what step comes next.

Core Features & Use Cases

Detects current branch and whether a PR exists, then stops if on main or nothing to continue.
Runs local CodeRabbit CLI review loops with convergence tracking and fallbacks to self-review when the CLI is unavailable.
Pushes changes, creates or reopens PRs, polls for CodeRabbit or Greptile feedback with rate-limit handling, processes unresolved review threads, verifies merge gate and acceptance criteria, and offers to squash-merge when ready.
Real-world use case: resume a feature-branch review that was interrupted after a local review pass, finish outstanding fixes, wait for CI and bot reviews, and complete merge checks automatically.

Quick Start

Run the continue workflow to detect the next incomplete review step for the current feature branch and finish it until the PR is merge-ready.

Frequently Asked Questions about continue

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

FAQPage Schema

How do I automatically resume a stalled pull request review workflow?▼

To resume stalled pull request reviews, you can run a workflow that detects the current branch, completes outstanding code review fixes, polls for CI and bot feedback, verifies merge gates, and offers to squash-merge when ready. It removes manual tracking of review steps.

What happens if CodeRabbit CLI is unavailable during a local code review?▼

When the CodeRabbit CLI is unavailable during a local code review, the workflow uses convergence tracking and falls back to a self-review loop. This ensures the code review process continues without interruption until ready for PR creation.

Can I use Greptile feedback alongside CodeRabbit for PR reviews?▼

Yes, you can use Greptile feedback alongside CodeRabbit. The workflow polls for both CodeRabbit and Greptile feedback on pull requests, handling rate limits and processing unresolved review threads from either integration automatically.

How do I enforce merge-gate verification and acceptance criteria before merging a PR?▼

Merge-gate verification and acceptance criteria are enforced by running repository helper scripts with timeouts and fallbacks. The workflow checks these conditions automatically and offers to squash-merge the pull request only when all merge checks pass.

Do I need GitHub CLI installed to automate PR creation and thread resolution?▼

Yes, GitHub CLI is required to automate PR creation, pushes, and thread resolution. The workflow operates via Git and GitHub CLI commands to manage remote pull requests and interact with CodeRabbit or Greptile feedback.

What is the best way to handle interrupted code review loops on a feature branch?▼

The best way to handle interrupted code review loops is running a detection workflow that identifies the next incomplete review step for your feature branch. It finishes local reviews, pushes changes, reopens PRs if needed, and completes merge checks automatically.