shipit

Show CI/CD pipeline status for current branch with job details and failure diagnostics

Cross-validate documentation and artifacts across the codebase for consistency, conflicts, and contradictions. Use when users ask to "cross-validate", "validate docs", "check documentation consistency", "audit documentation", or find conflicts/contradictions in docs. Supports automatic fixing with "validate and fix" argument. Runs parallel subagents for efficient validation across categories (domain-models, agent-system, tech-stack, architecture, cli-commands). Part of the ShipIT autonomous SDLC platform — https://github.com/jrmatherly/shipit

React Flow (@xyflow/react) for workflow visualization with custom nodes and edges. Use when building graph visualizations, creating custom workflow nodes, implementing edge labels, or controlling viewport. Triggers on ReactFlow, @xyflow/react, Handle, NodeProps, EdgeProps, useReactFlow, fitView.

Diagnose semantic-release and npm publish failures from the latest CI release job

Provides complete shadcn/ui component library patterns including installation, configuration, and implementation of accessible React components. Use when setting up shadcn/ui, installing components, building forms with React Hook Form and Zod, customizing themes with Tailwind CSS, or implementing UI patterns like buttons, dialogs, dropdowns, tables, and complex form layouts.

Use when ready to commit, push, and create a PR with CI verification. Triggers include "commit and pr", "push pr", "create pr", "ship it", or when implementation is complete and needs CI validation. Watches CI and auto-fixes failures. Part of the ShipIT autonomous SDLC platform — https://github.com/jrmatherly/shipit

Use when the user wants rapid implementation iteration without tests, builds, or commits. Triggers include "fast loop", "fast iteration", "just code", "no tests", "iterate quickly", or when the user says they have a dev server running and want to check results manually. Part of the ShipIT autonomous SDLC platform — https://github.com/jrmatherly/shipit

Validate specs and autonomously execute implementation tasks with status tracking. Use after /shipit-kit:plan when ready to start implementation. Part of the ShipIT autonomous SDLC platform — https://github.com/jrmatherly/shipit

Use after a PR has been merged to clean up. Switches to main, pulls latest, and deletes the local feature branch. Triggers include "merged", "pr merged", "cleanup branch", or after confirming a PR was merged. Part of the ShipIT autonomous SDLC platform — https://github.com/jrmatherly/shipit

Fast-track feature creation that collapses new-feature, research, and planning into a single autonomous pass. Produces all spec YAMLs (spec, research, plan, tasks, feature) in one go with minimal user interaction. Triggers include "quick feature", "fast feature", "rapid spec", or explicit /shipit-kit:new-feature-fast invocation. Part of the ShipIT autonomous SDLC platform — https://github.com/jrmatherly/shipit

Use when starting any new feature, functionality, or enhancement. Triggers include "new feature", "start developing", "add functionality", "implement X", or explicit /shipit-kit:new-feature invocation. Creates spec branch and scaffolds specification directory. Part of the ShipIT autonomous SDLC platform — https://github.com/jrmatherly/shipit

Use when a task can be worked on in isolation alongside other work. Creates a git worktree in .worktrees/ with a unique branch for parallel development. Triggers include "parallel task", "worktree", "work in isolation", or explicit /shipit-kit:parallel-task invocation. Part of the ShipIT autonomous SDLC platform — https://github.com/jrmatherly/shipit

Use after /shipit-kit:research to create implementation plan and task breakdown. Triggers include "plan", "implementation plan", "break down tasks", "create tasks", or explicit /shipit-kit:plan invocation. Part of the ShipIT autonomous SDLC platform — https://github.com/jrmatherly/shipit

Use after /shipit-kit:new-feature to analyze technical approach, evaluate libraries, document decisions. Triggers include "research", "technical analysis", "evaluate options", "which library", or explicit /shipit-kit:research invocation. Part of the ShipIT autonomous SDLC platform — https://github.com/jrmatherly/shipit

Quick feature status and "what to do next" guide. Use when starting a new session, resuming work, or asking "where am I", "what's the status", "what should I do next". Gives a zero-to-hero walkthrough of the current feature branch. Part of the ShipIT autonomous SDLC platform — https://github.com/jrmatherly/shipit

Use when creating, modifying, or reviewing web UI components. Triggers include "new component", "add component", "create UI", "build a widget", "update component", working with files in src/presentation/web/components/, or when the user asks to build any React component for the web UI. Part of the ShipIT autonomous SDLC platform — https://github.com/jrmatherly/shipit

Use when creating, modifying, or documenting TypeSpec domain models. Triggers include adding new entities, value objects, enums, extending base types, or when asked to create a "tsp model", "domain model", "entity", or work with files in the tsp/ directory. Part of the ShipIT autonomous SDLC platform — https://github.com/jrmatherly/shipit

Use when making architectural decisions, planning features, designing new components, reviewing PRs, or validating that proposed changes align with Clean Architecture principles. Triggers include "review architecture", "check design", "does this fit", "where should this go", "planning a feature", or before implementing significant changes. Part of the ShipIT autonomous SDLC platform — https://github.com/jrmatherly/shipit

Deploy parallel subagents to verify consistency across all Clean Architecture layers

Verify feature flags are consistently wired across all Clean Architecture layers (TypeSpec through presentation)

Refactor direct infrastructure imports into port interfaces with dependency injection

Orchestrate parallel subagents to update all mock implementations when a port interface changes

Analyze the blast radius of port interface changes using Serena and Code Review Graph MCP tools

Scaffold a new use case with TDD RED-GREEN-REFACTOR cycle, DI registration, and test file

Generate centralized mock factories for port interfaces, reducing duplicate mocks across 30+ test files