dotcontext

Add a new subcommand to the dotcontext bash CLI (e.g. `dotcontext status`, `dotcontext validate`) — define the command function, route it via the case statement, and wire help and shell completion. Use when extending the CLI surface.

Add a new Claude Code slash command to the dotcontext toolkit — author the command markdown with frontmatter and wire it into the templates and docs. Use when adding a new interactive `/command` workflow that users invoke in Claude Code.

Apply a change safely across many files — refactors touching more than 5 files, library or API migrations, project-wide renames of symbols/imports/paths, or adding boilerplate to many files. Use when "do it all at once" risks context overflow or silent failures.

Reproduce a bug with a failing test before fixing it. Use when investigating a bug, working a bug report or issue, or before attempting any fix — always reproduce first. Pairs with the /fix-bug workflow.

Detect the git hosting platform (GitHub, GitLab, Bitbucket, …) before running any hosting CLI — creating PRs, viewing issues, commenting on PRs. Never assume GitHub.

Reproduce a bug with a failing test before fixing it. Use when investigating a bug, working a bug report or issue, or before attempting any fix — always reproduce first. Pairs with the /fix-bug workflow.

Keep external REST API and webhook contracts documented from a single OpenAPI source of truth (docs/openapi.yml), with generated Redoc HTML, validate/build tasks, and a CI step. Use on any change to a public route, request/response shape, auth scheme, or error contract.