Shipshape

Shipshape checks Lucas's engineering practices across personal and organization repositories, including private repositories. A GitHub App reads repositories; the dashboard and MCP show stored evidence as pass, fail, unknown, or not_applicable. Only the configured owner can sign in.

Connect

codex mcp add shipshape \
  --url https://shipshape-mcp.aranlucas.workers.dev/mcp \
  --oauth-client-registration auto

The MCP tools are practices_overview, repo_practices, and practice_detail. The dashboard and MCP use central Auth. Connect GitHub on its account page before signing in. See authentication setup and migration for the resource, scope, owner gate, and client reconnection requirements.

Related MCP server: ProofScope

Practices

Built-in practices ship from catalog-seed/practices/. The private aranlucas/practices repository supplies overrides, custom practices, and disabled markers. Catalog setup explains how to edit or reset them without blocking future built-in updates.

Each practice's instructions.md contains remediation guidance and check limits. The coverage gaps explain where a passing result still needs review. The Worker never executes repository code or writes to evaluated repositories; dashboard edits write only to the allowlisted catalog repository.

Develop

pnpm install --frozen-lockfile
cp .dev.vars.example .dev.vars
pnpm types
pnpm check

For dashboard work without credentials, run pnpm ui:dev and open http://localhost:5200/app/. It uses fixture data.

For the full Worker, follow local setup, including development Auth configuration and local migrations. Run pnpm ui:build before pnpm dev so the Worker can serve the dashboard bundle.

Deployment setup covers production releases, migration safety, and Workers Builds.

• Architecture and consistency boundaries

• Contributing

• Security and private reporting

• Product roadmap