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

​
Custom flags

Custom flags 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 flag

  1. Navigate to your repository in the Pullfrog console
  2. Scroll to the Flags section
  3. Click Add flag
  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. Flag tags are case-sensitive — --refactor and --Refactor are different flags.
Creating a custom flag

​
Using flags

Once defined, use your flag 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
PR comment containing a flag
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.

​
Precedence

When flags 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 flag set for the specific trigger
  3. Repository custom instructions (lowest) — The default flag for the repo
If the same flag appears multiple times in the same location, the last occurrence wins. Higher-priority sources override lower ones.