Slash Commands
Slash commands are comments posted on GitHub issues to control the Colony pipeline. The Mayor watches every issue comment and dispatches the appropriate action when it recognizes a command.
Default prefix: colony — commands take the form /colony:<command>. The prefix is configurable via commands.root in colony.config.yaml.
Who can run commands: by default, Colony honors commands only from commenters with write access to the repository. Set commands.authorization: any to accept any non-bot commenter. Comments from bots are always ignored.
Command reference
Section titled “Command reference”| Command | Syntax | Effect | Valid states |
|---|---|---|---|
| retry | /colony:retry [small|medium|large] | Re-queue the issue for its current pipeline stage. The optional size argument (small, medium, or large) overrides the complexity tier stored in the pipeline — useful when the analyzer under-estimated scope. | Any non-terminal state |
| skip-planning | /colony:skip-planning | Skip the planning step and proceed directly to implementation. Also clears failure-blocked and dependency-blocked states by re-enqueueing the current state’s executor. | Any non-terminal state |
| decompose | /colony:decompose | Route the issue to the planner agent for epic decomposition into subtasks. | new, analyzing, needs-clarification, ready-for-dev, changes-requested, dependency-blocked, parent-branch-pending, failure-blocked, paused (colony-default; custom workflows may differ) |
| cancel | /colony:cancel | Cancel the issue and close it, abandoning any in-progress work. Closes the issue’s open PR, unless it is an epic’s PR that is mergeable with green CI, which stays open for a human to decide. | Any non-terminal state |
| pause | /colony:pause | Pause pipeline processing for this issue. Also stops any run in progress. The issue remains open and preserves all state; no Worker will pick it up until it is resumed. | Any state; the command doesn’t check the state |
| resume | /colony:resume | Resume a paused issue, returning it to the state it was in before the pause. | paused |
| reimplement | /colony:reimplement | Discard the current implementation and PR, and start fresh from analysis. On a Dependabot tracking issue this behaves like /colony:adopt. | in-review, merge-pending, human-review-ready, changes-requested, failure-blocked (colony-default; custom workflows may differ) |
| state | /colony:state <target-state> | Force a manual state transition to <target-state>. The transition is validated against the workflow graph — invalid targets are rejected with an explanation. | Any state |
| priority | /colony:priority <high|normal|low> | Set the manual scheduling priority for this issue. High-priority issues are picked up before normal, normal before low, within the same Worker pool. | Any state |
| review | /colony:review | Re-trigger deterministic checks and LLM review. Also requests a Colony review on an external (human-authored) PR when external PR review is turned on. | human-review-ready, merge-pending, ready-for-dev |
| feedback | /colony:feedback | Send operator feedback to the implementation. On a PR awaiting review or merge, converts the PR to draft and requests changes; otherwise the feedback is stored for the agent’s current or next run. The body of your comment is forwarded as guidance. | Any state except done. Also refused on Dependabot tracking issues, and where it would be stored for a later run if the mailbox is turned off |
| reanalyze | /colony:reanalyze | Re-run issue analysis from scratch. Re-queues the analyzer on the current issue, discarding the previous analysis result. | ready-for-dev, needs-clarification (colony-default; custom workflows may differ) |
| reopen | /colony:reopen | Reopen a completed (done) issue and send it back to intake (new). Requires a workflow that declares the reopen action — the default colony-default workflow does; a custom workflow may not, in which case Colony posts guidance to open a fresh issue with /colony:enqueue. | done |
| track | /colony:track | Currently performs no action. Colony recognizes the command and acknowledges it with a 👍, but nothing is assigned. Track assignment is managed from the Cloud dashboard — see Self-improvement tracks. | Any state |
| enqueue | /colony:enqueue [high|normal|low] | Add an untracked issue (one that doesn’t yet have a colony:* label) to the Colony pipeline. The optional priority argument sets the initial scheduling priority. | unlabeled (no existing pipeline state) |
| constrain | /colony:constrain <text> | Record a standing constraint on this item that every station reads on every run. | Any state |
| unconstrain | /colony:unconstrain <n|all> | Remove a standing constraint by number, or all. The bare form re-posts the numbered list. | Any state |
| release | /colony:release #<child> | On a parent, release a canceled subtask so the parent can finalize without it. | Epic parents |
| adopt | /colony:adopt <instructions> | Dependabot tracking issues only. Create a linked issue whose branch starts from the Dependabot PR head, so your change and the bump merge together; the tracking issue waits on it. | Dependabot tracking issues |
| followup | /colony:followup [instructions] | On a Dependabot tracking issue, create a linked follow-up issue that starts after the bump merges; instructions are required. On an epic, file or link the follow-up issue that lists the open polish findings; no text is needed. | Dependabot tracking issues, epics |
| approve | /colony:approve [followup|no-followup] [note] | Accept an epic’s remaining blocking findings from its epic review. Records your acceptance, the accepted findings and your note on the issue. followup files a follow-up issue for them; no-followup only logs them; with neither, the configured default applies. It does not merge, change state or approve the PR — approve the PR on GitHub to merge. In Cloud, Accept on an epic accepts the findings and merges, with no PR approval needed. | human-review-ready (epics only) |
| help | /colony:help | Post a comment listing all available operator slash commands with their syntax and descriptions. | Any state |
retry size override
Section titled “retry size override”/colony:retry [small|medium|large] accepts an optional complexity size. When provided, it overrides the tier stored in the pipeline store for this issue — Colony will allocate model capacity and time budget as if the issue had been analyzed at that tier. Omit the argument to retry at the existing complexity tier.
review on external PRs
Section titled “review on external PRs”Posted as a comment on a pull request opened by a human (not Colony), /colony:review asks Colony to run its standard reviewer agent against that PR: the same deterministic checks and LLM review it applies to its own PRs. This needs review.external_prs.mode set to something other than off, which is the default, and the PR must pass the configured author, label, draft and bot filters. Otherwise Colony ignores the command without replying.
feedback vs reimplement
Section titled “feedback vs reimplement”/colony:feedback— use when the implementation direction is correct but the current attempt needs specific changes. Colony forwards your comment text to the Worker. On a PR awaiting review or merge the PR is marked draft and changes are requested; in other states the feedback is stored for the agent’s current or next run. It is refused ondone./colony:reimplement— use when the approach is fundamentally wrong and you want Colony to start over. The current PR is closed and Colony begins fresh from analysis.
Valid states and custom workflows
Section titled “Valid states and custom workflows”The valid states for reimplement and reanalyze are the operator_actions declared by the bundled colony-default workflow. A custom workflow can declare different from lists, and Colony gates the commands against those.
Standing constraints
Section titled “Standing constraints”/colony:constrain <text> records a standing constraint on the item; every station reads it on every run. /colony:unconstrain <n> removes one constraint by its number and /colony:unconstrain all removes every constraint. Posting /colony:unconstrain with no argument re-posts the numbered list.
release on epic parents
Section titled “release on epic parents”When a subtask of an epic is canceled, the parent waits on it. /colony:release #<child>, posted on the parent, releases that canceled subtask so the parent can finalize without it.
adopt and followup on Dependabot issues
Section titled “adopt and followup on Dependabot issues”/colony:adopt only works on Dependabot tracking issues. It creates a linked issue whose branch starts from the Dependabot PR head, so your change and the bump merge together, and the tracking issue waits on it. On a tracking issue, /colony:followup <instructions> creates a linked issue that starts after the bump merges. On an epic, /colony:followup files or links the follow-up issue that lists the epic’s open polish findings.
reopen and custom workflows
Section titled “reopen and custom workflows”/colony:reopen is fully supported when the active workflow declares the reopen operator action. The bundled colony-default workflow declares reopen: from: [done] to: new, so it works out of the box for standard deployments.
If you are using a custom workflow that does not declare the reopen action, Colony will post a comment explaining that reopen is unavailable for your workflow. In that case, open a new GitHub issue describing the same work and apply the colony:enqueue label (or post /colony:enqueue on the new issue) to seed it into the pipeline.