Testing and Running Rules
Dry-run a rule on a real task before enabling, trigger any rule manually from the Command Palette, and bind rules to keyboard shortcuts for instant recall.
Automations are most trustworthy when you can see what they'll do before committing, and run them on demand when you want. PrimeTask gives you three paths for that:
- Test mode - dry-run a rule on a real task to preview every action.
- Command Palette - every custom rule is a searchable command, ready to run manually.
- Keyboard shortcuts - bind a rule to a key combination and run it from anywhere.
For the custom rule builder itself, see Building Custom Rules. For the built-in rules, see Built-in Automations.
Custom rules, test mode, and shortcut triggers are Pro
The Pro tier unlocks the rule builder and its test mode, plus keyboard shortcut triggers. See License Settings.
What you can do
Preview every action
a rule would run, on a task you pick, without committing.
Run any rule by name
from the Command Palette.
Bind a rule to a keyboard shortcut
so you can trigger it anywhere in PrimeTask.
See how often each rule has fired
and when it last ran.
Test a rule before enabling
The rule editor has a Test action. It dry-runs the rule against a task you pick so you can see exactly what each action would do.
How it works
Step 1
Open the rule in the editor.
Step 2
Use the Test action.
Step 3
Pick a task from your Space.
PrimeTask shows a preview of every action
"Will set status from Backlog to In Progress," "Will start timer," "Will add tag deliverable," and so on.
Review the preview. If it looks right, run the test
the actions execute on the selected task for real.
Step 6
If anything looks wrong, close the test without running.
Use a throwaway task for testing so you never put real work at risk.
Test mode runs real actions
Once you click Run Test, the listed actions execute on the selected task - they're not simulated. Preview first; run only when the preview looks right. Use a test task you're happy to throw away.
Run a rule manually - Command Palette
Every custom rule also appears in the Command Palette. Open it, start typing the rule's name, and run the rule on demand - no trigger event needed.
How to reach it
- Command Palette - ⌘+K on macOS, Ctrl+K on Windows.
- Type the rule's name.
- Press Enter to run.
This is especially useful for rules with a Manual trigger - the command palette becomes the main way to fire them. It's also handy for rules with automated triggers when you want to re-run one now rather than wait for the trigger event.
See App Header for other ways to open the Command Palette.
Bind a rule to a keyboard shortcut
Rules can have their own keyboard shortcut. Press the combination anywhere in PrimeTask and the rule runs immediately.
How to assign one
Step 1
Open the rule in the editor.
Step 2
Set a keyboard shortcut in the shortcut field.
Step 3
Save.
PrimeTask checks your shortcut for conflicts against other rules and built-in commands. If your combination is already taken, you'll see the conflict and can pick a different one.
Great for focus and daily rituals
Bind a "Start my day" rule (set status of pinned tasks to In Progress, start the timer on the top one) to ⌘+⇧+D. One keypress every morning starts the routine.
See how often a rule fires
Each rule tracks two things automatically:
- Trigger count - how many times this rule has fired since you created it.
- Last triggered - when the most recent fire happened.
Both appear on the rule in the Settings card. Use them to spot rules that aren't doing anything (maybe the trigger or conditions don't match what you thought) and rules that are doing a lot (good candidates to keep; or ones to review if they're firing more than expected).
Putting it all together
A good rollout rhythm for a new rule:
Step 1
Build the rule in the editor.
**Test** on a throwaway task
review the preview first.
Step 3
Enable the rule in the Space.
Step 4
Watch the trigger count for a week.
Step 5
Bind a shortcut if the rule works well and you'd benefit from manual fires too.
Iterate
adjust triggers, conditions, or actions based on what happens.
Things worth knowing
Test mode is the safest preview
Test mode is the one place you can see what a rule would do before you turn it on. Use it on anything that modifies data.
Manual triggers don't need an event
Rules with the Manual trigger only run when you invoke them - from the Command Palette, a keyboard shortcut, or test mode. They never fire on their own.
Shortcuts are user-specific
Keyboard shortcuts you assign are specific to this device. Another device you set up PrimeTask on keeps its own shortcut map.
Shortcuts can conflict with system keys
PrimeTask checks against other PrimeTask commands, not against macOS or Windows system shortcuts. Pick combinations that don't collide with your operating system (e.g., avoid ⌘+Space on macOS).
Running a rule manually bypasses conditions
When you run a rule by command or shortcut, PrimeTask executes the actions directly on the current context (usually the active task). Conditions that scope automatic fires don't gate manual runs.
Common questions
"Will running a test actually change the task?"
Yes - Run Test executes the actions on the task you picked, for real. Use a throwaway task. The preview step shows you exactly what will happen before you run.
"Can I run a built-in rule from the Command Palette?"
The Command Palette surfaces custom rules. Built-in rules run automatically when their trigger fires. If you want manual control over a built-in behaviour, build a custom rule that does the same thing with a Manual trigger.
"What if my shortcut conflicts?"
The editor flags conflicts and tells you what command the combination is already assigned to. Pick a different shortcut and save.
"How do I find out which rule fired on a given event?"
The trigger count and last-triggered time on each rule give you recent activity. For a fuller record, the rule editor shows the rule's history over time.
"Can I disable manual runs without disabling the rule?"
Manual runs happen through the Command Palette and keyboard shortcuts. Remove the shortcut if you don't want to run it that way; the rule still fires on its automatic trigger when enabled.
"Does running a rule manually count toward the trigger count?"
Yes - any fire, automatic or manual, increments the trigger count.
Where to go next
| If you want to… | Read this |
|---|---|
| Build a new custom rule | Building Custom Rules |
| See the seven built-in rules | Built-in Automations |
| Look up triggers, conditions, actions | Triggers and Actions Reference |
| Automate from Siri or Shortcuts | Apple Shortcuts and Deep Links |
| Use the Command Palette and App Header | App Header |
| Configure the settings card | Automations Settings |