Skip to content

Triggers

Triggers define when a skill runs. Each skill can have one or more triggers. Triggers can override output settings and the main agent model.

FieldPurpose
typepull_request, local, or schedule.
actionsEvent actions for pull_request triggers.
failOnOverride failure threshold.
reportOnOverride reporting threshold.
maxFindingsOverride maximum findings.
reportOnSuccessOverride report-on-success behavior.
requestChangesOverride REQUEST_CHANGES behavior.
failCheckOverride check failure behavior.
modelOverride the main agent model for this trigger. See Models and Runtimes.
maxTurnsOverride max agentic turns.
ActionMeaning
openedPR created.
synchronizeNew commits pushed.
reopenedPR reopened.
closedPR closed or merged.
warden.toml
[[skills]]
name = "security-review"
[[skills.triggers]]
type = "pull_request"
actions = ["opened", "synchronize"]

Schedule triggers run on cron workflows instead of PR events. They require paths so Warden knows which files to scan.

FieldPurpose
issueTitleTitle for the tracking issue. Default: Warden: {name}.
createFixPRCreate a PR with fixes when available. Default: false.
fixBranchPrefixBranch prefix for fix PRs. Default: warden-fix.
warden.toml
[[skills]]
name = "security-review"
paths = ["src/**/*.ts"]
[[skills.triggers]]
type = "schedule"
createFixPR = true