github-via-theorymcp

Perform governed GitHub operations using agent-scoped tools that enforce repository policies and attribute writes automatically to a designated bot. Cover branches, commits, pull requests, reviews, and checks while preserving server-side merge gates and repository access controls.

Fall back to gh CLI for repository management only when TheoryMCP tools lack a needed action. Permitted fallback scenarios include reading PR bodies, handling Projects v2, deleting branches, dispatching workflows, managing releases, secrets, gists, and generic REST access.

Policy-aware fallbacks via gh are required for GitHub actions like reading PR bodies, managing Projects v2, deleting branches, dispatching workflows, handling releases, and accessing secrets or gists. Use these only when agent-scoped TheoryMCP tools do not expose the needed operation.

Keep GitHub commits and reviews attributable by using governed agent-scoped tools that automatically attribute writes to a designated bot account. This preserves repository access controls and ensures all branch, commit, pull request, and closeout workflows remain policy-compliant.

Yes, this approach supports GitHub closeout workflows and check runs through governed agent-scoped tools. It covers branches, commits, pull requests, reviews, issues, comments, and checks while enforcing policy and respecting server-side gates for merges and closeout flows.

Limitations of governed tools for GitHub repository management include lacking native support for reading PR bodies, Projects v2, branch deletion, releases, workflow dispatch, secrets, and gists. You must switch to gh CLI for these specific unsupported gaps while maintaining policy enforcement.