📝 Document Workflow Run Subcommand#86
Open
gilday wants to merge 1 commit into
Open
Conversation
The pixee CLI 0.13.0 release adds `pixee workflow run <id>` for triggering a scheduled workflow on demand. The audit-skills workflow caught the corresponding skill drift — `pixee-workflow` documented list, create, update, and delete, but not run — so an agent asked to kick off a schedule after re-enabling it had no skill grounding. This extends `skills/pixee-workflow/SKILL.md` with a `## pixee workflow run` section placed between `update` and `delete` in the natural workflow lifecycle. The section calls out that `run` targets `schedule` workflows specifically — `new-scan` and `pull-request-scan` workflows fire on their own events and have nothing for the agent to trigger — and pairs naturally with `update schedule --enabled` for the "re-enable, then trigger once now" flow. A two-line example joins the existing block showing exactly that pairing, and a best-practices bullet captures the schedule-only constraint and the common patterns. The picker description is rewritten to verb-first "List, create, update, run, and delete Pixee workflows on a repository with partial-update semantics across event kinds." (119 chars, picker-safe). The README bullet is refreshed to match. /close ISS-7252
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The pixee CLI 0.13.0 release added
pixee workflow run <id>for triggering a scheduled workflow on demand. The audit-skills workflow caught the corresponding skill drift:pixee-workflowdocumented list, create, update, and delete but not run, so an agent asked to kick off a schedule after re-enabling it had no skill grounding.This PR extends
skills/pixee-workflow/SKILL.mdwith a new## pixee workflow runsection placed betweenupdateanddeletein the natural workflow lifecycle. The section calls out thatruntargetsscheduleworkflows specifically —new-scanandpull-request-scanworkflows fire on their own events and have nothing for the agent to trigger manually — and that the verb pairs naturally withupdate schedule --enabledfor the "re-enable, then trigger once now" pattern. A two-line example joins the existing examples block showing exactly that pairing, and a best-practices bullet captures the schedule-only constraint along with the common patterns.The picker description is rewritten verb-first to "List, create, update, run, and delete Pixee workflows on a repository with partial-update semantics across event kinds." (119 characters, no picker-breaking punctuation). The README bullet is refreshed to match.
/close ISS-7252