A continuous delivery orchestration skill that automates PingCode work item resolution, branching, merge requests, code reviews, and reporting.
Install & Download
1. ClawHub CLI
The fastest way to install a skill directly from the registry.
npx clawhub@latest install e2e-delivery
2. Manual Installation
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
3. Prompt Installation
Copy this prompt to OpenClaw to install it automatically.
Help me install e2e-delivery using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Prefer to download?
Get the raw skill files in a ZIP archive.
What is e2e-delivery?
The e2e-delivery driver is designed to streamline the software development and release pipeline. By taking a PingCode work item URL, ID, or a natural language description, it manages five main execution phases: preparation, development, submission, verification, and delivery. It functions as a stateful orchestrator that continuously updates local session files using dedicated Python scripts to prevent data loss or flow corruption. It offers structured assistance for developers looking to automate repetitive Git and project management operations.
Integrating with Openclaw Skills, this automation engine reduces manual overhead by automatically initiating branching, checking local builds, creating merge requests, and validating merge conditions. The process handles human intervention points with non-blocking waiting states, guaranteeing that code reviews and deployment checkpoints are respected before finalizing delivery.
e2e-delivery Use Cases
- Automating the entire lifecycle of a PingCode issue, task, or bug from a single CLI command.
- Orchestrating Git branch creation, local validation, and remote pushing based on project management tickets.
- Automating merge request creation and linking them with downstream project management work items.
- Standardizing delivery reporting by automatically compiling development metrics and syncing them to REDoc.
How e2e-delivery Works
- Input Identification: The driver checks if the input is a direct PingCode URL/ID (Mode A) or a natural language instruction (Mode B), calling necessary helper modules to retrieve or create the ticket.
- Environment Precheck: It validates local configurations, checking if required CLIs (such as ee-cli, hi, and git) are installed and up to date, and verifies SSO credentials.
- Preparation & Dev: The system initializes or restores a session file, cuts a new feature branch, checks local builds, and pushes the changes.
- Submission & Verification: A Merge Request is generated and linked to the task. It handles manual deployment blockages elegantly via a gate-wait status.
- Validation & Delivery: It carries out double checks before merging (MR checklists and pipeline approvals), closes the ticket, writes a Markdown report locally, and publishes it online.
e2e-delivery Setup
Ensure that ee-cli, hi, and git are installed on your system. To use this with other Openclaw Skills, check your local configuration file:
# Check status or perform SSO login
ee-cli login
# Configure REDoc integration properties
cat <<EOF > ~/.claude/e2e-delivery/config.json
{
"redocParentId": "YOUR_REDOC_PARENT_PAGE_ID"
}
EOF
The orchestration processes run autonomously, triggering sub-skills like pingcode-assistant-pro or hi-docs when necessary.
e2e-delivery Data Schema & Taxonomy
The execution state is managed via a JSON session file located at ~/.claude/e2e-sessions/<workitem-id>.json. All file updates must be handled by scripts/session.py to preserve automatic field population (e.g., durationMs, updatedAt).
| Location | File Pattern | Purpose |
|---|---|---|
| Session Records | ~/.claude/e2e-sessions/<workitem-id>.json |
Maintains execution phase and state history |
| Local Reports | docs/e2e-reports/<workitem-id>-<yyyymmdd>.md |
Markdown delivery report compiled upon success |
| Configuration | ~/.claude/e2e-delivery/config.json |
Global settings such as REDoc parent ID |
e2e-delivery Advanced Features
- Interactive Resumption: If a session exists, it queries the user to either resume from the last known state or archive and restart.
- Work Item Auto-Conversion: Converts a parent requirement into developer tasks automatically if cloud platform constraints require subtask-level associations.
- Double-Lock Verification: Enforces rigorous checklist confirmations and verification checks prior to code merge, preventing unverified code deployments.
- REDoc Sync Failure Fallback: Ensures local Markdown report creation succeeds even if the network upload to REDoc encounters an error.
SKILL.md
Loading
Related Openclaw Skills
scrapfly-cli
A comprehensive command-line interface and MCP server to orchestrate Scrapfly scraping, automated rendering, screenshots, and remote CDP browser sessions.
Ghost Eye
Ghost Eye functions as an image preprocessing bridge, converting visual data into rich OCR text and scene descriptions for pure-text LLMs.
scrapfly-agent-rules
A set of architectural principles for coordinating stateless scraping and stateful Cloud Browser interactions using a connected Scrapfly MCP server.
Kubernetes Pod Logs Analyzer
An AI-powered log aggregation and anomaly detection tool for live monitoring of Kubernetes namespace pods.
File-Count Threshold Probe
A diagnostic utility that binary-searches multipart part-count limits to identify upload thresholds and prevent HTTP 413 errors.
SVG to PPT Skill
Convert SVG content, geographic maps, and Chinese character stroke orders into fully editable PowerPoint presentations.
Featured*
