Skip to content

v2.1.0 — GitHub Issues first-class; :merge MCP-preferred; gh optional

Choose a tag to compare

View all tags
@iansmith iansmith released this 03 Jun 14:25
· 1017 commits to master since this release
v2.1.0
b961626

What's new in v2.1.0

GitHub Issues as a first-class ticket system

Set system = "github" in .project-conf.toml. Workflow state is label-based via [status_labels]. Two shapes: 3-state (Todo → In Progress → Done) and 4-state (with an In Review gate). All lifecycle skills (:start, :document, :archive, :merge) support GitHub Issues.

.project-conf.toml replaces .project-prefix

system = "github"   # or "linear" / "jira"
key    = "owner/repo"
prefix = "MYPREFIX"
[status_labels]
in_progress = "status:in-progress"

:merge migrated to MCP-preferred

PR operations now use the GitHub MCP (list_pull_requests, pull_request_read, merge_pull_request) with gh CLI as fallback. gh auth status pre-flight is now skipped when using MCP.

gh CLI is now optional

Required only for CodeRabbit polling (gh api) and gh pr create fallback (MCP create_pull_request returns 403 on some repos due to PAT scope). Install gh for the full experience; MCP-only works for everything else.

START-HERE.md at repo root

The cold-start setup guide is now at the repo root for immediate discoverability.

Design documentation

design/github-backend-primitives.md now documents all PR-level MCP primitives, the CodeRabbit in-place-edit completion trap, the create_pull_request 403 limitation, and the 3-state/4-state workflow shape requirement.

See CHANGELOG.md for the full entry including known gaps (:pr skill migration deferred).

Assets 2
Loading