oneshot-ship_skill

Overview

This skill lets you ship code with a single command using the oneshot CLI. It runs a full autonomous pipeline—plan, execute, review, and open a PR—either locally or over SSH, and integrates Claude and Codex to automate each step. Use it to delegate end-to-end code changes, create PRs, and enforce repo conventions automatically.

How this skill works

On invocation the tool validates the target repo, creates an isolated git worktree, and auto-detects/install dependencies. Claude generates an implementation plan, Codex implements the changes and reviews the diff, and Claude opens a branch and creates the PR. Worktrees are cleaned up after the run and optional integrations (Linear, CLAUDE.md) provide ticket context and enforcement.

When to use it

• You want to ship a code change without manual coding edits
• You need an automated plan→implement→review→PR workflow
• You want to run an autonomous coding pipeline on a remote server via SSH
• You want to run the full pipeline locally with installed CLIs
• You want to attach a Linear ticket as context and update its status automatically

Best practices

• Run oneshot init to configure host, workspace, and API keys before first use
• Keep CLAUDE.md in repo roots to enforce coding conventions and pass guidance to models
• Use --bg for long jobs to run detached on the server
• Set conservative per-step timeouts for large codebases to avoid runaway runs
• Run --dry-run to validate repo existence before executing changes

Example use cases

• Implement a small feature or bugfix by describing the task in one command and getting a PR back
• Convert a Linear ticket URL into an automated implementation and PR, with ticket status updated
• Run the pipeline on a build or staging server over SSH to keep local environment clean
• Use local mode to iterate quickly when Claude and Codex CLIs are available on your machine
• Create consistent PRs across many repos by dropping CLAUDE.md to standardize expectations