Check the input, then compare the complete deliverables
Explore the original materials, item-by-item outcomes and full report below. Attempt the input independently before using the reference to find omissions or disagreements.
The PR snapshots, commit ids and reference results below are synthetic. A separate read-only run on 2026-10-18 checked public PR #3 and its current-head checks and reviews. Notion writes, notifications, continuous monitoring and Routines remain untested; see the verification record.
Original synthetic material. Try the input independently, then compare the reference results.
Original synthetic input
{
"synthetic": true,
"case": "github-pr-watch",
"data": {
"prs": [
{
"id": "PR12",
"head": "new-b",
"checks": [
{
"sha": "old-a",
"status": "success"
},
{
"sha": "new-b",
"status": "pending"
}
],
"review": "unknown",
"state": "open"
},
{
"id": "PR13",
"head": "c",
"checks": [
{
"sha": "c",
"status": "success"
}
],
"review": "changes_requested",
"state": "open"
},
{
"id": "PR14",
"state": "merged",
"merged": true
},
{
"id": "PR15",
"head": "d",
"draft": true,
"checks": [
{
"sha": "d",
"status": "success"
}
],
"review": "not_reviewed",
"state": "open"
},
{
"id": "PR16",
"readable": false,
"error": "No read permission"
}
]
}
}Processing rules
Use snapshots only without inferring complete branch protection. Associate checks with the current head; old success does not pass a new commit. Keep CI, review, draft, conflicts and merged status separate. Unreadable is unknown, not closed.
Complete reference results under this tutorial’s rules; nothing was written to a third-party service.Scroll horizontally within the table if needed.
| PR | Current evidence | Suggested status | Next step |
|---|---|---|---|
| PR12 | New head pending; old head passed | Waiting for checks | Track new-b; do not report all passed |
| PR13 | CI passed; changes_requested | Review action needed | Inspect unresolved feedback |
| PR14 | Merged | Leave active queue | Retain merge record |
| PR15 | Draft; checks passed | Still draft | Author must make ready for review |
| PR16 | No permission | Unknown | Report access blocker |
An old green commit does not prove the new head passed.
CI success and changes_requested can coexist. This is not sufficient evidence of merge readiness.
PR report — synthetic snapshots PR12: new-b pending; old-a success is stale. PR13: handle review feedback; CI does not override changes_requested. PR14: merged, remove from active work. PR15: still draft. PR16: unreadable; status unknown. Unconfirmed: real branch protections, conflicts and security-check completeness. No board update, notification, merge or push.
Prepare the materials and check your tools
Start with the practice files
- Download five snapshots and identify current heads.
- Exercise ids are not real GitHub PRs.
- Classify before opening reference actions.
Before using real services
- Specify repository and PR list.
- Verify current-head, check and review read capabilities.
- Board writes, owner contact and CI reruns require their own scope.
Complete one file-based exercise first. For real services, verify the actual account, available tools and operation scope, then follow the acceptance check at each stage.
Download the original input and rules ↓Execution and takeover boundaries
The actions below require the agreed inputs, accounts and scope. Configuring a Routine does not expand that authorization.
Can run automatically
Read current commits, checks and reviews for specified PRs; report conflicts, draft state and merge state separately.
Requires confirmation
Confirm exact targets before changing Notion status, notifying owners, reviewing, editing code, rerunning CI or merging.
Take over after a failure
Mark mismatched SHA checks or inaccessible data as unknown. Have the user inspect the current commit, then update only records with verified changes.
Fix PR identity and observation time
A number needs its repository context. Real reports also need observation time and current head to explain stale results.
Inventory the five uploaded records, readability, heads and missing fields. Use snapshots only; do not connect GitHub/Notion or notify owners. Save index.md.Five identities and gaps.
PR16 remains unknown and PR14 remains merged.
Count only effective current-commit checks
Checks can target an old head or test merge commit. This exercise uses explicit SHA matching and does not invent protection rules.
Compare head with checks.sha. Separate old checks and current checks. PR12 new-b remains pending; old-a success does not count as a current pass. List unconfirmed branch protections.A commit-associated check table.
PR12 is not all checks passed.
Evaluate review, draft and merged dimensions separately
CI cannot summarize every condition. Preserve unknown review state where unavailable.
For each PR, list CI, review, draft, merged and readability, then a next step. Retain PR13 changes_requested and PR15 draft. Do not infer mergeable.Five status/action rows.
PR13/PR15 do not become ready solely because CI passed.
Write a report and a proposed board diff
A suggested state is not an actual board write. Keep the old value and evidence so the transition can be reviewed.
Generate a report and proposed board changes with PR ids and reasons. If the old value is unavailable, say needs verification. Merged leaves active; unreadable stays unknown. Deliver files only; no board edits or messages.A summary and pending changes.
Suggested and executed writes are clearly distinct.
Read current state again before a specific write
A new commit or review may arrive after the snapshot. Revalidate the exact version before updating any external record.
Read only <repository/PR list>. Record latest heads, checks, reviews, draft/merge states and time. If a specific Notion update is authorized, preview the diff and read it back. Do not notify agents, rerun CI, merge or push.A real report or access blocker.
Any write uses current evidence, not an old summary.
Follow meaningful changes without repeat noise
Persistent unreadability is a failure state, not no change. Record state versions, new faults and recovery.
Draft a pr-watch Skill with scope, heads, observed state, limits, diffs, failures and recovery. Propose a Routine only; stay quiet when unchanged. Contact requires separate authorization. Do not delegate across Bots or execute code actions.Rerun and notification rules.
Unchanged state is not repeatedly announced; new heads trigger fresh checks.
Find the evidence before choosing the next action
Yesterday’s green status was reused
Check the current head and effective check identity.
Requested changes became mergeable
Keep human review separate from CI.
403 became closed
An access error means unknown, not a business state.
Can it automatically ask an agent to fix it?
Prepare evidence first and wait for explicit messaging/delegation authorization.
Check every item before finishing
These page-local checkboxes reset on refresh. Checking them does not verify a real service connection.
Checked 0 / 6 items
Download the inputs separately from the reference answers
Start with input and rules without showing the reference answers. After acceptance, save the report and complete prompt set.
source-data.json↓Rules and scopeDefinitions, exceptions and delivery requirements.workflow-rules.md↓Item-by-item reference resultsCompare every input with its outcome.expected-results.csv↓Complete reference reportResults, evidence and missing information.reference-report.md↓All stage prompts6 instructions with expected outputs and acceptance checks.practice-prompts.txt↓Check documented capabilities and exercise results separately
Content updated: · Editing a page does not reverify its sources or live workflow.
Documentation review: Reviewed within the recorded scope ·
Reviewed effective checks for current head/test-merge commits, reviews and merge state. Public reads, Notion writes and sustained monitoring require separate acceptance.
Documentation review evidence and limits ↗
Live workflow verification: Partial verification · includes failed checks ·
Partial: Grok Bot read real public PR #3, its current-head checks and reviews; original API results were reviewed. CI, review and merged state are separate. Continuous tracking of open PRs, pagination, Notion writes, notifications and Routines remain untested; mergeable=null remains unknown.
Last execution attempt: · An attempt date does not establish a passed verification.
The PR snapshots, commit ids and reference results below are synthetic. A separate read-only run on 2026-10-18 checked public PR #3 and its current-head checks and reviews. Notion writes, notifications, continuous monitoring and Routines remain untested; see the verification record.
- GitHub: required status checks ↗
Associate effective checks with the current commit; the exercise uses synthetic snapshots.
- GitHub: resolving reviews ↗
Review status and automated checks are separate dimensions.
- Grok Bot: apps and the shared computer ↗
Check connected accounts, available tools, visibility and user takeover.
- Grok Bot: Skills and Routines ↗
Validate a manual run before saving a method or scheduling it.
Try another small batch of your own material
Retain original input and operation records. Verify that each result can be traced before adding connections or recurring runs.