You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs(verify): open the PR as a draft until the evidence is in - #1230
CodeRabbit reviews a pull request when it opens or turns ready, and its device evidence check judges the description it reads then. The skill had the agent open the PR ready and run attach right after, so the review could start before the evidence was written. On [BLACKSMITH TEST] fix(auth): shorten the phone field switcher label to "Use email or username" clerk-ios#805 the table landed 16 seconds after the PR opened, CodeRabbit had already read the earlier description, and the check failed until someone asked for a fresh review.
The skill now says to open the PR with gh pr create --draft, run attach and down, and run gh pr ready <n> once the description holds the evidence. For a remote session, where the evidence arrives about a minute after down, it says to check that gh pr view <n> --json body shows the verify-evidence block first. references/remote.md says the same.
team-review-request and code-owner-approval already run on ready_for_review, and local attach and the verify-attach workflow both publish to drafts, so nothing else changes.
In a Claude Code cloud session GitHub's GraphQL API is blocked, so gh pr create, gh pr view and gh pr ready fail there. The skill names the REST forms that work, including POST repos/<repo>/pulls/<n>/ccr/ready_for_review, which a cloud session on clerk/clerk-ios confirmed by flipping test PR Update dependency com.materialkolor:material-kolor to v5 #805 to draft and back. The wait for the evidence polls the description over REST for the table row and gives up after ten minutes.
Testing
Docs only. The next PR an agent opens with this skill shows whether CodeRabbit's first review passes the device evidence check.
Risk
Low: docs only. A PR stays a draft if an agent stops before gh pr ready, which is visible and easy to fix by hand.
CodeRabbit reviews a PR when it opens or turns ready and judges the
description it reads then. A PR opened ready was reviewed before attach
wrote the evidence, so its device evidence check failed (clerk-ios#805).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
No actionable comments were generated in the recent review.
Before this change, the verification workflow attached device evidence but did not require the pull request to remain a draft until the evidence appeared. It now opens the pull request as a draft and marks it ready only after the evidence table is present in the description. For remote sessions, the workflow checks for the table for up to ten minutes after down; Claude Code cloud sessions use documented REST alternatives when GraphQL-backed gh pr commands fail. Reviewers should start with the workflow and evidence check in SKILL.md, then read references/remote.md for remote-session publishing details.
Walkthrough
The verification instructions create pull requests as drafts, check for the evidence table, and mark them ready after it appears. They add polling after remote teardown and document GitHub API alternatives for Claude Code cloud sessions.
Changes
Verification evidence workflow
Layer / File(s)
Summary
Draft pull request until evidence is present .claude/skills/verify-clerk-android/SKILL.md, .claude/skills/verify-clerk-android/references/remote.md
The workflow creates a draft pull request before attaching evidence, waits for the evidence table to appear, and then marks the pull request ready. It documents GitHub API alternatives for pull-request commands in Claude Code cloud sessions.
clerk/clerk-android#1198: Adds a workflow triggered when a pull request becomes ready for review.
Suggested reviewers: wobsoriano
Merge Risk: Moderate · up to e69da
The verification workflow can mark a pull request ready before device evidence is available, so this existing review risk should be resolved before merge.
Pre-merge checks: 6
Check name
Status
Explanation
Title check
The title clearly identifies the documentation change and its purpose: keeping the pull request in draft status until evidence is available.
Description check
The description includes all required sections and provides clear context, testing status, risk, and rollback information. The change is documented as docs-only, so omitting What to focus on is accept…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Testing, Risk, And Revert
The PR description includes all three required sections. Testing states that the change is docs-only and identifies the next PR as the validation point. Risk states that the risk is a PR remaining dra…
Device Evidence
The pull request changes only .claude/skills/verify-clerk-android/SKILL.md and references/remote.md. It does not change any file under source/api/, source/ui/, or e2e/, so device evidence is…
Full details: Description check
Explanation
The description includes all required sections and provides clear context, testing status, risk, and rollback information. The change is documented as docs-only, so omitting What to focus on is acceptable.
Full details: Testing, Risk, And Revert
Explanation
The PR description includes all three required sections. Testing states that the change is docs-only and identifies the next PR as the validation point. Risk states that the risk is a PR remaining draft if the agent stops early. How to revert states that a plain revert is sufficient.
Full details: Device Evidence
Explanation
The pull request changes only .claude/skills/verify-clerk-android/SKILL.md and references/remote.md. It does not change any file under source/api/, source/ui/, or e2e/, so device evidence is not required by this check.
CodeRabbit Verify
Run CodeRabbit Verify to test the changes in this pull request.
Recent review info
Automatic approval policy
Commit: e69daccc598d.
Setting
Effective value
Source
Automatic approvals
Enabled
Global configuration
Merge risk
Moderate
Global configuration
Security risk
Not set
Global configuration
Not set means no limit was configured after inheritance. Use @coderabbitai configuration to inspect the resolved settings and their sources.
Reviewing files that changed from the base of the PR and between c16c82d and e69dacc.
Files selected for processing: 1
.claude/skills/verify-clerk-android/SKILL.md
Limit details: You’ve used all 5 included reviews currently available. Your 57 included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour.
… the cloud REST forms
In a Claude Code cloud session GitHub's GraphQL API is blocked, so gh pr
create, view and ready fail. Name the REST and CCR routes that work there,
and replace the eyeballed wait with a polling check that fails after ten
minutes instead of a fixed one-minute guess.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
attachright after, so the review could start before the evidence was written. On [BLACKSMITH TEST] fix(auth): shorten the phone field switcher label to "Use email or username" clerk-ios#805 the table landed 16 seconds after the PR opened, CodeRabbit had already read the earlier description, and the check failed until someone asked for a fresh review.gh pr create --draft, runattachanddown, and rungh pr ready <n>once the description holds the evidence. For a remote session, where the evidence arrives about a minute afterdown, it says to check thatgh pr view <n> --json bodyshows theverify-evidenceblock first.references/remote.mdsays the same.team-review-requestandcode-owner-approvalalready run onready_for_review, and localattachand theverify-attachworkflow both publish to drafts, so nothing else changes.gh pr create,gh pr viewandgh pr readyfail there. The skill names the REST forms that work, includingPOST repos/<repo>/pulls/<n>/ccr/ready_for_review, which a cloud session on clerk/clerk-ios confirmed by flipping test PR Update dependency com.materialkolor:material-kolor to v5 #805 to draft and back. The wait for the evidence polls the description over REST for the table row and gives up after ten minutes.Testing
Risk
gh pr ready, which is visible and easy to fix by hand.How to revert
Screenshots / video
🤖 Generated with Claude Code