omnicheck-github

OmniCheck

Verify whether requested PR changes have been applied — diff analysis + targeted nudge comments.

Check all review comment threads on a GitHub PR against the current diff. Resolved threads are marked APPLIED. Unresolved threads are analyzed by a subagent to determine if the fix was applied silently or not at all. Unaddressed threads receive nudge replies and a summary comment.

Core principle: Thread status check + diff analysis + user approval gate = accurate, non-spammy follow-up.

Announce at start: "I'm using OmniCheck to verify findings on PR #{id}."

Prerequisites

• gh CLI authenticated (gh auth status to verify)
• Git repository with remote pointing to GitHub
• Current working directory is in the git repo
• PR must have review comment threads

Input Parsing

Accept any of: PR number (136), prefixed (#136), or full GitHub URL. Extract PR ID. If URL provided, extract owner/repo and PR number.

The Process

Phase 1: GATHER   — fetch all threads + PR diff/data
Phase 2: ANALYZE  — single subagent checks each open thread against the diff
Phase 3: REPORT   — present status table, user approves nudge list
Phase 4: NUDGE    — reply on each NOT_APPLIED thread + post summary PR comment
Phase 5: DONE     — no cleanup needed (no worktrees)

---

Thread Verdicts

Verdict	Meaning	Action
APPLIED	Thread is resolved/dismissed — trusted as-is	None
SILENTLY_APPLIED	Thread open, but diff shows the concern was addressed	Note in summary only
NOT_APPLIED	Thread open, diff shows no relevant change	Nudge: thread reply + summary row
NEEDS_HUMAN	Ambiguous — cannot determine from diff alone	Flag in report; no automatic nudge

---

Phase 1: Gather

Step 1: Fetch all review comment threads.

mcp__omniforge__fetch_pr_discussions(pr_id="{id}", repo_root="{cwd}")

Returns structured threads with: comment_id, type, file_path, line_number, body, author, replies. The tool already excludes discussions whose notes are all system-generated — every thread returned contains at least one human note.