audit-work-integrity

To audit GitHub branches and pull requests, you can run an integrity audit that maps branches to open PRs and issues, enforcing strict policy checks to detect orphan branches and missing linkages before delivery. It produces a deterministic report with a final score and remediation guidance.

An orphan branch is a branch lacking an open pull request targeting the base branch. You detect branches without an open PR by auditing repository worktrees, mapping active branches against current pull requests, and flagging any branches that lack a corresponding PR.

To verify pull request to issue linkage, audit your repository's open PRs and issues to ensure in-progress issues have active PRs. The audit maps PRs to their corresponding issues, flags missing links, and identifies duplicate PRs targeting the same issue.

Yes, you can post automated repository audit findings directly to a specified GitHub issue. The audit generates a structured report with findings by severity, a readiness score, and remediation steps, then optionally posts this output to an issue for traceability.

The repository audit applies MCP-first data gathering with fallback gh commands to map branches, PRs, and issues. This means it prioritizes MCP tools but falls back to standard gh CLI commands, requiring no separate API token setup beyond your existing gh authentication.

Yes, you can include recently closed pull requests and issues in the workflow audit. The audit optionally incorporates recently closed items alongside open PRs and branches, providing broader historical context to accurately evaluate repository drift and workflow gaps.