Claude Code tells engineer: don't move the CodeRabbit skill to cloud

The exchange is a follow-up to an earlier article in which the same engineer taught Claude Code a set of work patterns. This time the request was to move an existing skill, /coderabbit-queue, off the local machine and into a cloud session so it would survive the PC being closed. Claude Code's first line was a refusal, and its reasons came from the engineer's own history: a prior decision to narrow the GitHub app to 3 repositories, recorded in CLAUDE.md and memory, put the target repos out of reach. The proposed alternative, a GitHub Actions queue, came with its weak points listed in the same table — scheduled runs can drift by several minutes, and one token has to be managed. Claude Code ended with three options, including the cloud route marked as a choice made with full awareness of the trade-offs. The engineer picked keeping the current setup, a decision made on a non-technical measure: a weekend hobby project can absorb a 1–2 hour review delay. What the piece illustrates is that a useful assistant can surface a forgotten constraint before building anything, and that the final call still belongs to the person.