Get PR notifications by SMS, then ask a follow-up

Turn a review-ready change into a useful text

You leave the desk while your agent finishes a fix. The PR is ready, but you do not yet know whether it is a tiny correction or a change that needs careful attention. A short SMS can name the PR, describe the change, and report the checks the agent actually ran.

The agent can text a result such as “PR #42: parser fix, regression added, checks passed.” You can then ask about one edge case from your normal SMS inbox. The connected agent reads that question in the workspace that already holds the code and test output.

A text is useful for deciding what to inspect next. Open the diff and full test evidence in your review environment when you need the details.

Set up the agent that prepares the PR

Follow local-agent setup, then test a complete text and reply. The Codex SMS and Claude Code SMS pages cover those environments.

Tell the agent when to notify you and how much context to include. It needs to know which result counts as ready: an actual PR, a branch ready for review, or a draft summary. Ask it to describe the state accurately.

Keep the local computer awake and online with the agent active. Campfire SMS transports the update; your agent supplies the repository tools and observes whether the work is ready.

Use a PR notification prompt with real evidence

Work on the fix within our agreed scope. When the change is ready for review, text me through Campfire SMS with the PR or branch identifier, a one-sentence summary, and the checks you actually completed. Mention a material unresolved issue. Keep the bridge open for the reply window we agreed, check for my questions, and answer using the code and results in this workspace.

If checks have not run, the update should say so. If a PR still needs manual setup or a permission approval, say what remains. That lets you decide whether to return to the computer without mistaking “prepared” for “published” or “passed.”

Ask a question that narrows the review

• “Which files changed?” asks for the footprint before you open the diff.
• “Summarize the migration risk.” asks the agent to focus on the decision that matters.
• “Does the regression cover empty input?” asks for a specific test fact.
• “Add a note about the manual check.” clarifies the review description within the existing task.

SMS supplies task input. Repository protections, review requirements, and native runtime approvals continue to apply. Use the phone decisions and approvals guide to understand that boundary.

Agent updates and GitHub event notifications

This workflow starts with an agent that knows about the PR it is preparing. Installing Campfire SMS alone does not subscribe you to every GitHub comment, review, or repository event. A separate watcher or integration would need to observe those events and send messages.

For a reminder to review tomorrow after today's agent session ends, choose a persistent scheduler. For a question about active work, use the SMS reply path. The notifications vs reminders guide explains the difference.

Common questions