midnite-create-adhoc

Executes one-off ad hoc coding tasks through worktree, PR, CI, and merge workflow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It handles one-off tasks — a bug mentioned in chat, a small sketched feature, an unwritten cleanup — that don't belong to any tracked phase item, running them through the same disciplined build → PR → CI → merge pipeline without requiring a backlog or phase document. ## Core Features & Use Cases - Quick scope clarification: Asks 0–3 targeted questions only where genuinely ambiguous, then proceeds autonomously through build, test, and merge stages. - Isolated worktree workflow: Creates a git worktree under .worktrees/adhoc-<slug>, maintains a resumable SCRATCHPAD.md handover file, and tears everything down after merge. - Full delivery pipeline: Ships tests with the change, captures before/after Playwright screenshots for visual work, opens a draft PR, drives CI green, and squash-merges. - Use Case: A teammate mentions a bug in the commit graph context menu. Invoke the skill with that description, confirm the worktree option, and receive a merged PR with screenshots and a passing CI run. ## Quick Start Invoke the skill with a description of the ad hoc task you want built, such as fixing a specific bug or adding a small feature.

Frequently Asked Questions about midnite-create-adhoc

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

FAQPage Schema
How do I run a one-off coding task that isn't in the backlog?▼

Invoke the skill with a concrete description of the task. It asks up to three clarifying questions only where genuinely ambiguous, then builds, tests, opens a draft PR, drives CI green, and squash-merges autonomously.

What is the difference between midnite-create and midnite-create-adhoc?▼

midnite-create picks work from the .midnite/tasks/ phase backlog, while midnite-create-adhoc takes a task you describe up front. The ad hoc variant skips every step that assumes a phase doc exists and never touches the task tracker.

Does the skill work in a git worktree or the primary checkout?▼

It always prompts with an option sheet before any edits. The recommended option creates an isolated worktree under .worktrees/adhoc-<slug> from origin/main; the alternative works directly on a feature branch in the primary checkout.

What happens if a session dies mid-task in a worktree?▼

Each worktree keeps an untracked SCRATCHPAD.md at its root recording decisions, progress, and the next step. A new session scans existing scratchpads first and asks whether to resume that worktree or tear it down and start fresh.

What checks run before a pull request is pushed?▼

The pre-push gate runs moon run :typecheck, :lint, and :test, and nothing pushes red. Tests ship with the change using Vitest at the right layer, and visual changes get Playwright before/after screenshots embedded in the PR body.

When should I not use the ad hoc task workflow?▼

Avoid it for work that belongs to a tracked phase item in .midnite/tasks/ — use midnite-create instead. It also never claims themes in the task index or touches done.md, since ad hoc work is deliberately not phase-tracked.