ship-branch
Ship Branch
Workflow
- Inspect
git status --shortfirst. - Leave unrelated dirty files untouched.
- Group changes by semantic purpose and split mixed work into separate commits when needed.
- Use short scoped Conventional Commit messages that match the change.
- If the current branch is
main, create a working branch first; otherwise stay on the current branch. - Commit all intended changes before pushing.
- Push the branch to the remote.
- Open a PR into
mainwithgh pr create. - Use a Conventional Commits PR title and a reviewer-ready PR body built from repo-defaults.md.
Commit Rules
- Prefer one commit per semantic change.
- Keep commit order aligned to reviewer value:
feat,fix,test,docs,refactor,chore. - Do not stage unrelated files or use
git add .unless the whole task is one coherent change.
More from bjornmelin/dev-skills
streamdown
|
13zod-v4
Expert guidance for Zod v4 schema validation in TypeScript. Use when designing schemas, migrating from Zod 3, handling validation errors, generating JSON Schema/OpenAPI, using codecs/transforms, or integrating with React Hook Form, tRPC, Hono, or Next.js. Covers all Zod v4 APIs including top-level string formats, strictObject/looseObject, metadata, registries, branded types, and recursive schemas.
9vitest-dev
World-class Vitest QA/test engineer for TypeScript + Next.js (local + CI performance focused)
8docker-architect
SOTA Docker/Compose architecture, implementation, refactor, and security hardening. Use when working on containerization tasks such as creating or rewriting Dockerfiles, docker-compose files, buildx/bake configs, .dockerignore, and CI pipelines for build/test/scan/publish; auditing existing container setups for security, correctness, size/perf, and best practices (least privilege, non-root, minimal images, pinned base images, BuildKit secrets, healthchecks); debugging Docker build/run issues; or designing dev vs prod compose workflows across services (DB/cache/queues) with correct networking, volumes, secrets, and resource limits.
7pytest-dev
World-class pytest engineer for Python: write/refactor tests, fix flakiness, design fixtures/markers, add coverage, speed up suites (collection/runtime), and optimize CI (GitHub Actions sharding, xdist parallelism, caching). Use when asked about pytest best practices, pytest 9.x features (subtests, strict mode, TOML config), pytest plugins (xdist/cov/asyncio/mock/httpx), or test performance/CI tuning.
6notebook-ml-architect
>
5