CLI reference¶

All commands are available as developer <command> (with venv activated) or uv run developer <command>.

resolve¶

developer resolve REPO ISSUE_NUMBER [--dry-run]

Resolve a GitHub issue. Triages, implements, evaluates, and opens a PR.

Arguments:

REPO -- repo name from developer.yaml, or a GitHub issue URL
ISSUE_NUMBER -- issue number (omit if using a URL)

URL formats:

developer resolve assistant 25
developer resolve https://github.com/gregology/assistant/issues/25
developer resolve github.com/gregology/assistant/issues/25
developer resolve gregology/assistant/issues/25

When using a URL, the repo name is matched against your developer.yaml config by the GitHub owner/repo pair.

Flags:

Flag	Description
`--dry-run`	Run the pipeline but don't create the PR
`--provider NAME`	Force all stages to use this provider (overrides both `provider` and `providers` in `developer.yaml`)

review¶

developer review REPO PR_NUMBER [--dry-run]

Review a pull request. Analyzes the diff, generates findings, posts a comment.

Arguments:

REPO -- repo name from developer.yaml, or a GitHub PR URL
PR_NUMBER -- PR number (omit if using a URL)

URL formats:

developer review assistant 42
developer review https://github.com/gregology/assistant/pull/42
developer review github.com/gregology/assistant/pull/42
developer review gregology/assistant/pull/42

Flags:

Flag	Description
`--dry-run`	Print the review comment to stdout instead of posting
`--provider NAME`	Force all stages to use this provider (overrides both `provider` and `providers` in `developer.yaml`)

address¶

developer address REPO PR_NUMBER [--dry-run]

Address review feedback on a PR. Fetches comments, identifies actionable items, implements changes, pushes.

Arguments:

REPO -- repo name from developer.yaml, or a GitHub PR URL
PR_NUMBER -- PR number (omit if using a URL)

URL formats: same as review.

Flags:

Flag	Description
`--dry-run`	Run the pipeline but don't push changes or post comments
`--provider NAME`	Force all stages to use this provider (overrides both `provider` and `providers` in `developer.yaml`)

audit¶

developer audit TYPE REPO [--dry-run] [--limit N]

Audit a repo. Creates GitHub issues for findings.

Types:

docs -- check documentation for drift from the codebase
refactor -- identify refactoring opportunities using quality tool output
tests -- evaluate test coverage against risk

Arguments:

TYPE -- one of docs, refactor, tests
REPO -- repo name from developer.yaml

Flags:

Flag	Description
`--dry-run`	Print findings to stdout instead of creating issues
`--limit N`	Max number of findings (default 3)
`--provider NAME`	Force all stages to use this provider (overrides both `provider` and `providers` in `developer.yaml`)

validate¶

developer validate [REPO] [--all]

Validate a repo's configuration by cloning from scratch into a temp directory, running setup commands, and running quality tools. Reports pass/fail for each step.

Arguments:

REPO -- repo name from developer.yaml (required unless using --all)

Flags:

Flag	Description
`--all`	Validate every repo in `developer.yaml`

add¶

developer add OWNER/REPO [--dry-run] [--provider NAME]

Investigate a repo and add it to developer.yaml. Clones the repo, runs an agent to discover setup commands, testing philosophy, and quality tools, then writes the discovered config.

Arguments:

OWNER/REPO -- GitHub owner and repo name (e.g. gregology/assistant)

Flags:

Flag	Description
`--dry-run`	Print discovered config without saving to `developer.yaml`
`--provider NAME`	Agent provider to use (default `claude`)

serve¶

developer serve [--host HOST] [--port PORT]

Start the Developer API server. Exposes the same pipelines as the CLI over HTTP so a UI or other tooling can drive them.

Flags:

Flag	Description
`--host HOST`	Bind address (default `127.0.0.1`)
`--port PORT`	Bind port (default `6768`)

Pipeline endpoints (/resolve, /review, /address, /audit/{type}, /validate, POST /repos) accept JSON bodies and return a task_id immediately. Poll GET /tasks/{task_id} for status, logs, and results. See API reference for the full endpoint list.

Exit codes¶

All commands return 0 on success and non-zero on failure. Config errors, missing repos, and GitHub API failures all produce non-zero exits with descriptive error messages.