amit-mizrachi

Claude Amit Mizrachi — Git skill for Claude Code

Git community

Claude Code skills for unattended work: hand a session off (next-prompt), take a feature through the night as one PR (night-sprint), chart a wayfinder map (mywayfinder).

How to install Claude Amit Mizrachi

This entry records only its repository, not the path inside it, so there is no exact command to give. Open amit-mizrachi/claude-amit-mizrachi and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Claude Amit Mizrachi does

Claude Code skills for unattended work: hand a session off (next-prompt), take a feature through the night as one PR (night-sprint), chart a wayfinder map (mywayfinder). Plus a sliding 8h macOS caffeinate hook.

Alternatives in Git

Fresh Start — The original nirholas/claude-code before DMCA and take down 6.2k ★
Diri — Native macOS orchestrator for coding agents — run Claude Code, Codex, Cursor, Gemini and shells in parallel ac 272 ★
Cetus — One macOS app for Claude Code, Codex, and every agent runtime you use — scheduled runs, global hotkey launcher 141 ★

README

amit-mizrachi

Three [Claude Code](https://claude.com/claude-code) skills for running work you are not sitting and watching - handing a session off, taking a feature through the night, and keeping a big effort's map legible - plus the macOS hook that stops your machine sleeping through it.

Install

/plugin marketplace add amit-mizrachi/claude-amit-mizrachi
/plugin install amit-mizrachi@amit-mizrachi

Start a new session (or `/clear`). The skills then appear as `amit-mizrachi:next-prompt`, `amit-mizrachi:night-sprint`, and `amit-mizrachi:mywayfinder`.

What's in it

`next-prompt`

Writes a self-contained continuation prompt for the next task and **launches it as a background agent**, so the work carries on in a fresh session instead of dying with this one.

The prompt is built around what a new session *cannot* recover on its own. It can read git, `CLAUDE.md`, and the codebase; it cannot read the decisions you made, the gotchas you hit, or the state that never got written down. So the template spends its words there, and the `Gotchas:` line is mandatory.

Handles a phased plan too: it generates every phase's prompt at once, then launches only the next actionable one - because Phase 2 usually cannot start until Phase 1 lands, and starting both just creates conflicting work. Say "launch them all" and it will, telling each session to take an isolated worktree.

Use it when you are low on context, wrapping up, or want to queue work you will not be around for.

`night-sprint`

Delivers a whole feature overnight as a **chain** of autonomous sessions. Ticket 01 lands and hands off to ticket 02, and so on, with exactly one session touching code at a time - all in one worktree, on one branch, landing as **one PR**. No frozen contracts, no disjoint-file rules, no merge conflicts, no integration step.

You are the conductor and you write no product code. You set the sprint up, launch the first ticket, then watch: revive what dies, fire reviews at the ch