Skip to content

feat(ship): add shipping readiness skill - #618

Merged
baleen37 merged 1 commit into
mainfrom
worktree/drifting-sauteeing-lemur
Apr 15, 2026
Merged

feat(ship): add shipping readiness skill#618
baleen37 merged 1 commit into
mainfrom
worktree/drifting-sauteeing-lemur

Conversation

@baleen37

@baleen37 baleen37 commented Apr 15, 2026

Copy link
Copy Markdown
Owner

Summary

  • add a new /ship skill for shipping readiness review instead of deploy execution
  • add a /ship checklist reference and targeted BATS coverage
  • document the design and implementation plan for the new skill

Test Plan

  • bash tests/run-all-tests.sh

Summary by CodeRabbit

  • New Features
    • Added /ship skill as a launch-readiness gate for evaluating whether changes are ready to ship. Assesses pre-launch, rollout, rollback, and monitoring readiness. Produces structured output with blocking issues, warnings, per-area readiness assessments, and actionable next steps. Defines three decision states: Ready, Conditionally ready, and Not ready.

Add the new /ship skill as a launch-readiness gate with supporting checklist and test coverage.
@baleen37
baleen37 enabled auto-merge (squash) April 15, 2026 09:19
@coderabbitai

coderabbitai Bot commented Apr 15, 2026

Copy link
Copy Markdown
📝 Walkthrough

Walkthrough

The PR introduces a new /ship skill to the me plugin, implementing a launch-readiness gate (not a deploy executor) with supporting design specification, implementation plan, skill definition, reference checklist, and comprehensive test coverage.

Changes

Cohort / File(s) Summary
Design & Planning Documentation
docs/superpowers/specs/2026-04-15-me-ship-skill-design.md, docs/superpowers/plans/2026-04-15-me-ship-skill.md
Design specification and implementation plan for the /ship skill, defining goals, non-goals, output contract, readiness checking criteria, and testing strategy.
Skill Implementation
plugins/me/skills/ship/SKILL.md, plugins/me/skills/ship/references/ship-checklist.md
Skill definition file with frontmatter and detailed contract for /ship as a readiness gate, plus a reference checklist with structured guidance for assessing pre-launch, rollout, rollback, and monitoring criteria.
Test Coverage
tests/me/me-specific.bats, tests/skills/test_ship_skill_content.bats
New and updated Bats test suites validating skill file presence, frontmatter structure, required Markdown sections, gate vs. deploy distinction, and readiness outcome markers.

Poem

🐰 A shipping gate hops into place,
No deploy commands in this space—
Just readiness checks, all neat and clean,
With checklists and tests in between!
Ready or not? The /ship will show,
Before any changes take flight and go. 🚀

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'feat(ship): add shipping readiness skill' clearly and concisely describes the main change: introducing a new /ship skill for shipping readiness assessment.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch worktree/drifting-sauteeing-lemur

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.

auto-merge was automatically disabled April 15, 2026 09:19

Repository rule violations found

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
docs/superpowers/plans/2026-04-15-me-ship-skill.md (1)

353-356: Small readability tweak for repeated bullet openings.

These three bullets all begin with “If …”. Rewording to parallel “For failures …” phrasing reads cleaner.

✍️ Suggested wording tweak
-- If the failure mentions `has_frontmatter_field` or delimiter checks, edit `plugins/me/skills/ship/SKILL.md` frontmatter only.
-- If the failure mentions missing file paths, create or rename only the missing `/ship` files.
-- If the failure mentions specific text assertions, update only the exact tested wording in `plugins/me/skills/ship/SKILL.md` or `tests/skills/test_ship_skill_content.bats`.
+- For failures mentioning `has_frontmatter_field` or delimiter checks, edit only `plugins/me/skills/ship/SKILL.md` frontmatter.
+- For failures mentioning missing file paths, create or rename only the missing `/ship` files.
+- For failures mentioning specific text assertions, update only the exact tested wording in `plugins/me/skills/ship/SKILL.md` or `tests/skills/test_ship_skill_content.bats`.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docs/superpowers/plans/2026-04-15-me-ship-skill.md` around lines 353 - 356,
Update the three bullet points in
docs/superpowers/plans/2026-04-15-me-ship-skill.md so their opening phrase is
parallel — change the leading "If ..." to "For failures ..." in the bullets that
reference edits to plugins/me/skills/ship/SKILL.md, creation/renaming of /ship
files, and updates to plugins/me/skills/ship/SKILL.md or
tests/skills/test_ship_skill_content.bats; keep the rest of each bullet
unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@plugins/me/skills/ship/SKILL.md`:
- Line 49: In SKILL.md update the inconsistent link path: replace the reference
string "ship/references/ship-checklist.md" with the relative format
"references/ship-checklist.md" so it matches other skills (e.g., qa, jira
daily-standup) and resolves correctly relative to the skill directory.

---

Nitpick comments:
In `@docs/superpowers/plans/2026-04-15-me-ship-skill.md`:
- Around line 353-356: Update the three bullet points in
docs/superpowers/plans/2026-04-15-me-ship-skill.md so their opening phrase is
parallel — change the leading "If ..." to "For failures ..." in the bullets that
reference edits to plugins/me/skills/ship/SKILL.md, creation/renaming of /ship
files, and updates to plugins/me/skills/ship/SKILL.md or
tests/skills/test_ship_skill_content.bats; keep the rest of each bullet
unchanged.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 42acbeae-cb96-4b85-aff3-7ef5a60f12a1

📥 Commits

Reviewing files that changed from the base of the PR and between 07ed610 and 5588442.

📒 Files selected for processing (6)
  • docs/superpowers/plans/2026-04-15-me-ship-skill.md
  • docs/superpowers/specs/2026-04-15-me-ship-skill-design.md
  • plugins/me/skills/ship/SKILL.md
  • plugins/me/skills/ship/references/ship-checklist.md
  • tests/me/me-specific.bats
  • tests/skills/test_ship_skill_content.bats

3. **Rollback** — Could the team explain how to recover if the launch goes badly?
4. **Monitoring** — Are there logs, metrics, alerts, or explicit watchpoints that would reveal success or failure?

For concrete examples and decision patterns, read `ship/references/ship-checklist.md`.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== Reference links in existing SKILL.md files =="
fd -t f SKILL.md plugins | while read -r file; do
  echo "-- $file"
  rg -n "references/.*\\.md" "$file" || true
done

echo
echo "== Ship skill reference line(s) =="
rg -n "ship/references/ship-checklist\\.md|references/ship-checklist\\.md" plugins/me/skills/ship/SKILL.md

echo
echo "== Places documenting expected reference style =="
rg -n "references/ship-checklist\\.md|ship/references/ship-checklist\\.md|ship checklist|SKILL\\.md" docs tests plugins

Repository: baleen37/bstack

Length of output: 37037


Use relative path format consistent with other skills.

Line 49 uses ship/references/ship-checklist.md, but all other skills (qa, jira daily-standup, jira generate-status-report, etc.) use the relative format references/filename.md. Change to references/ship-checklist.md to match the established convention and ensure the path resolves correctly relative to the skill directory.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@plugins/me/skills/ship/SKILL.md` at line 49, In SKILL.md update the
inconsistent link path: replace the reference string
"ship/references/ship-checklist.md" with the relative format
"references/ship-checklist.md" so it matches other skills (e.g., qa, jira
daily-standup) and resolves correctly relative to the skill directory.

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