Instructions

Instructions tell Pullfrog how your team wants work done. They are fields in the repository console under Automations: one for every run, and one on each card for the runs that card covers.

FieldApplies toEffect
General → Standing instructionsEvery runAdded to the run
Mentions → Custom instructionsRuns a mention startsAdded to the request
Review PRs → Custom instructionsReviews and re-reviewsAdded to the built-in workflow
Plan → Custom instructionsPlansAdded to the built-in workflow
Build → Custom instructionsCode changesAdded to the built-in workflow
Address reviews → Custom instructionsReview feedback on a PRAdded to the built-in workflow
Fix CI failures → Custom instructionsCI fixesAdded to the built-in workflow
Enrich issues → Enrichment promptNew issues in Enrich modeReplaces the default prompt
Enrich issues → Custom instructionsNew issues in Plan or Build modeAdded to the mode's prompt
Label issues → Custom instructionsIssue labelsShapes the choice of labels

Instructions on a card apply to automatic runs and to direct requests alike, and win where they conflict with the built-in workflow. The Plan and Build cards start no runs of their own: the Enrich issues card chooses what a new issue starts.

Review instructions

By default, a review looks for defects, meaning anything that changes what the code does, and puts each one inline at its real severity. It does not go looking for missing tests, stale comments, naming, dead code or rollout plans, and it never flags formatting.

Ask for that feedback in the Review PRs card's Custom instructions:

Flag new code that has no test.
Flag new code that duplicates an existing helper.
Check the rollout order of schema changes.

The field applies to automatic reviews, re-reviews, and reviews you request with @pullfrog. It overrides the built-in review checklist where they conflict. Guidance in AGENTS.md does not.

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. Keep them short and actionable.

Run `pnpm test` and `pnpm lint` before pushing.
Match the patterns in the file you're editing.
Keep PRs small and move unrelated cleanup to a separate PR.

Plan instructions

Plan instructions guide how Pullfrog writes implementation plans. They apply when enrichment runs in Plan mode, when someone clicks Make a plan, and when an @pullfrog mention asks for a plan.

The plans that Enrich mode posts follow the enrichment prompt instead.

Modes

A mode is the workflow a run follows. The agent reads the request, picks the mode that matches, and gets that mode's instructions, so nobody names a mode: "Please review this PR" selects Review, and "Add dark mode support" selects Build.

ModePicked forWhat the run does
BuildA change to implement, or a plan to executeCreates a branch, makes the change, runs tests, pushes, and opens a PR
Address ReviewsReview feedback on an existing PRReads each review thread, replies, and pushes the changes asked for
ReviewA request to review a PRReads the diff and submits a review with inline comments
Incremental ReviewNew commits on a reviewed PRReviews only the changes since the last review
FixA failing checkReads the failure logs, reproduces the failure with the CI commands, fixes it, and pushes
PlanA request for a planPosts a plan with milestones and dependencies
Resolve ConflictsMerge conflicts on a PR branchMerges the base branch, resolves the conflicts, verifies, and pushes
TaskAnything else: a question, a comment, a label, an ad-hoc commandDoes the task, and opens a PR if it changed code
© 2026 Pullfrog, Inc.

On this page