Skip to content

refactor(me): replace ship fan-out with shipping-and-launch renamed to ship - #655

Merged
baleen37 merged 1 commit into
mainfrom
feat/improve-ship2
May 16, 2026
Merged

refactor(me): replace ship fan-out with shipping-and-launch renamed to ship#655
baleen37 merged 1 commit into
mainfrom
feat/improve-ship2

Conversation

@baleen37

@baleen37 baleen37 commented May 16, 2026

Copy link
Copy Markdown
Owner

Summary

  • Remove the parallel fan-out orchestrator ship skill and promote shipping-and-launch to the ship name
  • The two skills overlapped in purpose; the checklist-driven pre-launch skill is the one worth keeping
  • Update plugins/me/README.md and internal references accordingly

Changes

  • Delete plugins/me/skills/ship/ (old fan-out orchestrator)
  • Rename plugins/me/skills/shipping-and-launch/plugins/me/skills/ship/
  • Update new ship/SKILL.md: frontmatter name, title, and remove now-self-referential /ship handoff notes
  • Collapse two ship-related entries in plugins/me/README.md into one

Test plan

  • git mv preserves history for the renamed skill
  • No remaining shipping-and-launch references under plugins/
  • CI green

Summary by CodeRabbit

  • Documentation
    • Updated deployment workflow documentation to emphasize staged rollouts, monitoring, and operational readiness over previous go/no-go decision model.
    • Consolidated deployment guidance with comprehensive pre-launch checklists, feature-flag lifecycle guidance, rollback strategies, and post-deployment verification procedures.

Review Change Stack

…o ship

Remove the parallel fan-out orchestrator and promote the
shipping-and-launch pre-launch checklist skill to the `ship` name.
The two skills overlapped in purpose and the checklist-driven skill is
the one worth keeping.
@baleen37
baleen37 enabled auto-merge (squash) May 16, 2026 16:24
@coderabbitai

coderabbitai Bot commented May 16, 2026

Copy link
Copy Markdown

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: efb18bf5-ca93-4771-882d-08e0d01e49b9

📥 Commits

Reviewing files that changed from the base of the PR and between 2436c03 and 0c9e452.

📒 Files selected for processing (3)
  • plugins/me/README.md
  • plugins/me/skills/ship/SKILL.md
  • plugins/me/skills/shipping-and-launch/SKILL.md

📝 Walkthrough

Walkthrough

The /ship skill documentation was completely redesigned from a parallel fan-out review orchestrator to a production-launch readiness playbook. The README overview was updated to emphasize staged rollout and operational monitoring. New sections cover pre-launch checklists, feature-flag lifecycle management, staged rollout decision thresholds, error-reporting instrumentation templates, rollback procedures, and post-deploy verification checkpoints.

Changes

Ship Skill Redesign

Layer / File(s) Summary
Ship skill core framework and overview
plugins/me/README.md, plugins/me/skills/ship/SKILL.md
The Ship lifecycle step description in README was updated from fan-out launch review to emphasize staged rollout, monitoring, and production checks. The ship skill opening replaced the parallel fan-out orchestrator model with a "Prepares production launches" framing covering automation policy and execution workflow.
Pre-launch checklist and feature-flag strategy
plugins/me/skills/ship/SKILL.md
Structured pre-launch checklist with items across code quality, security, performance, accessibility, infrastructure, and documentation. Feature-flag strategy section includes lifecycle timeline, ownership/expiration rules, nesting prohibitions, and CI coverage requirements.
Staged rollout and monitoring observability
plugins/me/skills/ship/SKILL.md
Staged rollout guidance with explicit decision/threshold table for advancing, holding, or rolling back across stages. Monitoring and Observability section expanded with error-reporting template snippets for client boundaries and server middleware, plus first-hour post-launch verification checklist.
Rollback strategy and post-deploy verification
plugins/me/skills/ship/SKILL.md
Rollback strategy template with trigger conditions, rollback steps, database considerations, and time-to-rollback guidance. Added "See Also", "Common Rationalizations", "Red Flags" sections, and comprehensive pre/post-deploy verification checklist covering health, error rates, latency, logs, and rollback readiness.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

  • baleen37/bstack#654: Modifies plugins/me/skills/ship/SKILL.md frontmatter to allow model invocation, while this PR rewrites the skill's playbook content and lifecycle description.
  • baleen37/bstack#641: Locks /ship to explicit invocation via disable-model-invocation: true, while this PR rewrites the skill's launch/playbook content.
  • baleen37/bstack#652: Expands plugins/me/skills/shipping-and-launch/SKILL.md with safe automation policy, while this PR consolidates that guidance by removing the file and integrating its concepts into the ship skill.

Poem

🐰 The ship sets sail with checklist in hand,
Staged rollouts guard the promised land,
With monitoring eyes and rollback plans,
Production launches flow like desert sands,
From preflight checks to post-deploy cheer—
Safe sailing draws ever near! 🚀

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/improve-ship2

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@baleen37
baleen37 merged commit 474f601 into main May 16, 2026
4 of 5 checks passed
@baleen37
baleen37 deleted the feat/improve-ship2 branch May 16, 2026 16:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant