its-alive

Initializes a development session by stamping time, opening a session file on an orphan git branch, and presenting a project briefing.

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/mobiustripper42/jig --skill its-alive-mobiustripper42
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: its-alive
Source: https://github.com/mobiustripper42/jig/tree/main/.claude/skills/its-alive
Command: npx skills add https://github.com/mobiustripper42/jig --skill its-alive-mobiustripper42

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a coding session cold means manually reconstructing context: what branch you're on, what the last session shipped, what the project plan says to do next, and whether prior sessions left orphaned branches behind. This Skill automates that entire session-start ritual so every session begins with a consistent, recorded, context-rich briefing. ## Core Features & Use Cases - Session file management on an orphan branch: Creates a timestamped session file on a dedicated sessions orphan branch via a .sessions-worktree/ git worktree, keeping session records out of the main code history. - Orphan branch and PR scan: Cross-references remote claude/* branches against GitHub PR state to detect abandoned work that has no shipping path, without false-alarming on squash-merged branches. - Context restoration and briefing: Reads the previous closed session's task blocks, next steps, and gotchas, greps the project plan for priorities, checks template drift and permission policy, then presents a briefing with a task recommendation and waits for confirmation. - Use Case: A developer opens Claude Code on a project and runs the session-start ritual; the Skill detects a leftover branch with commits but no PR, surfaces it for a decision, loads last session's next steps, and recommends the next planned task before any work begins. ## Quick Start Run the its-alive skill at the start of a Claude Code session to stamp the session, load prior context, and get a briefing with a recommended task.

Frequently Asked Questions about its-alive

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

FAQPage Schema
How do I track Claude Code sessions across multiple branches?

Use an orphan git branch checked out via a git worktree to store one markdown file per session. Each file records the session number, branch, start time, transcript path, and status, keeping session history independent of code branches.

How to detect orphaned git branches after squash merges?

Cross-reference branches that have commits not on main against GitHub PR state using gh pr list. A squash-merged branch's original commits never land on main, so only flag branches whose most recent PR is missing entirely or was closed without merging.

Can multiple Claude Code sessions run concurrently in one repo?

Yes, but each concurrent session needs its own linked worktree created before launching, using git worktree add with a new task branch. The session-start skill detects open session files and asks whether they are live or stale.

Why does git worktree detection fail with -d test?

In a linked worktree, .git is a file containing a gitdir pointer, not a directory, so -d reports missing. Use -e instead, which matches both files and directories, to correctly detect an existing worktree.

What are the limitations of session-start automation?

The skill cannot create a code worktree mid-session because the harness pins the working directory at launch. It also skips PR-state checks when both gh and the GitHub MCP tool are unavailable, reporting branches without assuming orphan status.