docverse

Project-specific build/test/lint/typing commands for this repo. Read this skill at the start of any phase that runs validation (`stoker-work`, `stoker-fixup`, `stoker-rebase`).

Drive a single pre-selected task through stoker-work's TDD cycle and commit/push/PR/close it (or stuck-mark it on failure). Use when invoked from the implement-phase prompt — the host has already picked the task and checked out its branch.

The universal red/green/refactor TDD methodology building block — drives a unit of work through plan → failing test → minimal implementation → refactor → validation against this repo's project-mechanics. Use when invoked from `stoker-implement` (always delegates here for the dev cycle), from `stoker-fixup` or `stoker-rebase` when a finding or conflict warrants the full TDD discipline rather than an in-place apply-and-validate, or any time the user wants to drive a feature/bug-fix/refactor through plan → test → implement → validate.

Drive a single pre-selected task through stoker-work's TDD cycle and commit/push/PR/close it (or stuck-mark it on failure). Use when invoked from the implement-phase prompt — the host has already picked the task and checked out its branch.

The universal red/green/refactor TDD methodology building block — drives a unit of work through plan → failing test → minimal implementation → refactor → validation against this repo's project-mechanics. Use when invoked from `stoker-implement` (always delegates here for the dev cycle), from `stoker-fixup` or `stoker-rebase` when a finding or conflict warrants the full TDD discipline rather than an in-place apply-and-validate, or any time the user wants to drive a feature/bug-fix/refactor through plan → test → implement → validate.

Create or update a pull request with a Summary / Validation steps / References body, including `Closes

Apply a trusted blocking stoker-review's findings to one PR — read the latest review JSON from the PR, fix what you agree with, re-validate against this repo's project-mechanics, push, and post a follow-up comment for anything you skip. Use when invoked from the stoker fixup-phase prompt, or when the user asks to address a stoker review's findings on a PR — and you are working in a stoker-installed repo. Consumes project-mechanics (Phase 0.5 prelude) and MAY delegate to stoker-work.

Add follow-up `prd-task` issues to an existing PRD so the stoker AFK loop picks them up and appends commits to the open PR, propagating the Jira Key/URL and commenting back on Jira. Use for review-derived fix-ups on an open PR, or for ad-hoc adjust/refactor ideas that should feed back into the AFK loop instead of being done interactively — in a Rubin stoker-installed repo.

Write a Product Requirements Document seeded from a Rubin/DM Jira ticket (via the Atlassian MCP), interviewing the user and exploring the codebase, then submit it as a GitHub issue using the stoker `prd` Issue Form and comment back on Jira. Use when the user wants to write a PRD, plan a feature, or create a product requirements document — especially from a `DM-` ticket — in a Rubin stoker-installed repo.

Break a PRD GitHub issue into independently-grabbable `prd-task` issues using tracer-bullet vertical slices, applying Rubin branch naming and propagating the Jira Key/URL onto each task, then comment back on Jira. Use when the user wants to break a PRD into tasks, convert a PRD to issues, or create implementation tickets — in a Rubin stoker-installed repo.

Rebase one stale PR branch onto main with intelligent conflict resolution — replay the branch onto a freshly-fetched origin/main, resolve each conflict by understanding both sides, re-validate against this repo's project-mechanics, and leave the branch rebased and clean for the host to force-push. Use when invoked from the stoker rebase-phase prompt, or when the user asks to rebase a PR branch onto main and resolve conflicts — and you are working in a stoker-installed repo. Consumes project-mechanics (Phase 0.5 prelude) and MAY delegate to stoker-work.

Read-only PR review primitive — inspect a pull request's diff and emit a single stoker-review JSON sentinel (findings + blocking verdict) for the host to post as a GitHub Review. Use when invoked from the stoker review-phase prompt, or when the user asks to review a PR and emit the stoker review sentinel — and you are working in a stoker-installed repo. Does NOT consume project-mechanics and never modifies code.

Create or update a pull request with a Summary / Validation steps / References body, including `Closes

Apply a trusted blocking stoker-review's findings to one PR — read the latest review JSON from the PR, fix what you agree with, re-validate against this repo's project-mechanics, push, and post a follow-up comment for anything you skip. Use when invoked from the stoker fixup-phase prompt, or when the user asks to address a stoker review's findings on a PR — and you are working in a stoker-installed repo. Consumes project-mechanics (Phase 0.5 prelude) and MAY delegate to stoker-work.

Add follow-up `prd-task` issues to an existing PRD so the stoker AFK loop picks them up and appends commits to the open PR, propagating the Jira Key/URL and commenting back on Jira. Use for review-derived fix-ups on an open PR, or for ad-hoc adjust/refactor ideas that should feed back into the AFK loop instead of being done interactively — in a Rubin stoker-installed repo.

Write a Product Requirements Document seeded from a Rubin/DM Jira ticket (via the Atlassian MCP), interviewing the user and exploring the codebase, then submit it as a GitHub issue using the stoker `prd` Issue Form and comment back on Jira. Use when the user wants to write a PRD, plan a feature, or create a product requirements document — especially from a `DM-` ticket — in a Rubin stoker-installed repo.

Break a PRD GitHub issue into independently-grabbable `prd-task` issues using tracer-bullet vertical slices, applying Rubin branch naming and propagating the Jira Key/URL onto each task, then comment back on Jira. Use when the user wants to break a PRD into tasks, convert a PRD to issues, or create implementation tickets — in a Rubin stoker-installed repo.

Rebase one stale PR branch onto main with intelligent conflict resolution — replay the branch onto a freshly-fetched origin/main, resolve each conflict by understanding both sides, re-validate against this repo's project-mechanics, and leave the branch rebased and clean for the host to force-push. Use when invoked from the stoker rebase-phase prompt, or when the user asks to rebase a PR branch onto main and resolve conflicts — and you are working in a stoker-installed repo. Consumes project-mechanics (Phase 0.5 prelude) and MAY delegate to stoker-work.

Read-only PR review primitive — inspect a pull request's diff and emit a single stoker-review JSON sentinel (findings + blocking verdict) for the host to post as a GitHub Review. Use when invoked from the stoker review-phase prompt, or when the user asks to review a PR and emit the stoker review sentinel — and you are working in a stoker-installed repo. Does NOT consume project-mechanics and never modifies code.

Author a new exception class in the lsst-sqre/docverse server. Use when adding a new exception, raising a new error type, creating a new error class, or making code throw a new exception inside the Docverse FastAPI app, workers, services, or storage layer. Codifies the DocverseSlackException base, the API-facing-identifier tag/context recipe, the to_sentry() override pattern, the matching SentryEventInfo test skeleton, and the docverse-client "no safir, no sentry" boundary.