shift

Verify the prerequisites (repository setup, cloud environment, GitHub App rights, merge policy), then let the Skill draft a RemoteTrigger routine body with a cron expression and self-contained shift prompt. It creates the routine only after you confirm, then runs it once manually to verify.

One shift integrates finished worker pull requests with green checks and approvals, marks covered tasks done in tasks.md on MySpec, plans the next wave of grouped tasks, dispatches one cloud worker session per group, and posts a summary report to a tracking issue before stopping.

Yes, but only under the squash policy you choose: it merges one green, approved pull request at a time with --match-head-commit, waits for default-branch checks, and never crosses a milestone boundary. The report-only policy verifies and lists mergeable pull requests without merging.

The shift prompt checks gh auth status and looks for MySpec MCP tools at run time. Without GitHub access it stops and reports; without MySpec tools it skips tasks.md writes, reads any committed local copy, and defers task marking to the interactive manager.

Routines cannot attach MCP servers configured in Claude Code, cannot be deleted from the Skill (pause or delete at claude.ai/code/routines), require a minimum one-hour cadence, and stop after two consecutive worker failures. The first run must be triggered manually and its log reviewed.