Galley Documentation

July 19, 2026 ยท View on GitHub

Start with the main README to install Galley and set up a repository with the Galley skill. The documents here explain how to configure, operate, and troubleshoot the resulting workflow.

The Workflow

  1. Use the Galley skill to inspect the repository and create its quality and environment profiles.
  2. Ask the skill to draft a task, then review its acceptance criteria, scope, executor settings, and loop budget.
  3. Queue the approved task. The daemon runs the executor in an isolated worktree.
  4. A separately configured supervisor reviews acceptance criteria first, then repository quality policy. Verified passes carry forward so later attempts can focus on unresolved work and regression risks.
  5. Accepted work is either left in the local worktree or committed and opened as a pull request, depending on the environment profile.

Documentation Map

GoalRead
Choose an executor or supervisor, set model and effort, or understand retriesModels and supervision
Review or hand-write a task fileTask YAML reference
Understand or tune quality.yaml and environment.yamlProfiles
Start and stop the daemon, inspect the queue, or configure notificationsOperations
Understand a failed or stalled task and resume it safelyTroubleshooting
Configure pull requests, comment requeues, and cleanupPR automation
Understand security and trust boundariesSecurity policy
Build, test, or contribute to GalleyContributing

Configuration Files

Galley keeps settings at the scope where they apply:

FileScopeContains
Task YAMLOne taskGoal, acceptance criteria, implementation scope, executor overrides, attempt budget, and worktree
quality.yamlOne repositoryRequired checks, review dimensions, evidence expectations, and pass policy
environment.yamlOne repositoryExecutor and supervisor defaults, commands, constraints, PR behavior, and worktree cleanup
daemon.yamlOne Galley daemonConcurrency, polling, timeouts, daemon-level supervisor default, provider credentials, and notifications

The Galley skill is the recommended way to create task and profile files. The reference documents describe the resulting contracts for review, manual adjustment, and troubleshooting.