prep-workspace

Verify repository state, create a feature branch, and detect unfinished work.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/asochan-ai/claude-plugins --skill prep-workspace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prep-workspace
Source: https://github.com/asochan-ai/claude-plugins/tree/main/plugins/prep-workspace/skills/prep-workspace
Command: npx skills add https://github.com/asochan-ai/claude-plugins --skill prep-workspace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the initial phase of starting new work by performing state checks, creating a dedicated branch, and surfacing unfinished work to avoid rework.

Core Features & Use Cases

  • Branch creation from origin/main with configurable prefixes to structure work.
  • Pre-start checks including git status, stash, open PRs, and pending tasks to guard against errors.
  • Kickoff-driven workflow to quickly prepare a ready-to-work state and report current status.

Quick Start

Activate the kickoff or start trigger to begin preparing your workspace.

Frequently Asked Questions about prep-workspace

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

FAQPage Schema
How do I automate git branch creation and pre-start checks for new development tasks?

Automating git branch creation and pre-start checks involves verifying repo state, creating a feature branch from origin/main, and detecting unfinished work. This workflow guards against errors by surfacing open PRs and pending tasks before development begins.

What is the best way to ensure a clean mainline before starting new feature work?

Ensuring a clean mainline requires pre-start checks on git status, stashes, and open PRs. By verifying the repository state and detecting unfinished work before branching, you prevent conflicts and avoid rework on the main codebase.

Can I configure branch naming prefixes when setting up a new git workspace?

Configurable branch prefixes are supported during workspace setup to structure work consistently. When a new development task is initiated, the feature branch is created from origin/main using your defined naming conventions.

How do I discover pending tasks and open PRs before resuming development work?

Pending tasks and open PRs are discovered through automatic pre-start checks during workspace setup. The system scans for unfinished work and reports current status and potential blockers, allowing you to resume work without missing context.

Does automated workspace setup work without manual git stash or status checks?

Automated workspace setup handles git status and stash checks automatically as part of its pre-start workflow. You do not need manual checks; the system verifies repository state and reports blockers before creating a dedicated branch.

When should I not use automated branching for task setup?

Automated branching should be avoided when your project lacks a clean mainline or requires complex branching strategies beyond feature branches. If origin/main is not the baseline, the pre-start checks and configurable prefixes may not fit your workflow.