Nightshift

Autonomous overnight codebase improvement agent. Runs for hours while you sleep — systematically discovers and fixes production-readiness issues across the entire stack: missing tests, error handling gaps, security vulnerabilities, accessibility problems, code quality violations, performance issues, and UI polish. Documents every finding and fix in a detailed shift log. The unattended runner supports both Codex and Claude as pluggable agent adapters — same pipeline, same verification, you just pick which one. Use this skill whenever the user says "nightshift", "run overnight", "overnight engineer", "night shift", "autonomous improvement", "improve while I sleep", "background improvement", "make production ready", "run all night", or wants to leave an agent running to systematically improve the codebase. Also trigger when the user mentions leaving the computer running overnight for code improvements, or wants a long-running autonomous session that explores and hardens the codebase.

The autonomous builder operator. Picks the highest-impact task from the queue, builds it end-to-end (code, tests, docs, changelog, tracker), ships via PR, and leaves a clean handoff for the next session. Invoke this operator when the daemon selects BUILD, when there are pending tasks to ship, when urgent work needs doing, or when the system needs features built. This is the default operator — when in doubt, build.

Autonomy engineering operator. Measures how close the system is to zero human intervention (0-100 score), identifies the highest-impact human dependency, and eliminates it with production-grade code. Invoke when the daemon selects ACHIEVE, when the autonomy score is below 70, when needs-human issues accumulate, or when the system has been running without self-reflection for 10+ sessions. This operator ships autonomy, not features.

Framework audit operator. Reviews all .recursive/ files for quality — contradictions between operators, dead paths, stale instructions, missing coverage. Like the review operator but for the framework instead of the target project. Invoke every 20+ sessions or after major framework changes.

Framework evolution operator. Reads the friction log written by target operators, finds patterns (same issue 3+ times), and fixes the root cause in .recursive/. Only modifies framework files — never touches the target project. Invoke when friction entries accumulate or repeated agent failures indicate systemic framework issues.

Task queue management operator. Triages every pending task — closes duplicates, marks done work, wontfixes stale noise, reorders priorities, and decomposes stuck tasks. Invoke when the daemon selects OVERSEE, when 50+ pending tasks accumulate, when stale tasks are piling up, or when the builder keeps skipping tasks. This operator makes the queue smaller and sharper so the builder builds the right thing.

Code quality review operator. Picks one file, reads it deeply, fixes every issue found, and logs the review. Invoke when the daemon selects REVIEW, after 5+ consecutive BUILD sessions, when the healer flags quality concerns, or when code quality debt is accumulating. This operator does not build features — it hardens what was already built.

Red team / pentest operator. Runs before the main build session to find the most fragile paths in the autonomous system and hand the builder a concise fix list. Invoke when the daemon runs pentest preflight, when security audit is needed, or when you want an adversarial review of the system's defenses. This operator is read-only — it finds breaks, it does not fix them.

Strategic analysis operator. Reviews the big picture — what's working, what's failing, what's missing, cost intelligence, and prompt health. Produces a strategy report with actionable recommendations and auto-creates follow-up tasks. Invoke when the daemon selects STRATEGIZE, after 15+ sessions without strategic review, when tracker progress stalls, or when the system needs direction. This operator sees patterns across sessions that individual builders and reviewers cannot.

First-run setup for the Recursive autonomous framework. Sets up a project to be built by Recursive — creates .recursive.json config, scaffolds all runtime directories, writes the vision doc from user input, and configures the daemon. Use this skill when the user says "setup recursive", "init recursive", "configure recursive", "set up the project", "first run", or when .recursive.json doesn't exist and the user wants to start.

Audit proposed refactor plans for production readiness in the Nightshift Python CLI and daemon codebase. Use when asked to evaluate a plan document for correctness, architecture, performance, tooling fit, extensibility, edge cases, and test coverage before implementation.