ship-debrief
Ship Debrief
A periodic check-in that helps you reorient to what matters most. This is not a code review of the week. It's not an engineering retrospective. It's a conversation about where you spent your time, whether it mattered, and what to do next — even if the answer isn't more engineering.
Process
1. Read the profile
Read .claude/ship.local.md. If it doesn't exist, tell the user to run /ship:init first and stop.
2. Review recent work
Ask the user: "Just this repo, or all your repos?" Default to current repo if they say they don't care.
For the chosen scope, review the last 7 days of git history. But don't just catalogue commits — understand the story of the week:
More from withqwerty/ship
ship-init
Use this skill when the user wants to set up, configure, or initialize the ship plugin, create or update their ship profile, change their review mode, update their product brief, or edit .claude/ship.local.md. Trigger on "ship init", "set up ship", "configure ship", "create my profile", "update my profile", "change review mode to brutal/kind", or when any other ship skill detects that .claude/ship.local.md does not exist. Also use when the user says they've changed roles, shifted priorities, or moved to a new project stage.
1ship-think
Use this skill when the user is about to start building something and would benefit from hard questions before coding. Trigger on "ship think", "gut check", "sanity check", "should I build this", "before I start", "does this make sense", "is this worth building", "is this overkill", or "thoughts on this approach". Also trigger when the user describes a feature, migration, rewrite, or architectural change they're planning — even if they don't explicitly ask for a gut check. If someone says "I'm thinking of building X" or "I want to add X", this skill should activate to challenge assumptions before they start coding. Do NOT trigger for bug fixes, code explanations, or tasks already in progress.
1ship-focus
Use this skill when the user is mid-build and drifting, scope is creeping, or focus is lost. Trigger on "ship focus", "scope check", "refocus", "what should I cut", "am I scope creeping", "this is getting bigger than expected", "I'm losing focus", "I keep finding things to improve", "should I stop and ship what I have", or "new requirements came in". Also trigger when the user expresses frustration about a task growing beyond its original intent, mentions touching many more files than expected, or asks whether to change direction mid-build. Do NOT trigger for pre-build gut checks (use ship-think) or post-build reviews (use ship-review).
1