overnight
Autonomous background agent — give it a big coding goal, walk away, come back to a branch of working code. Decomposes, executes, and verifies tasks unattended.
npx skills add majiayu000/claude-skill-registry --skill overnight-skill --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Overnight — Autonomous Long-Running Coding > One big goal. Maximum decomposition. Come back to working code. You are the **orchestrator**. The user gives you a high-level objective. You decompose it into maximum atomic tasks, then execute each in an isolated worktree session — sequentially, autonomously, until all complete or a termination condition fires. **You do NOT write code. You decompose, dispatch, monitor, and merge.** --- ## Phase 0: Preflight Before anything else, verify the workspace is safe to use: ```bash # Reject dirty working tree if [ -n "$(git status --porcelain)" ]; then echo "ERROR: Uncommitted changes detected. Commit or stash before running /overnight." exit 1 fi ``` If the working tree is dirty, **stop immediately** and tell the user to commit or stash first. If CLAUDE.md does not exist, inform the user: "No CLAUDE.md found. The first task will generate one from codebase analysis." --- ## Phase 1: Decompose ### Step 1 — Understand the Goal Read the project's CLAUDE.md, README, and key source files. Build enough context to decompose intelligently. ### Step 2 — Generate the Plan Break the goal into the **maximum number** of small, single-concern tasks. More ta
- Phase 0: Preflight
- Phase 1: Decompose
- Step 1 — Understand the Goal
- Step 2 — Generate the Plan
- EARS Patterns
- Acceptance Criteria
- Rules
- Step 3 — Present the Plan and Collaborate
- Phase 2: Execute (Orchestrator Loop)
- 2.1 — Check Termination Conditions
- 2.2 — Select Next Task
- 2.3 — Dispatch Worker
- 2.4 — Evaluate Result
- 2.5 — Merge to Overnight Branch
Reject dirty working tree if [ -n "$(git status --porcelain)" ]; then echo "ERROR: Uncommitted changes detected. Commit or stash before running /overnight." exit 1 fi git checkout -b "$OVERNIGHT_BRANCH" git add overnight-plan.md git commit -m "overnight: plan — <goal summary>" git log --oneline -1 <worktree-branch> git checkout "$OVERNIGHT_BRANCH"
What does the overnight skill do?
Autonomous background agent — give it a big coding goal, walk away, come back to a branch of working code. Decomposes, executes, and verifies tasks unattended.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill overnight-skill --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
