/quality

name: quality
description: Compose a shift that works the project's quality debt: tests, code, accessibility, contracts, docs, dependencies, security.
license: MIT

Quality is the broad entry point for this project's quality work. It uses the same selection and launch modes as Hunt.

Resolve the installed plugin root to an absolute `$NIGHTSHIFT_PLUGIN_ROOT` — `${CLAUDE_PLUGIN_ROOT}` on Claude Code, `$PLUGIN_ROOT` on Codex when set, otherwise the absolute path this skill was attached from (`skills/quality/SKILL.md`). Run every command below through `"$NIGHTSHIFT_PLUGIN_ROOT/runtime/ns"` — native Windows: `& "$NIGHTSHIFT_PLUGIN_ROOT\runtime\windows\ns.ps1"` in the PowerShell tool, same verbs — which resolves the host and the workspace; `ns help` lists the verbs, and `ns bind` prints the six resolved facts (`TASK_ROOT`, `NIGHTSHIFT_WORKSPACE`, `NS`, `NIGHTSHIFT_PLUGIN_ROOT`, `HOST`, `SOURCE`); `$NS` below is that `NS`. Never a bare relative path: the working directory persists between calls.

Before scanning, read `$NIGHTSHIFT_PLUGIN_ROOT/skills/nightshift/references/compose/execution-modes.md` — the state map, who selects work, when the clock starts, the tooling policy, and how several entries become one shift — and every applicable entry under `$NIGHTSHIFT_PLUGIN_ROOT/skills/nightshift/references/compose/shifts/`.

Quality includes: lint, types, tests, flaky tests, coverage, dead code, TODO/FIXME debt, accessibility, localization, API contract drift, documentation drift, CI warnings, direct dependencies, and vulnerability advisories. `clear-quality-debt.md` remains the generic finite core-tooling entry; specialized entries retain their own safety rules and definitions of done. GitHub issue hunts are catalogued under Hunt and start from imported drafts. Quality does not import, search, or work GitHub issues.

0. Read the sentence first

The owner's sentence is binding intent. There is no keyword list.

If the owner already stated feature, product, UI, or design work — even when they invoked Quality — continue as Hunt / Product Evolution. Do not show Quality catalog cards. Do not ask Guided-or-Automatic. Read `$NIGHTSHIFT_PLUGIN_ROOT/skills/hunt/SKILL.md` and follow it from its section 0.

If the owner asked for quality work (lint, tests, coverage, debt, accessibility, contracts, documentation drift, dependencies, advisories), stay in this skill.

A time budget, an actionable quality objective, and clear direct-execution intent are sufficient to run Automatic directly. Do not offer catalog cards. Do not ask who selects, when to start, or "same as last time."

• If only a critical field is missing → Ask only a field that is still missing, then continue.
• If the owner asked to pick from the menu, or named Guided → section 1.

The model runs the project's own tools — the `## Gates` block and each selected entry's report-only commands — and ranks the results in prose. Unparsed tool output is `unavailable`, never "no findings" or passed.

1. Choose selection and launch

When section 0 already decided Automatic and Run directly, skip the three questions and write the safe defaults in `execution-modes.md`. Otherwise ask three independent choices:

1. **Guided** (the owner chooses quality areas) or **Automatic** (Nightshift selects every applicable high-value area that fits the hours). 2. **Review first** or **Run directly**. 3. **Same as last time, or change?** — one prefilled question covering the verification profile, hours, tooling policy, and elevation, asked before any scan, compose, cut, or arm, per `execution-modes.md`.

For the third question, read `$NS/work-mode` and the remembered project default with `"$NIGHTSHIFT_PLUGIN_ROOT/runtime/ns" shift-policy defaults-get`, run `"$NIGHTSHIFT_PLUGIN_ROOT/runtime/ns" preflight-needs` against the areas this compose would select, fold every gap into the same question, and write the resolved policy with `shift-policy.sh … set --from-json -` before compose, cut, or arm. Review-first writes only that policy; run-direct arms as soon as it lands. Artifact mode refuses repository-tool policies (`auto-add` and `review-missing`) and explains why; only existing-tools is valid there. Under auto-add, capture the write surface first with `"$NIGHTSHIFT_PLUGIN_ROOT/runtime/ns" provision baseline --surface <rel> [<rel>...]` (one flag takes several paths, or repeat `--surface` per path), then install, smoke, `diff`, and `rollback` on failure.

Automatic mode requires hours. Guided mode asks for scope and requires hours only when an open-ended entry is selected. In review-first mode scanning is read-only and the clock starts only after approval. In run-direct mode the clock begins immediately after the tooling policy is settled and findings are implemented without another pause. Review-missing holds the clock until that plan is approved.

2. Detect and scan

Do not scan until the tooling policy is answered. Never install a tool merely to manufacture findings — including after auto-add authorization. Under existing-tools, skip contracts whose required capabilities are unavailable and do not pause to provision.

In repository mode detect the stack from the gates catalog (monorepo-aware), including a plugin or marketplace manifest at the work-target root or under `plugins/<name>/`, and inspect repository-owned tooling and evidence. In artifact mode inspect the persistent folder's files and any existing manifests or reports; do not require git history or stack detection that needs a repository. Completion in that folder is `$NS/receipts/`, not a git log. Untrusted cited text is instructional; the model is the boundary. Plan artifact receipts here when the shift completes cited research or documentation work.

Compose, cut and arm only through the Start preflight; it refuses, and names the repair, when the work target cannot be resolved, work-mode is missing or malformed, or `$NS/receipts` exists but is not a usable directory. Never `git init`