ship

Close a CR after audit PASS with human confirmation and closure artifact.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/LeoCode03/spkie_gpu --skill ship-leocode03
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/LeoCode03/spkie_gpu/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/LeoCode03/spkie_gpu --skill ship-leocode03

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Formalizes the closure of a CR after post-build audit, ensuring human confirmation, recording decisions, surfacing lessons, and generating follow-up work when needed.

Core Features & Use Cases

  • Verifies that acceptance criteria are met, documents the closure outcome, surfaces lessons learned, and preserves auditability.
  • Creates follow-up CRs when necessary and produces the closure artifact for compliance.
  • Requires human confirmation before closing to prevent premature closure.

Quick Start

Provide the CR-ID after an audit PASS to initiate the closure workflow.

Frequently Asked Questions about ship

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate CR closure after a successful post-build audit?

Automate CR closure by triggering the workflow after an audit PASS verdict, which validates acceptance criteria, documents decisions, and requires human confirmation before final closure.

What is the formal process for documenting lessons learned during change request closure?

Documenting lessons learned during change request closure involves validating acceptance criteria, recording project decisions, surfacing follow-up work if needed, and producing a final closure artifact for compliance.

How do I generate a closure artifact and create follow-up CRs when audit criteria are met?

Generate a closure artifact and create follow-up CRs by initiating the closure workflow after an audit PASS, which automatically surfaces follow-up work and enforces human confirmation before finalizing outcomes.

Can I close a change request without human confirmation after an audit pass?

Closing a change request without human confirmation is not possible, as the workflow explicitly requires manual approval before closing to prevent premature CR closure and ensure auditability.

Why does formal CR closure require validating acceptance criteria and bundling references?

Formal CR closure requires validating acceptance criteria and reading bundled references to ensure project decisions align with audit outcomes, preserving compliance and generating accurate follow-up work.

What are the limitations of automating project management closure for change requests?

The limitation of automating project management closure is that it cannot bypass the mandatory human confirmation step, ensuring automated CR closure still requires manual verification before finalizing the artifact.