-
-
Notifications
You must be signed in to change notification settings - Fork 4
Open
Description
Background
Currently, triggers are configured with events like pull_request, issues, issue_comment, and schedule. These all run automatically based on GitHub events or cron schedules. There's no way to define a skill that only runs when explicitly invoked via the warden CLI.
Requirements
Add a new manual event type that:
- Never runs automatically - Not triggered by GitHub events or schedules
- Only runs via CLI - Activated when running
wardencommand locally - Supports same filters - Path patterns, ignorePaths, etc. should still work
Decisions
- Event name:
manual✓ - Invocation: Hybrid approach ✓
wardenruns allevent = "manual"triggerswarden --trigger <name>runs specific trigger⚠️ TODO: Evaluate this UX more thoroughly before finalizing
Open Questions
- Should manual triggers be able to specify a target (single file, directory, etc.)?
- Does
actionsfield make sense for manual? Probably not required.
Config Example
[[triggers]]
name = "security-audit"
event = "manual"
skill = "security-review"
[triggers.filters]
paths = ["src/**/*.ts"]Implementation Notes
- Update
TriggerSchemainsrc/config/schema.tsto acceptmanualevent - Update
matchTriggerinsrc/triggers/matcher.tsto handle manual events - Update CLI to invoke manual triggers (may need new subcommand or flag)
- Consider how this interacts with existing
--skillflag for running arbitrary skills
Reactions are currently unavailable