Sponsor Suno AI Music arrow_forward
Plugin

Overnight Dev

Run Claude autonomously for 6-8 hours overnight using Git hooks that enforce TDD - wake up to fully tested features

Type
Plugin
GitHub stars
2.8k
License
MIT
Repo last updated
Sep 27, 2026
Version
1.29.0
Author
Intent Solutions IO

What Overnight Dev is

Overnight Dev is a plugin published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.”

A plugin is a package that bundles skills, slash commands, subagents, hooks, and MCP connectors so they install together. Plugins are plain files with a manifest at .claude-plugin/plugin.json, and they work in both Claude Code and Claude Cowork.

Installing Overnight Dev adds everything it ships in one step. Connectors inside a plugin still need to be connected separately, and hooks and subagents only run in Cowork and Claude Code, not in regular chat.

How to install Overnight Dev

Claude Code

  1. Add the repository as a plugin marketplace: claude plugin marketplace add jeremylongshore/tons-of-skills-marketplace
  2. Install the plugin: claude plugin install overnight-dev@<marketplace-name>, using the marketplace name from the repository's .claude-plugin/marketplace.json.
  3. Restart the session if the new skills or commands don't appear straight away.

Claude Cowork

  1. Open Customize → Plugins and choose Add marketplace.
  2. Enter jeremylongshore/tons-of-skills-marketplace (the owner/repo shorthand works for GitHub).
  3. Find Overnight Dev in the list, click Install, then connect any connectors it needs from its Connectors tab.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/productivity/overnight-dev/.claude-plugin/plugin.json, shared under the repository's MIT license. Read the full file on GitHub.

Go to bed. Wake up to fully tested features.

Run Claude autonomously for 6-8 hours overnight using Git hooks that enforce test-driven development. No more "should work" - only "does work."

The Problem

You write code all day. Tests fail. You debug. Repeat. Progress is slow.

What if Claude could keep working while you sleep?

The Solution

Overnight Development turns Claude into an autonomous developer using Git hooks that enforce TDD:

  • Git hooks block commits until all tests pass
  • Claude can't commit broken code - hooks enforce quality
  • Automatic iteration - debug, fix, retry until green
  • You wake up to fully tested, production-ready features

Quick Start (2 minutes)

# 1. Install the plugin
/plugin install overnight-dev@claude-code-plugins-plus

# 2. Setup in your project
/overnight-setup

# 3. Start coding
# Every commit now requires passing tests!

That's it. Hooks are installed. Quality is enforced. Let Claude work overnight.

How It Works

Traditional Development

Write code → Hope it works → Find bugs later → Repeat
 Slow, error-prone, stressful

Overnight Development

Write test → Write code → Hooks enforce tests → Commit only when green
 Fast, reliable, autonomous

The Magic: Git Hooks

Pre-commit hook:

# Runs before EVERY commit
1. Lint your code
2. Run your tests
3. Check coverage
4. If anything fails → Commit blocked
5. Claude sees the error → Fixes it → Tries again

Commit-msg hook:

# Ensures quality commit messages
- Enforces conventional commits format
- feat: fix: docs: test: etc.
- Makes git history readable

The Result

Claude can't commit until all tests pass. So it keeps working until they do. Overnight. While you sleep.

Real-World Example

9 PM: Start overnight session

/overnight-setup
# Task: "Build JWT authentication with 90% test coverage"

What Claude does overnight:

  1. 10:15 PM - Write failing auth tests (TDD)
  2. 10:45 PM - Implement JWT signin (tests still failing)
  3. 11:30 PM - Debug token generation (commit blocked, keeps trying)
  4. 12:15 AM - Tests passing! Commit succeeds
  5. 1:00 AM - Add middleware (write tests first)
  6. 2:30 AM - Integration tests (debugging edge cases)
  7. 4:00 AM - All tests green (Coverage: 94%)
  8. 5:30 AM - Add docs, refactor, still green
  9. 7:00 AM - Session complete

7 AM: You wake up to:

  • 47 passing tests (0 failing)
  • 94% test coverage
  • Clean conventional commit history
  • Fully documented JWT authentication
  • Production-ready code

Time saved: 6-8 hours of your life

Features

Test-Driven Development Enforcement

Git hooks force TDD:

  • Write tests first
  • Implementation after
  • Commit only when green
  • No shortcuts, no broken code

Autonomous Debugging

When tests fail:

  1. Claude reads the error
  2. Analyzes the problem
  3. Forms a hypothesis
  4. Makes a fix
  5. Tries to commit again
  6. Repeat until green

You never have to intervene. Just check progress in the morning.

Progress Tracking

Watch overnight sessions in real-time:

# View the log
cat .overnight-dev-log.txt
[22:15]  Session started: JWT Authentication
[22:20]  Tests: 12/12 passing
[23:10]  Tests: 18/18 passing - Auth routes done
[00:30]  Tests: 24/24 passing - Middleware complete
[02:15]  Tests: 35/35 passing - Integration tests done
[04:00]  Tests: 47/47 passing - Coverage 94%
[06:45]  SESSION COMPLETE

️ Flexible Configuration

Works with any test framework:

Node.js:

{
  "testCommand": "npm test",
  "lintCommand": "npm run lint"
}

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Overnight Dev?

Overnight Dev is a plugin for Claude Code and Claude Cowork from the jeremylongshore/tons-of-skills-marketplace repository on GitHub. Run Claude autonomously for 6-8 hours overnight using Git hooks that enforce TDD - wake up to fully tested features

How do I install Overnight Dev in Claude Code?

Add the repository as a plugin marketplace: claude plugin marketplace add jeremylongshore/tons-of-skills-marketplace Install the plugin: claude plugin install overnight-dev@<marketplace-name>, using the marketplace name from the repository's .claude-plugin/marketplace.json. Restart the session if the new skills or commands don't appear straight away.

Can I use Overnight Dev in Claude Cowork?

Open Customize → Plugins and choose Add marketplace. Enter jeremylongshore/tons-of-skills-marketplace (the owner/repo shorthand works for GitHub). Find Overnight Dev in the list, click Install, then connect any connectors it needs from its Connectors tab.

Is Overnight Dev safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.