pkg-ship

Implements roadmap packages end-to-end from spec through worktree, tests, PR, and CI fixes.

Updated Dec 27, 2025
One-click install
npx skills add https://github.com/HendrikGC02/Astroray --skill pkg-ship-hendrikgc02
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pkg-ship
Source: https://github.com/HendrikGC02/Astroray/tree/main/.claude/skills/pkg-ship
Command: npx skills add https://github.com/HendrikGC02/Astroray --skill pkg-ship-hendrikgc02

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping a roadmap package in a large C++/CUDA renderer project involves many error-prone steps: reading the spec, branching correctly, implementing with tests, catching stale call sites, opening a PR, and fixing CI. This Skill codifies that entire sequence so nothing is skipped and recurring failure modes (like stale call sites breaking CI) are caught before push. ## Core Features & Use Cases - Spec-Driven Implementation: Reads the package spec end-to-end, extracts acceptance criteria, non-goals, and open design questions, and stops when owner input is required. - Worktree & Build Hygiene: Creates an isolated git worktree, verifies location, and scans for shadow .pyd files that could mask fresh builds. - Pre-Push Call-Site Sweep: Audits every changed signature across the repo (including tests, mocks, and Python bindings) before opening a PR. - Full PR Lifecycle: Runs the local test suite, opens a PR with measured acceptance criteria, watches CI, fixes failures, and resolves merge conflicts with explicit resolution statements. - Use Case: When the owner says "implement pkg88", invoke this Skill to go from spec to a green, review-ready PR without missing project-specific discipline rules. ## Quick Start Ask the AI to implement a specific roadmap package by name, for example: run /pkg-ship pkg88 to implement that package end-to-end from its spec through a green CI pull request.

Frequently Asked Questions about pkg-ship

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

FAQPage Schema
How do I implement a roadmap package end-to-end with this workflow?▼

Invoke /pkg-ship with the package name. The Skill reads the spec, creates a git worktree branch, implements the scoped phase with tests, sweeps for stale call sites, runs the local test suite, opens a PR, and fixes CI until green.

How to catch stale call sites before opening a pull request?▼

The Skill diffs changed headers and Python files for modified signatures, then greps the entire repo for callers, treating tests, mocks, and bindings as first-class call sites. Any stale caller is updated in the same commit as the signature change.

When should I not use the pkg-ship skill?▼

Do not use it for research-only sessions, spec filing without implementation, hardware verification of merged PRs, or multi-package coordination. It also stops when a spec has unresolved owner questions or requires unavailable hardware like an RTX GPU.

Why does CI fail after changing a function signature?▼

CI failures after signature changes are usually caused by stale call sites in tests, mocks, stubs, or Python bindings that were not updated. Re-running the call-site sweep from Step 4 typically identifies the outdated callers.

Does the skill auto-merge pull requests after CI passes?▼

No. When CI is green the PR is marked ready for review and the PR number is surfaced, but merging requires explicit owner authorization, especially for packages with C++ or CUDA changes.