ship-standards

Plugin ship-standards from marketplace jawad-plugins in Jawad606/standard-ship-plugins. Commands read from the repo's manifest — 19 days ago.

Skills (5)

• engineering-standards

  Default engineering standards for building features — structure, TypeScript/NestJS/Next.js/Python practices, testing strategy, security and AI-feature practices. Use whenever writing or changing code in a repo that uses ship-standards, when scaffolding a new project, or when the user asks "what's th

• init-standards

  Set up the ship-standards workflow (specs, decision logs, tests, verification, CI) in a repository. Works in two modes — adopting an EXISTING codebase without overwriting its conventions, or bootstrapping a NEW project. Use when the user runs /init-standards, says "set up standards", "add the workfl

• merge-critique

  Explain and critique a finished code change for the person who will review or merge it. Answers "why this approach?", "why does this file exist?", "why not X?", and flags weak spots honestly, with every claim backed by evidence from the repo, ticket, tests, or decision log. Use this whenever a codin

• spec

  Write a structured feature spec (goal, user stories, acceptance criteria, scope, data and API changes) in the repo's specs folder before any code is written. Use when the user runs /spec, asks to "plan a feature", "write requirements", "spec this out", or asks to build a new feature in a repo using

• verify

  Run the project's quality gates (lint, typecheck, unit/integration tests, e2e, build) using the commands recorded in .ship-standards.json, and map results back to the spec's acceptance criteria. Use when the user runs /verify, before claiming any coding task is done, before running merge-critique, o

Subagents (1)

• critique-reviewer

  Fresh-context skeptical reviewer that challenges a finished change before merge. It reads the diff, spec, and decision log, and flags any claimed reason that has no evidence. Used by the merge-critique skill; can also be invoked directly. <example> Context: The coding agent just finished a feature a

Hooks (2)

• SessionStart

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/session-start.sh"

• Stop

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/stop-check.sh"

Similar plugins