spec-shippability-review

Detect dev-tree references and unshipped helpers in specification changes.

5|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/friedbotstudio/baseline --skill spec-shippability-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-shippability-review
Source: https://github.com/friedbotstudio/baseline/tree/main/.claude/skills/spec-shippability-review
Command: npx skills add https://github.com/friedbotstudio/baseline --skill spec-shippability-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill catches spec changes that would accidentally ship dev-tree references or unshipped helpers into consumer installs, preventing runtime failures before approval.

Core Features & Use Cases

  • Spec draft review: Checks drafted specs for runtime invocations that point at development-only paths.
  • Shipped skill audit: Re-scans actual shipped SKILL.md files to ensure they only reference files included in the consumer manifest.
  • Python helper gate: Flags new Python helpers under shipped skill directories and distinguishes grandfathered edits from new violations.
  • Use case: A maintainer updates a workflow spec and wants a read-only punch list of blocker and advisory issues before approving it.

Quick Start

Ask the skill to review a spec slug and report any blocker or advisory shippability findings.

Frequently Asked Questions about spec-shippability-review

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

FAQPage Schema
How do I check a skill spec for unshipped dev-tree references before publishing?▼

To check a skill spec for unshipped dev-tree references, validate the spec draft against the shipped consumer manifest to detect development-only path prefixes and output a read-only punch list of blocker or advisory findings.

What is a spec shippability review for consumer installs?▼

A spec shippability review is a validation process that detects specification changes which would accidentally ship dev-tree references or unshipped Python helpers into consumer installs, preventing runtime failures before approval.

How do I validate Python helper additions in a shipped skill directory without blocking grandfathered edits?▼

To validate Python helper additions, scan the shipped skill directory for new helper files and distinguish grandfathered edits from new violations by checking them against the shipped manifest, outputting advisories for new unshipped helpers.

Does spec shippability review work on already shipped SKILL.md files to find runtime import leaks?▼

Yes, spec shippability review works on shipped SKILL.md files by re-scanning them to ensure they only reference files included in the consumer manifest and flagging any runtime imports or shell-fence invocations pointing to unshipped paths.

What are the limitations of read-only punch-list output for spec review?▼

The limitation of read-only punch-list output is that it only reports blocker and advisory findings without modifying the spec, meaning maintainers must manually resolve all detected dev-tree references and unshipped helper violations before approval.