oneshot-ship
Ship code with oneshot CLI. One command that plans, executes, reviews, and opens a PR. Runs over SSH or locally. Use when the user wants to ship code changes, automate PRs, or run a coding pipeline with Claude and Codex.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/adwilkinson/oneshot-shipWhat This Skill Does
The oneshot-ship skill acts as an autonomous engineering co-pilot designed to handle the entire lifecycle of a code change. By leveraging a multi-agent orchestration pipeline, it automates the traditional development workflow. When triggered, the agent performs a sequence of high-level actions: it validates the repository environment, creates a temporary git worktree to maintain workspace integrity, utilizes Claude for strategic planning, Codex for technical execution and self-review, and finally integrates with GitHub to open a pull request. It is engineered to run either locally or via SSH, making it ideal for remote server management or local environment automation. By delegating the grunt work of planning and implementation to specialized models, you can focus on architectural decisions while ensuring that repository conventions are strictly followed.
Installation
To integrate this skill into your OpenClaw environment, execute the following command in your terminal:
clawhub install openclaw/skills/skills/adwilkinson/oneshot-ship
Additionally, ensure that the system dependencies—Bun, Claude Code CLI, Codex CLI, and GitHub CLI—are installed and properly authenticated on the machine where the execution will occur.
Use Cases
- Automated Feature Implementation: Quickly prototype and ship features by providing a high-level task description.
- Linear Workflow Integration: Seamlessly link coding tasks to project management tickets, ensuring status updates are automated once the PR is submitted.
- Headless Pipeline Execution: Run complex refactoring or repetitive coding tasks on a remote server while you are away from the machine, utilizing the background mode.
- Safe Experimentation: Use the dry-run flag to ensure repository access and environment health without committing any changes to the codebase.
Example Prompts
- "oneshot my-org/web-app 'Add a dark mode toggle to the navigation bar, following our existing Tailwind CSS conventions.'"
- "oneshot my-org/api 'Integrate the new Stripe webhook handler and add validation logic for incoming requests' https://linear.app/my-org/issue/ENG-123"
- "oneshot my-org/data-service 'Refactor the database connection pool to use a singleton pattern' --local"
Tips & Limitations
- Configuration: Ensure your
~/.oneshot/config.jsonis accurately populated. The tool relies heavily on thebasePathto locate repositories. - Conventions: The tool respects
CLAUDE.mdfiles; keeping these files updated in your repositories will significantly improve the quality of generated code. - Timeouts: If dealing with large codebases, adjust the
stepTimeoutsin your config file to prevent the pipeline from cutting off during deep analysis. - Safety: Always review the generated pull request. While the tool includes a self-review step by Codex, human oversight is recommended before merging changes to production branches.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-adwilkinson-oneshot-ship": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: network-access, file-write, file-read, external-api, code-execution