delivery

Diagnose and fix failing pull request checks — read the failing job logs, reproduce locally, classify the failure, apply a fix, and push until the checks go green. Use when: PR checks are red, CI is failing, a required status check is blocking merge, or a build/test/lint job fails on a PR.

Run any change to a repository outside its devbook folders, end to end — a feature or an incremental change, a bug fix, a structure or layout refactor, a new module, service, or first product increment, and the tooling, CI, scripting, and housekeeping work around them. From an ad-hoc request or an approved specification through scope discovery, a middle stage the kind selects, implementation, validation, review, and personal approval. Missing scope, acceptance criteria, reproduction steps, or architecture context is derived in Stage 0 rather than being a reason to skip the flow. DO NOT USE FOR: a devbook chapter (flow-spec), a dependency move (flow-update-packages), or creating and scaffolding a repository (flow-project).

Create, govern, and scaffold a repository — from an empty GitHub repository, or none, to a development project that builds and runs: the repository itself, its README and instructions, branch protection, templates and governance, the stack config through devbook-config:init, CI workflows, tooling, the Aspire AppHost, the project structure, and local validation. Use for a new project, and for scaffolding a project into a repository that already exists; stages the repository already has are a short check, not a reason to skip the flow.

Run any change to a devbook folder — an arc42/ chapter, decision record, debt record, or proposal; a domain/ context map or bounded context; the tech/ technology graph; design/ tokens and guidelines; the ai/ adoption record. One flow for the five folders: it derives the folder and the kind, loads the repository's own instruction files for that folder, drafts through the role the folder maps to, runs the repository's check, and closes through the documentation tier. The escalation target for a new decision, a cross-cutting redesign, a boundary question, and accepted debt. DO NOT USE FOR: the code that implements a chapter (flow-code), the dependency behind a tech/ entry (flow-update-packages), or wireframes, prototypes, and UI reviews (the ux role directly).

Run dependency and package update workflows — routine NuGet, npm, SDK, and tool updates, and framework upgrades such as a .NET Aspire version move that carry a baseline gate and new-feature adoption. Scans the graph, plans by risk with security first, updates in reversible batches, and validates runtime behavior with recorded results. Use for: update the packages, move us to the latest Aspire, bump the SDK. DO NOT USE FOR: the maintenance policy behind an update (flow-spec, as a decision record) or the tech/ chapter that records the outcome (flow-spec).

Record the delivery engine in a repository for the first time — write its pluginVersion under components.delivery in .devbook/config.json. Materializes nothing: the engine reads the config and the repository's skills by path. Refused where components.delivery already exists: run delivery:update. Use when: adopting the delivery engine. Triggers on: "delivery init", "init delivery", "install delivery", "adopt the delivery engine".

Shared Build & Test phase for code-modifying flow-* flows. Builds all projects and runs the unit and end-to-end suites first, failing fast on any red result. Invoked in order by the flow-runner agent.

Shared Personal Validation review handoff for every flow-* flow. Brings the application up, publishes the review links as clickable URLs, and says what to check by hand. Runs again on every revise round. It presents and never decides — the mandatory approval gate stays with the flow-runner. Invoked by the flow-runner agent.

Shared Validation phase for code-modifying flow-* flows. Runs after Build & Test; depth is driven by change kind (new functionality = Playwright QA with capture, bug/existing-flow change = targeted verification, dependency update = startup-only, otherwise skipped). Invoked by the flow-runner agent.

Take one pull request to merge-ready: score it against the merge-ready checklist and clear its blockers using update-pr-branch, fix-pr-checks, and pr-remarks-review. One PR per pass, worked in this session. Built to run repeatedly under /loop as a PR babysitter, picking the next PR each pass. Use when: getting your pull request ready for merge, watching CI on it, or running a scheduled pull request sweep.

Push the current branch to its remote and stop there — no pull request. Use when: pushing a branch, publishing local commits, setting the upstream for a new branch, or getting commits onto the remote so CI runs.

Create work items from active Azure Monitor SRE alerts, in whatever tracker the repository binds — GitHub issues, Jira tickets, or Markdown chapters. Use when: triaging Azure alerts, translating SRE incidents to tracked work, syncing Azure Monitor findings to the backlog, bulk item creation from an alert feed.

Start this session's work from a single tracker work item — a GitHub issue, a Jira ticket, a Backlog entry, or a Markdown chapter: fetch the items matching a filter, select one, claim it, route it to the flow-* skill that matches its type, and run that flow here. One item per run, no extra sessions. Use when: picking up an issue for implementation, pulling the next item off the backlog, or running a scheduled backlog pickup.

Move the delivery engine's record in a repository forward — release any file an earlier engine seeded, so the repository's own procedure skills are its own, and rewrite components.delivery in .devbook/config.json to the installed pluginVersion. Materializes nothing. Refused where no components.delivery stamp exists: run delivery:init. Use when: upgrading the delivery engine, or components.delivery still claims a seeded start or capture skill. Triggers on: "delivery update", "update delivery", "upgrade delivery".

Bring a pull request branch up to date with its base branch and resolve merge conflicts, then re-validate and push. Use when: a PR is behind or out of date, GitHub reports conflicts, 'this branch has conflicts that must be resolved', or a required 'branch up to date' status is blocking merge.