Skip to main content
Macros are text shortcuts that expand when used in prompts. Define a macro once in the dashboard, then reuse it across your repository’s custom instructions, trigger instructions, or one-off GitHub comments and issues.

​
Custom macros

Custom macros let you define reusable text snippets for your repository. For example, you could create #refactor that expands to detailed refactoring instructions, or #security that includes your team’s security review checklist.

​
Creating a macro

  1. Navigate to your repository in the Pullfrog console
  2. Scroll to the Macros section
  3. Click Add macro
  4. Enter a tag (e.g., refactor) and the replacement text
The tag must start with a letter and can contain letters, numbers, underscores, or hyphens. Macro tags are case-sensitive — #refactor and #Refactor are different macros.

​
Using macros

Once defined, use your macro by including #tag anywhere Pullfrog reads instructions:
  • Repository custom instructions — Set defaults that apply to all runs
  • Trigger-level instructions — Customize behavior for specific triggers
  • GitHub issue body — Include when creating a new issue
  • GitHub comment — Include when mentioning @pullfrog
For example, if you define #refactor to expand to “Follow the boy scout rule: leave code cleaner than you found it. Extract duplicated logic into shared utilities. Prefer composition over inheritance.”, then: 
@pullfrog clean up the auth module #refactor
becomes: 
@pullfrog clean up the auth module Follow the boy scout rule: leave code cleaner than you found it. Extract duplicated logic into shared utilities. Prefer composition over inheritance.

​
Built-in macros

Pullfrog includes built-in macros for controlling effort level and timeout:
MacroEffect
#miniUse fast models with minimal reasoning
#autoUse balanced defaults (this is the default)
#maxUse the most capable models with maximum reasoning
#timeout30mSet custom timeout (e.g., “#timeout10m”, “#timeout1h30m”, “#timeout2h”). Default: 1h
#notimeoutDisable timeout entirely
Built-in macros are kept in the prompt (visible to the agent) and also used to configure Pullfrog’s behavior. Custom macros are replaced inline with their text. All macros are case-sensitive — use lowercase for built-in macros.
You cannot create custom macros with the same names as built-in macros (#mini, #auto, #max, #timeout, #notimeout).

​
Precedence

When macros appear in multiple places, more specific locations take precedence:
  1. GitHub prompt (highest) — The comment or issue/PR body that triggered the run
  2. Trigger-level instructions — The macro set for the specific trigger
  3. Repository custom instructions (lowest) — The default macro for the repo
If your repo instructions include #mini but you comment “@pullfrog fix this bug #max”, the run will use #max. If the same macro appears multiple times in the same location, the last occurrence wins.