boatswain
01Agent Claude Code
Shipshape Boatswain: hygiene, verification recheck, and local commit custody. Use for pre-clean scans and post-implementation custody.
Agent Claude Code
Shipshape Boatswain: hygiene, verification recheck, and local commit custody. Use for pre-clean scans and post-implementation custody.
Agent Claude Code
Shipshape Captain: specification author, voyage lead, and outbound liaison. Use for voyage planning and spec-driven dispatch.
Agent Claude Code
Shipshape Crew Mate: the smallest production change for one named failing verification target. Use when QM dispatches a failing target.
Agent Claude Code
Shipshape Quartermaster: fresh-context verification and executable coverage from durable repository artifacts only. Use for the QM phase of the Shipshape workflow.
Agent Claude Code
Shipshape Shipwright: in-harbour code inspection, fitting out, @planks annotations, and @captain scenario skeletons. Use for harbour work only.
Command Claude Code
Audit Shipshape installation integrity: completeness, freshness, and coherence across channels and scopes. Read-only.
Command Claude Code
Report Shipshape deck state derived from repository signals. Read-only.
Hook Claude Code
One of 4 in hooks.json
Runs when a session starts on startup and clear, executing session-orient.sh, rigging-validate.sh and update-nudge.sh (3 commands). From dmytri/shipshape.
Hook Claude Code
One of 4 in hooks.json
Runs before the agent uses a tool for Edit, Write, MultiEdit, NotebookEdit, Bash, Monitor, Read, Grep, Glob and Task tool calls, executing write-custody.sh, bash-custody.sh, captain-notes-guard.sh and dispatch-guard.sh (4 commands). From dmytri/shipshape.
Hook Claude Code
One of 4 in hooks.json
Runs after a tool call finishes for Edit, Write, MultiEdit, Bash and Monitor tool calls, executing feature-quality.sh and captain-reset-nudge.sh (2 commands). From dmytri/shipshape.
Hook Claude Code
One of 4 in hooks.json
Runs when a subagent finishes, executing planks-check.sh and background-custody.sh (2 commands). From dmytri/shipshape.
Cursor rule Cursor
Boatswain hygiene, recheck, and local commit checklist.
Cursor rule Cursor
Captain custody checklist for specs, dispatch, and outbound.
Cursor rule Cursor
Crew Mate production-change checklist for one failing target.
Cursor rule Cursor
Quartermaster verification and dispatch checklist.
Cursor rule Cursor
Shipshape Articles of Agreement checklist for all roles.
Cursor rule Cursor
Shipwright harbour inspection and fitting-out checklist.
Skill Claude CodeCodex
Use this skill to run the Shipshape Boatswain role: hygiene, verification recheck, and local commit custody. Called by Captain for a pre-clean scan on a dirty deck and by QM after Crew finishes for commit custody.
Skill Claude CodeCodex
Use this skill to run the Shipshape Captain role: human-facing discovery, durable specs and assets, Captain-only notes, blocker resolution, and outbound decisions. Default entry for new product intent and any user conversation.
Skill Claude CodeCodex
Use this skill to run a Shipshape Crew Mate for one failing verification target, making the smallest required production change. Dispatched by QM with a target and failure evidence.
Skill Claude CodeCodex
Use this skill to run the Shipshape Quartermaster role: fresh-context verification and executable coverage from durable repository artifacts only. Run after Captain, in clear context.
Skill Claude CodeCodex
Use this skill to understand the Shipshape workflow, shared Articles of Agreement, and select the correct role skill: /captain, /qm, /crew, /boatswain, or /shipwright. Entry point when no role is active or the right role is unclear.
Skill Claude CodeCodex
Use this skill to run the Shipshape Shipwright role: in-harbour code inspection. Discovers existing behaviour and policy violations from production code, writes @captain-tagged scenario skeletons and @planks annotations for Captain review. Run for fitting out, onboarding an existing codebase, and between releases.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: