ulmentflam

Nightly — Development skill for Claude Code

Development community

Work while you sleep — a host-native autonomous coding agent that lands draft PRs by morning.

How to install Nightly

This entry records only its repository, not the path inside it, so there is no exact command to give. Open ulmentflam/nightly and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Nightly does

Work while you sleep — a host-native autonomous coding agent that lands draft PRs by morning.

Alternatives in Development

Book To Skill — Turn any technical book PDF into a Claude Code skill — ready to study, reference, and use while you work 25.9k ★
Ralph Loop — Autonomous coding loop — works through tasks, commits, repeats 14k ★
Claude Coder — Kodu is an autonomous coding agent that lives in your IDE 5.2k ★

README

Nightly

[![CI](https://github.com/ulmentflam/nightly/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/ulmentflam/nightly/actions/workflows/ci.yml) [![Latest release](https://img.shields.io/github/v/release/ulmentflam/nightly?include_prereleases&sort=semver)](https://github.com/ulmentflam/nightly/releases) [![Python 3.12+](https://img.shields.io/badge/python-3.12+-blue.svg)](https://www.python.org/downloads/release/python-3120/) [![License: MIT](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE) [![Code style: ruff](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json)](https://github.com/astral-sh/ruff)

Work while you sleep.

Nightly is a host-native autonomous coding agent that runs *inside* the coding CLI you already use — Claude Code, Codex, opencode, pi, Cursor, Antigravity, or Gemini CLI — and turns it into a self-directed, drainable session. You stop coding at 5pm, fire `/nightly`, and wake up to a stack of **draft PRs in review-ready shape**: each on its own worktree, each with its own commit history, each tied to a morning **briefing.html** that tells you what landed, what's blocked, and what needs your eyes.

Terminal session: nightly start opens a run, nightly task queues 'Add a retry budget to the auth client', a status transition moves it in-flight, and nightly next picks it with the reason 'An in-flight plan was found across runs. Finishing what's started outranks picking new work.'

That last command is the whole idea. `nightly next` doesn't just pick work — it names the rule it picked by, so an unattended run leaves a trail you can audit in the morning.

**Scope:** Nightly opens draft PRs and writes a morning briefing. A human still reviews and merges — the briefing is the review surface, and the refusal policy is what keeps the surface safe. Refused categories: destructive git, production state, external