overnight-development
SolidAutomates software development overnight using Git hooks to enforce test-driven development (TDD). This skill activates when you request "overnight development", "autonomous coding", "work while I sleep", or mention TDD workflows and Git hooks. It leverages Git hooks to block commits until all tests pass, enforcing a rigorous TDD process and ensuring high-quality, production-ready code. Perfect for building features autonomously - just define the goal and let Claude work overnight while tests enforce quality.
Install
Quality Score: 96/100
Skill Content
Details
- Author
- jeremylongshore
- Repository
- jeremylongshore/claude-code-plugins-plus-skills
- Created
- 8 months ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
overnight
Autonomous, long-running loop that drives a goal to completion while the user is away. Repeats AUDIT -> FIX -> VERIFY -> COMMIT (calling the /audit skill each round) until "nothing left to do" or the user interrupts, keeping a durable backlog + journal so nothing is ever lost, scheduling its own wake-ups for true overnight cadence, and pinging the user on blockers (device unplugged, build red, a decision needed). Trigger when the user says "work overnight", "keep going until I wake up / until it's done", "loop on this", "don't stop until nothing's left", or runs /overnight.
overnight-multi-issue-implementation
Run an overnight autonomous workflow that takes a cluster of related GitHub issues (typically a P1 review-panel finding set) and ships them to merged PRs by morning. Use when: (1) the user wants 6-15 related issues closed in one autonomous run, (2) the issues split naturally into two PRs (e.g., hardening + features, or refactor + new-functionality), (3) the user is going to sleep and won't be available to merge PR1 between phases, (4) each issue has clear acceptance criteria so each task can be implemented + tested + reviewed independently. Specializes `superpowers:subagent-driven- development` for the "issues -> stacked PRs by morning" problem shape: stacks PR2 on PR1's branch (so PR2 doesn't wait for human PR1-merge mid- night), audits tracker IDs against main before claiming (concurrent sessions steal ids), runs final code-review subagent before proposing merge, and surfaces important findings as PR comments before squashing (so review trail survives). Sister plugin to `overnight-review-client- delivery` (
overnight-review-client-delivery
Run an overnight autonomous work session that produces a client delivery package the next morning, with a multi-agent review panel built in to catch factual errors before they reach the client. Use when: (1) you have client deliverables that need polishing/regenerating before a morning hand-off, (2) you want a thorough quality gate without blocking on synchronous review, (3) the work scope is bounded enough to fit in 1-3 hours of agent time, (4) you want to maximise agent throughput by running content work and review agents in parallel. Implements the Phase A (content work in foreground) / Phase B (8-agent review panel in parallel background) / Phase C (morning synthesis + user hand-off) structure validated on the a causal-impact project, including the locked-file escape hatch discipline for surgical P0 fixes, the "regenerate don't banner" rule for stale content refreshes, and parallel-agent branch hygiene to avoid silent commit drops. NOT for: synchronous code review (use ce:review or claude-code-guide inste