Skip to main content
Pullfrog keeps pull requests moving: it applies review feedback and fixes failing CI without anyone re-triggering it. Both are cards in the repository console under Automations.

​
Auto-address reviews

When a person submits a review on a PR that Pullfrog opened, Pullfrog applies the feedback and pushes. The Address reviews card turns this on or off, and its Custom instructions field guides how Pullfrog handles feedback.
The Address reviews card in the repository console
Line-level comments, Fix all, and Fix 👍s are covered in Address reviews.
To request a change on any PR, including one Pullfrog did not open, comment with @pullfrog and describe the fix.

​
Auto-fix CI failures

When a check suite fails on an open PR, Pullfrog reads the failure logs, reproduces the failure with the CI commands, fixes it, and pushes to the PR branch.
Pullfrog's comment after fixing a failing test job on a pull request
The Fix CI failures card has two toggles:
The Fix CI failures card with its two toggles
Pullfrog skips a failure in these cases:
  • Bot commit. The failing commit was authored or committed by a bot, such as Dependabot or Renovate. This applies to PRs that Pullfrog did not open.
  • Failing base branch. The latest completed check suite on the PR’s base branch did not pass, so the failure is likely not the PR’s.
  • Recent attempt. Pullfrog already started a CI fix on the same PR within the last hour.
During the run, Pullfrog first confirms that the PR caused the failure. If the cause is unrelated, such as a flaky test, an infrastructure problem, or an existing bug, it makes no change and reports why. The card’s Custom instructions field applies whenever Pullfrog fixes CI, for example “Do not weaken assertions to make CI pass.”

​
Build instructions

Build instructions guide how Pullfrog writes code when it implements a task: a plan, an issue in Build mode, or an @pullfrog request for a change. Edit them in the Custom instructions field of the Build card under Automations.
The Build card and its Custom instructions field
Keep them short and actionable, for example “run pnpm test and pnpm lint before pushing,” “match the patterns in the file you’re editing,” or “keep PRs small and move unrelated cleanup to a separate PR.” Instructions that apply to every run, not only builds, belong under Agent → Standing instructions.