Analyze an epic's sub-issues and recommend batch vs sequential pipeline processing strategy. Use before starting work on an epic to determine optimal execution approach.

Semantic re-assessment of the open backlog: is each issue still **valid** against current `main`, still **worth doing**, **provable** when done, **safe** as designed, and **filed under the right epic**? Structural checks (labels, board fields, headings, `blockedBy` wiring) are `/nightgauge:issue-aud

> Category-1 (library & API reference) skill for Nightgauge' own surfaces.

Display the effective Nightgauge configuration with source annotations, showing where each value comes from (default, global, project, or environment). Use when debugging config precedence or confirming which tier supplies a value.

Auto-generate and update documentation for public APIs. Detects undocumented functions, generates JSDoc/docstrings, identifies signature changes, and suggests README updates. Use after /feature-dev or standalone on any codebase.

Monitor Claude Code documentation for new features and changes relevant to the pipeline. Use when checking for Claude Code updates or when a new CC version is released.

> **DEPRECATED — use `/nightgauge:issue-audit --epic <N>` directly.** > > This skill now delegates to `/nightgauge:issue-audit`, which subsumes > the previous epic-only validation with a universal post-creation audit > that covers every issue-creation flow (single, sub-issue, epic, batch, > cross-

File the run's discovered-work records as follow-up GitHub issues under the follow_up_filing gate. Runs after pr-merge on every issue whose run recorded discoveries; the scheduler skips it without dispatch when none were.

Cross-repository integration audit. Validates that client API calls match platform endpoints, auth flows are aligned, docs are current, and cross-repo dependencies are tracked. Run before major epic creation or after platform changes.

> Enrich a raw GitHub issue with structured sections and codebase context

Deterministic post-creation gate that verifies every issue created by issue-create (or any creation flow) has the labels, board membership, body sections, sub-issue links, blockedBy edges, cross-repo references, and knowledge scaffold the pipeline depends on. Reports findings by severity and offers --fix / --fix-interactive auto-repair using existing Go binary primitives. Use after every issue-creation flow or as a CI safety net.

Generate a model routing performance report from execution history. Shows auto-selection success rates, cost savings, under/over routing patterns, and threshold recommendations. Use when tuning model routing or reviewing what it cost.

Turn a vendor model release into reviewable work: a proposed model-registry patch, skill-overlay proposals and defect issues. Provider-neutral. Use when a provider ships a new model or publishes new model documentation.

Modernization plan generator that consumes health-check, security-audit, and test-scaffold outputs to produce a prioritized, phased roadmap. Use after running assessment skills to get an actionable improvement plan.

> Prime a GitHub repository for the Nightgauge SDLC pipeline

Re-review the current change with fresh-eyes critics that have no authoring context, each attacking it from a distinct lens (correctness, security, reuse/simplification, tests), then drive a fix loop until findings degrade to nitpicks. Use to harden a diff before opening or merging a PR, when asked for an adversarial/critical review, or from feature-dev/pr-create as an optional hardening gate.