Phasekit — Git skill for Claude Code

phasekit

Run a long refactor as a series of unattended agent sessions that you can actually review.

One plan, split into phases. One phase per headless run, on its own git branch, one commit per task, gates green before every commit. The runner survives usage limits, pins the conversation so your answers reach the right session, and prints what the agent is doing while it does it.

It exists because "let the agent go and see what happens" produces a diff nobody can read and a repository nobody can revert. The unit of trust here is the commit, not the session.

What it is not

It is not a framework, an orchestrator, or a way to avoid thinking about your codebase. The plan is the product; `phasekit` is the thing that presses play and refuses to let a bad run look like a good one.

Requirements

• PowerShell 7+ (Windows, macOS or Linux)
• claude on PATH (Claude Code)
• git

Platform support

Running phases, verifying, merging, waiting out usage limits, detaching and following logs work the same everywhere. Two things are the operating system's to provide, and phasekit uses whatever is there:

	Windows	macOS	Linux
Keep the machine awake during a long wait	SetThreadExecutionState	caffeinate -s	systemd-inhibit
Notify when a sequence ends or stops	sound + tray balloon	afplay + osascript	terminal bell + notify-send

Neither is required. If the mechanism is missing, phasekit says so once and carries on — a machine with no notification daemon must not take a run down, and a run that cannot prevent sleep is still a run. The terminal bell is the fallback everywhere, which is also the one that survives ssh.

`tools/resume-at-logon.ps1` and `tools/watchdog.ps1` register **Windows** Task Scheduler tasks. Elsewhere they refuse and print the launchd, systemd or cron equivalent to set up by hand.

Install

git clone https://github.com//phasekit.git