Quality Gates
Define automated checks that every merge request must pass before Orchestrator proceeds. Set your standards once and enforce them consistently across every task.
Customization
Orchestrator works your way
Every team is different. Orchestrator ships with sensible defaults and gets out of your way — but when you need control, every part of the pipeline is yours to configure.
What you can configure
Four areas. Total control.
Customize quality gates, AI behavior, and how code metadata is generated — independently, per project, or per task.
AI Instructions
Replace or augment every AI prompt that Orchestrator uses — from task refinement to code review and implementation guidance. Tune the AI to speak your team's language.
MR Titles & Descriptions
Let the AI draft your merge request title and description, or write them yourself. Either way, Orchestrator respects your choice and never overwrites your work.
Commit Messages
AI-generated commit messages follow your project's conventions out of the box. Prefer writing your own? Orchestrator steps aside and lets you author every message manually.
Quality Gates
Your standards, enforced automatically
Quality Gates let you define the criteria every merge request must satisfy before Orchestrator takes the next step. Configure them once and they apply consistently across every task — no manual checklist, no forgotten steps.
- Test coverage thresholds — require a minimum percentage before a task is considered done
- Linting and build checks — block progress if CI steps fail
- Custom rules — define your own conditions using flexible configuration
- Per-project overrides — set different gates for different repositories
quality-gates.yml
quality_gates:
coverage:
minimum: 80
fail_on_decrease: true
checks:
- lint
- build
- unit_tests
custom_rules:
- name: no_console_logs
pattern: "console\.log"
files: "src/**/*.ts"
severity: error
- name: migration_reviewed
condition: changed_files_match
pattern: "db/migrations/**"
require_label: "db-reviewed"AI Instructions
Teach the AI your standards
All AI-driven behavior is fully customizable. Override the default instructions for any stage of the workflow — or leave them as-is and start using Orchestrator in minutes.
Task Refinement
Shape how Orchestrator interprets and enriches task descriptions. Focus it on security, performance, domain terminology, or whatever matters most to your team.
Code Review
Tell the AI what to look for: enforce your style guide, flag specific anti-patterns, require test coverage thresholds, or highlight architectural concerns before they reach production.
Implementation Guidance
Guide the AI toward your preferred patterns, libraries, and conventions when it suggests implementation approaches — so every hint aligns with the way your team actually builds.
Instructions that scale with your team
Set instructions at the organization level as a shared baseline, then override them per project or even per task. The most specific instruction always wins — no merge conflicts, no confusion.
- Organization-wide defaults
- Per-project overrides
- Per-task one-offs
custom-instructions.md
# Code Review Instructions Always flag: - Missing error handling in async functions - Direct DOM manipulation outside React lifecycle - Any new dependency not listed in approved-deps.txt Style: - Prefer early returns over nested conditionals - Functional components only — no class components - Avoid abbreviations in variable names
Code metadata
AI-assisted or fully manual — your choice
Orchestrator can generate merge request descriptions and commit messages for you, or stay out of the way entirely. You decide how much the AI contributes.
MR Titles & Descriptions
Orchestrator reads your diff, your task description, and your commit history to draft a clear, accurate merge request title and description — ready to open in one click.
AI-generated mode
Orchestrator generates both the title and description from context. Review and edit them before opening the MR — the final content is always yours to approve.
Manual mode
Disable AI generation entirely and author every MR title and description by hand. Orchestrator opens the editor and waits for your input.
Commit Messages
The AI reads your staged changes and task context to write a commit message that follows your project's conventions — Conventional Commits, a custom prefix format, or whatever your team uses.
AI-generated mode
Orchestrator drafts a commit message per changeset. You can accept it as-is, edit it inline, or regenerate with adjusted instructions.
Manual mode
Prefer full authorship? Disable AI generation and write every commit message yourself. Orchestrator handles everything else in the pipeline without touching your words.
All metadata preferences are saved per project and can be changed at any time without affecting existing work.
You're always in control
Orchestrator ships with defaults that work for most teams on day one. When you need more, every setting is there — no feature flags, no support tickets, just configuration.