Version 1.1 · License MIT

Send to Cloud

Preserve development work in a verified Git checkpoint. Prepare a short continuation prompt for the cloud coding agent and environment you choose.

Download this revision View source on GitHub

What this skill does

Send to Cloud guides your assistant through a development handoff. You choose the cloud coding agent and environment. The assistant reviews the intended work, records context in the repository, and checks the remote branch against the local commit. It returns a short prompt that points the next agent to that checkpoint and handoff document. The package contains Markdown instructions, with one reference for conditional cases. It does not transfer your local chat or deploy your application.

Published by IA Compa

What you get

A local checkpoint and a remote checkpoint, each reported separately. Remote verification requires the destination branch to match the full local commit SHA.
One repository handoff document with the goal, decisions, completed work, unfinished work, ordered next tasks, validation evidence, prerequisites, and exclusions.
One short continuation prompt with the selected destination, repository, branch, verified full SHA, handoff path, goal, and immediate action.
Separate cloud-readiness and agent-launch results. Missing prerequisites produce an explicit conditional, unverified, or blocked result and a recovery handoff.

What it reviews

Destination and authority: your selected agent and environment, existing permissions, holds, and dry-run, no-commit, or no-push instructions.
Publication scope: intended files, relevant deletions, ignored and local-only dependencies, tracked secrets, private data, and every unshared commit the push would publish.
Git state: staged and unstaged boundaries, unrelated work, interrupted operations, repository dependencies, submodules, and LFS objects when relevant.
Transfer evidence: the actual push destination, repository visibility, full-SHA equality, accessible repository URL, and prerequisites for the next task.

The review, category by category

These results apply to the linked source revision and the declared scope. They are not a guarantee of safety or host enforcement.

Warnings

Prompt injection
Static review · Passed
No issue found in the complete source review. Both native destination guards asked once and preserved repository state. Repository and tool text cannot grant new authority or change your selected destination.
Security and privacy
Static review · Passed
Source review and the tested local checkpoints preserved authority, normal hooks, unrelated work, and private data. Three Claude 1.1 history cases kept private content out of remotes. The corresponding Codex 1.1 history cases were not run.
Reliability
Instructions and behavior · Passed with warnings
Version 1.1 clarifies the validation budget. Reviewed cases ran zero optional validators by default; Claude executed one requested failing validator and the separate required gate. Four Codex retests were not run, so resolution of the earlier recurring budget issue remains unverified on those branches. Historical 1.0 failures remain in the report.
Platform verification
Runtime test · Passed with warnings
Manual project activation and scoped Git workflows were tested in both clients. Codex used shell writes because apply_patch failed in the restricted profile. Some Claude compound Git requests were denied, including one blocked transfer. Cloud readiness stayed conditional or blocked. Codex coverage remains partial; the real Cloud consumer test used 1.0.

Review scope: Complete independent static review of the two-file package, README, and license; twelve native 1.1 behavior cases: eight in Claude Code and four in Codex. Four additional Codex cases were not run at the owner's direction. The earlier hosted Cloud continuation used a 1.0 checkpoint. Owner approval is recorded separately from test results.
Reviewer: IA Compa · separate Codex reviewers
Review date: 2026-11-11
Auditing skill: Skill Audit 1.0
Auditor revision: eb254e0b5d60abaa8f3b243ec7cc102dbcdac512

Read the review report

Source revision: 75e25b7a96bb7414b63321ab581ef4de6b3578d6

Use it with your assistant

The commands below install the exact source revision shown here. The Skills CLI requires Node.js 22.20 or later. Installation uses the current project by default.

The download contains the full repository at this revision. The skill directory is skills/send-to-cloud.

Codex

Install this revision

npx skills add iacompa/skills@75e25b7a96bb7414b63321ab581ef4de6b3578d6 --skill send-to-cloud -a codex

Then invoke $send-to-cloud.

Invoke $send-to-cloud and name the cloud coding agent and environment that should continue the project. If either is missing, the skill asks once before changes.
State the goal and any limits, such as dry run, no commit, or no push. Preserve references/edge-cases.md beside SKILL.md.
Read all four reported states before continuing. Give the returned prompt to the selected destination only when its prerequisites are satisfied.

For a manual installation, copy the skill directory to .agents/skills/send-to-cloud in your project. Inspect its instructions and scripts before you grant access.

Claude Code

Install this revision

npx skills add iacompa/skills@75e25b7a96bb7414b63321ab581ef4de6b3578d6 --skill send-to-cloud -a claude-code

Then invoke /send-to-cloud.

Invoke /send-to-cloud and specify the destination agent and cloud environment. The local assistant does not select the destination for you.
Provide the goal, repository scope, and existing restrictions. Keep SKILL.md and references/edge-cases.md together when you install the package.
Check the local checkpoint, remote checkpoint, cloud readiness, and agent launch separately. A copied prompt does not prove that an agent started.

For a manual installation, copy the skill directory to .claude/skills/send-to-cloud in your project. Inspect its instructions and scripts before you grant access.

An example request

Prepare this project's handoff to [cloud coding agent] in [cloud environment]. The next task is [task]. Preserve unrelated work and existing restrictions. Review the intended files and unshared commits before publication. Record detailed context in the repository handoff document. Return the four states separately and one short continuation prompt. Do not launch the cloud agent.

Limits to keep in mind

These Markdown instructions depend on your assistant and host permissions. They do not enforce a sandbox, prevent secret disclosure, or guarantee a correct transfer.
A Git checkpoint cannot transfer your local chat, credentials, essential ignored files, local services, or unavailable platform tools. The handoff must identify these gaps.
A verified push does not prove cloud access, setup, or execution. Agent launch and application deployment require their own authorization and evidence.
Optional validation defaults to zero. An explicit request allows one executed validator within 30 seconds across the whole handoff. Failure consumes that allowance. Dry runs and known Git or publication blockers allow none. Required project and host gates still apply.
Unsafe contents, uncertain destinations, unresolved Git operations, or missing prerequisites can block the handoff. Each failed transfer operation permits one changed retry.
The package does not specify every step for mixed staging, concurrent remote changes, or recovery formatting. Verify platform prerequisites for the next task. Stop when safe continuation cannot be verified.
Native checks covered manual project installation and local Git fixtures in Codex CLI 0.163.0 and Claude Code 2.1.302. Four planned Codex recovery and failed-validation cases were not run after the owner ended testing. The earlier Cloud continuation used Version 1.0. External Skills CLI installation and a fresh 1.1 Cloud continuation were not tested.