release
25Command
Create a release with changelog generation from merged PRs. Calculates semantic version, requires human confirmation. Tier 3 — never autonomous.
55 tagged agentic-design-patterns, measured the same way as everything else here.
Browse within: agentic-development 55agentic-workflow 55ai-developer-tools 55ai-first 55
Command
Create a release with changelog generation from merged PRs. Calculates semantic version, requires human confirmation. Tier 3 — never autonomous.
Command
Resolve merge conflicts on the current branch or for a pull request. Detects conflict types, analyzes both sides, applies per-file resolution strategies, and verifies the result compiles and passes tests.
Command
Read interrupted FlowRun state and propose the next safe action. Use /flow:resume (no args) for the most-recent active run, or /flow:resume for a specific run. Informational only — never auto-executes the next phase. The user decides whether to continue.
Command
Review a pull request with multi-faceted analysis. Supports both single-session parallel review and agent team adversarial review.
Command
Execute a FlowTrigger target ONCE. Subcommands: trigger . Does NOT schedule future execution.
Command
Start work on a GitHub issue. Assigns issue, creates branch, decomposes tasks from acceptance criteria, and guides implementation with autonomous execution.
Command
Manage FlowTrigger artifacts at .flow/triggers/. Subcommands: list, inspect , enable , disable , run , delete . Triggers describe wake-up intent; they do NOT guarantee background execution.
Command
Create a FlowTrigger from a template AND generate a /loop prompt file the user invokes manually. Subcommands: pr , ci, issue , branch. Flow CANNOT invoke /loop from plugin code; this command prepares the prompt and tells the user how to start the loop themselves.
Command
Inspect and validate FlowWorkflow YAMLs at plugins/flow/workflows/. Subcommands: list, inspect , validate , graph .
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: