midnite-create

Executes unblocked task themes in a worktree, opens a PR, and merges after CI passes.

Updated Sep 1, 2026
One-click install
npx skills add https://github.com/bilo-io/midnite-studio --skill midnite-create-bilo-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: midnite-create
Source: https://github.com/bilo-io/midnite-studio/tree/main/.agents/skills/midnite-create
Command: npx skills add https://github.com/bilo-io/midnite-studio --skill midnite-create-bilo-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It automates the full loop of picking planned work from a task tracker, implementing it in an isolated git worktree, and shipping it as a merged pull request without manual orchestration. ## Core Features & Use Cases - Two-pass task scanning: Reads the .midnite/tasks/_INDEX.md roll-up first, then only the candidate phase docs, to select up to 4 unblocked themes across phases. - Human-gated planning: Stops for theme selection and at least 5 upfront design decisions before writing any code, then claims the themes on main to avoid parallel conflicts. - End-to-end delivery: Builds in a .worktrees/ worktree with tests, captures Playwright before/after screenshots, opens a draft PR, drives CI green, updates trackers, squash-merges, and tears down the worktree. - Use Case: Run it with a phase hint to have an agent pick open themes, confirm design choices, and autonomously ship a tested, screenshot-documented PR for a desktop app feature. ## Quick Start Invoke the midnite-create skill with an optional phase number or task hint to select and ship the next unblocked themes as a merged PR.

Frequently Asked Questions about midnite-create

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

FAQPage Schema
How do I automate picking and shipping planned tasks as pull requests?▼

Invoke the skill with an optional phase number or task hint. It scans the task index, presents unblocked themes for selection, asks design questions, then builds, tests, and merges the work as a PR autonomously.

How does the skill avoid conflicts with parallel agent runs?▼

It claims chosen themes in the `_INDEX.md` WIP column with a commit straight to `main` before creating the worktree. It also checks for abandoned worktree scratchpads and asks whether to resume or start fresh.

Does it require human approval before writing code?▼

Yes. It stops twice: once for multi-select theme selection across up to 4 phases, and once for at least 5 upfront design decision questions. Implementation only begins after both are answered.

What testing and CI requirements must pass before merging?▼

Changes ship with Vitest unit or component tests and Playwright e2e coverage for visual changes. The pre-push gate runs typecheck, lint, and tests, and the PR must have green CI checks before squash-merging.

What happens to the worktree and task tracker after the merge?▼

Tracker files are updated on the branch so the squash-merge publishes them, then `_INDEX.md` is verified on `main`. The worktree and branch are removed, and the freed disk space is reported.