Skip to main content
Modes are specialized workflows that guide how Pullfrog handles different types of tasks. When Pullfrog receives a prompt, the agent analyzes the request and selects the most appropriate mode.

​
How mode selection works

Mode selection happens automatically at the start of each agent run:
  1. Pullfrog spawns an agent that reads all configured modes (built-in + custom)
  2. The agent analyzes the prompt against each mode’s description
  3. The agent calls the select_mode tool with the best-matching mode
  4. The agent receives guidance and instructions for that mode and executes the task
You don’t need to specify which mode to use—Pullfrog figures it out from context. For example, a comment like “Please review this PR” will automatically trigger Review mode, while “Add dark mode support” will trigger Build mode.

​
Built-in modes

Pullfrog comes with seven built-in modes:

Build

Implement, build, create, or develop code changes. Make specific changes to files or features. Execute a plan.Creates a branch, makes code changes, runs tests, pushes with a clean working tree (optional repo prepush hooks may run tests/lint first), and opens a PR.

Address Reviews

Address PR review feedback. Respond to reviewer comments. Make requested changes to an existing PR.Checks out the PR branch, addresses each review comment, replies to threads, and pushes updates.

Review

Review code, PRs, or implementations. Provide feedback or suggestions. Check code quality, style, and correctness.Analyzes the PR diff and submits a review with inline comments.

Incremental Review

Re-review a PR after new commits are pushed. Focus on new changes since the last review.Generates an incremental diff from the previous HEAD, fetches prior review feedback to avoid duplication, and submits a focused review on only the new changes.

Fix

Fix CI failures. Debug failing tests or builds. Investigate and resolve check suite failures.Fetches failure logs, reads workflow files to understand how CI runs, reproduces locally with exact CI commands, fixes the issue, and pushes.

​
Auto-fix CI failures

The Fix mode can be automatically triggered when CI fails on a PR. Enable this in your repository settings under “Auto-fix CI failures” (disabled by default). Key behaviors:
  • PR-scoped fixes only — Pullfrog only fixes issues that were introduced by the PR’s changes. If a CI failure is unrelated to the PR (flaky test, infrastructure issue, pre-existing bug), it aborts without making any changes and explains why.
  • Skips bot commits — Commits from bots (dependabot, renovate, etc.) are automatically skipped. These are automated dependency updates, not code changes that need fixing.
  • Loop prevention — Pullfrog tracks autofix attempts per PR. If an autofix was already triggered within the last hour, it won’t trigger again. This prevents infinite loops while still allowing retries after human intervention.
  • Target branch check — Autofix only runs if CI is passing on the PR’s target branch (usually main). This ensures Pullfrog doesn’t try to fix pre-existing failures.

Plan

Create plans, break down tasks, outline steps. Analyze requirements and understand scope of work.Creates a structured plan with clear milestones and dependencies.

Resolve Conflicts

Resolve merge conflicts in a PR branch against the base branch.Fetches the base branch and merges. If the merge is clean, pushes (optional repo prepush hooks may run) and finishes. If there are conflicts, resolves them, verifies, commits, pushes, and reports.

Task

General-purpose tasks that don’t fit other modes: answering questions, adding comments, labeling, running ad-hoc commands, or any direct request.Reads the request, gathers context if needed, performs the task, and creates a branch/PR if code changes are involved.

​
Custom modes

Custom modes let you specialize Pullfrog’s behavior for your team’s specific workflows. They work exactly like built-in modes but are tailored to your needs. To create a custom mode:
  1. Navigate to your repository in the Pullfrog dashboard
  2. Go to the Modes section
  3. Click Add mode
  4. Fill in:
    • Name — A short name for the mode (e.g., “Refactor”)
    • Description — When to use this mode—this is what the orchestrator matches against
    • Prompt — Instructions for the agent when this mode is selected
Custom modes in the Pullfrog dashboard