pr-ship

What This Skill Does

The pr-ship skill is a sophisticated pre-shipment auditing tool designed specifically for the OpenClaw ecosystem. It acts as an automated quality gate that analyzes your current branch changes against the main branch, providing a structured risk assessment before you push your code. By leveraging a series of reference layers, including architecture maps and timeless coding principles, pr-ship identifies potential architectural regressions, blast radius concerns, and version-specific gotchas. It performs dynamic exploration of your codebase, using read-only commands to assess the impact of your modifications on core modules and system stability. It does not gate your PRs; rather, it provides a comprehensive, evidence-backed report with severity-coded findings (🟢/🟡/🔴) to ensure you are fully informed of the technical debt or risks introduced in your pull request.

Installation

You can install this skill directly via the Clawhub CLI by running the following command:

clawhub install openclaw/skills/skills/glucksberg/pr-ship

Ensure you have your environment configured to access the openclaw/skills repository. We highly recommend running clawhub update pr-ship frequently to ensure the skill remains synchronized with the latest OpenClaw releases, as this keeps the version-specific context, such as behavioral changes and active risk areas, up to date.

Use Cases

• Pre-Merge Validation: Before creating a PR, run this to catch potential cross-module coupling issues you might have overlooked.
• Risk Assessment for Refactors: When changing core logic in critical modules, use pr-ship to identify which parts of the system are potentially affected by the blast radius.
• Dependency Verification: Quickly check if your changes align with current version-specific guidelines, preventing integration headaches after a release cycle.
• Onboarding/Audit Assistance: Use the generated reports to understand the structural impact of complex PRs, making code reviews significantly faster and more accurate.

Example Prompts

1. "@openclaw run pr-ship to analyze my current changes and identify any high-severity risks before I merge."
2. "@openclaw please check if my changes to the networking module violate any ARCHITECTURE-MAP guidelines using pr-ship."
3. "@openclaw run pr-ship and tell me if I've touched any files that might trigger a regression in the current OpenClaw version context."

Tips & Limitations

• Maintain References: Ensure your references/ directory contains STABLE-PRINCIPLES.md, ARCHITECTURE-MAP.md, EXPLORATION-PLAYBOOK.md, and VISION-GUIDELINES.md for the best results.
• Optional Context: While CURRENT-CONTEXT.md is optional, keeping it updated significantly improves the tool's ability to identify release-specific gotchas.
• Read-Only Nature: Remember that this skill performs read-only operations using commands like grep, find, and git. It cannot modify your code; it only provides the data needed for you to make informed decisions.
• Scope: The skill is strictly for OpenClaw repositories and relies on standard git diff mechanics; it may have limited utility in non-standard project structures.