all-nighter

Run an autonomous coding session with safety constraints and structured handoff.

Updated Mar 15, 2020
One-click install
npx skills add https://github.com/GameDevFox/neko --skill all-nighter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: all-nighter
Source: https://github.com/GameDevFox/neko/tree/main/claude/skills/all-nighter
Command: npx skills add https://github.com/GameDevFox/neko --skill all-nighter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces downtime when you are away by driving an end-to-end autonomous coding session that can scan the project, confirm scope, and produce a structured handoff summary when you return.

Core Features & Use Cases

  • Kickoff interview before you leave: gathers primary goal, availability window, off-limits scope, budget cap (when applicable), side-project bar, and confirms a layered plan (Primary, Backlog, Stretch).
  • Autonomous execution with strict safety rules: runs work without any user prompts during the autonomous phase, avoids remote pushes, prevents destructive git operations, honors off-limits paths, and enforces budget caps.
  • Session logging and resumable continuations: writes an ALL-NIGHTER session log with TL;DR, decisions, findings, cost ledger, and review checklist; schedules safety-net wake-ups and continues across invocations.

Quick Start

Invoke the skill explicitly with /all-nighter and answer the kickoff prompts to start an overnight autonomous coding session with an agreed plan and guardrails.

Frequently Asked Questions about all-nighter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up an autonomous coding session to run while I am away?

You set up an autonomous coding session by completing an interactive kickoff interview to define your primary goal, availability window, off-limits scope, and budget caps before the non-interactive execution phase begins safely.

What are the safety guardrails for running developer productivity automation overnight?

Developer productivity automation safety guardrails include preventing remote pushes, blocking destructive git operations, avoiding user prompts, enforcing budget caps, and restricting access to off-limits paths during execution.

Can I burn down backlog items during an autonomous coding session?

Yes, you can burn down backlog items during an autonomous coding session by confirming a layered plan during kickoff that includes Primary, Backlog, and Stretch goals alongside your main implementation objective.

How does session logging work for unattended git workflow automation?

Session logging for unattended git workflow automation writes a structured log containing a TL;DR, decisions, findings, cost ledger, and review checklist to provide an arrival handoff summary when you return.

Does autonomous coding work with local commits without pushing to remote repositories?

Yes, autonomous coding enforces atomic local commits and explicitly prohibits remote pushes to ensure all repository-wide work remains safely local and reversible during your absence.

What happens if a scheduled continuation wake-up fails during overnight automation?

Scheduled continuation wake-ups trigger session resumption across invocations by utilizing structured logs, maintaining strict safety constraints without requiring user prompts throughout the autonomous execution phase.