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.
Fields
Section titled “Fields”typepull_request,local, orschedule.actions- Event actions for
pull_requesttriggers. failOn- Override failure threshold.
reportOn- Override reporting threshold.
maxFindings- Override maximum findings.
reportOnSuccess- Override report-on-success behavior.
requestChanges- Override
REQUEST_CHANGESbehavior. failCheck- Override check failure behavior.
model- Override the main agent model for this trigger. See Models and Runtimes.
maxTurns- Override max agentic turns.
Pull Request Actions
Section titled “Pull Request Actions”| Action | Meaning |
|---|---|
opened | PR created. |
synchronize | New commits pushed. |
reopened | PR reopened. |
closed | PR closed or merged. |
[[skills]]name = "security-review"
[[skills.triggers]]type = "pull_request"actions = ["opened", "synchronize"]Schedule Triggers
Section titled “Schedule Triggers”Schedule triggers run on cron workflows instead of PR events. They require
paths so Warden knows which files to scan.
issueTitle- Title for the tracking issue. Default:
Warden: {name}. createFixPR- Create a PR with fixes when available. Default:
false. fixBranchPrefix- Branch prefix for fix PRs. Default:
warden-fix.
[[skills]]name = "security-review"paths = ["src/**/*.ts"]
[[skills.triggers]]type = "schedule"createFixPR = true