overnight-development
/overnight-development
Automates software development overnight using git hooks to enforce test-driven Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
- Author
- jeremylongshore ↗
- Repository
- tons-of-skills-marketplace ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 8
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Automates software development overnight using git hooks to enforce test-driven Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
Original author description
Automates software development overnight using git hooks to enforce test-driven Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
How it works
- Overview
- Prerequisites
- Instructions
- Output
- Error Handling
- Examples
- Resources
SKILL.md preview
---
name: overnight-development
description: Automates software development overnight using git hooks to enforce test-driven
Use when appropriate context detected. Trigger with relevant phrases based on skill
purpose.
version: 1.30.0
allowed-tools: Read, Write, Edit, Grep, Glob, Bash(general:*), Bash(util:*)
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags:
- productivity
- testing
- git
compatibility: Designed for Claude Code
---
# Overnight Development
## Overview
This skill automates software development overnight by leveraging Git hooks to enforce test-driven development (TDD). It ensures that all code changes are fully tested and meet specified quality standards before being committed.
## Prerequisites
- Access to project files in ${CLAUDE_SKILL_DIR}/
- Required tools and dependencies installed
- Understanding of skill functionality
- Permissions for file operations
## Instructions
1. Identify skill activation trigger and context
2. Gather required inputs and parameters
3. Execute skill workflow systematically
4. Validate outputs meet requirements
5. Handle errors and edge cases appropriately
6. Provide clear results and next steps
## Output
- Primary deliverables based on skill purpose
- Status indicators and success metrics
- Generated files or configurations
- Reports and summaries as applicable
- Recommendations for follow-up actions
## Error Handling
See [`references/errors.md`](references/errors.md) for comprehensive error handling.
## Examples
See [`references/examples.md`](references/examples.md) for detailed examples.
## Resources
- Official documentation for related tools
- Best practices guides
- Example use cases and templates
- Community forums and support channels
Files in this package (8)
- SKILL.md 2 KB
- assets/README.md 1 KB
- references/README.md 1 KB
- references/errors.md 4 KB
- references/examples.md 2 KB
- references/troubleshooting.md 1 KB
- references/workflow.md 3 KB
- scripts/README.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
| HelixDevelopment/agent | 100 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version bf15e1f03eb5 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100test-driven-development-tdd-workflow
Use this skill when developing software iteratively following the strict Red-Green-Refactor development cycle. - 96test-driven-development
Use when implementing any feature or bugfix, before writing implementation code - 100test-driven-development
Drives development with tests — red-green-refactor, Prove-It Pattern for bugs, test pyramid, property-based testing. Do NOT use when no spec exists yet (use spec-driven-development first). - 100test-driven-development
Drives development with tests — red-green-refactor, Prove-It Pattern for bugs, test pyramid, property-based testing. Do NOT use when no spec exists yet (use spec-driven-development first). - 100yaml-master
Execute proactive YAML intelligence: automatically activates when working with YAML files. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose. - 100yaml-master
Execute proactive YAML intelligence: automatically activates when working with YAML files. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.