workon

Create isolated Git worktrees for GitHub issue development.

116|56|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/Soul-Brews-Studio/arra-oracle-skills-cli --skill workon-soul-brews-studio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workon
Source: https://github.com/Soul-Brews-Studio/arra-oracle-skills-cli/tree/main/src/skills/workon
Command: npx skills add https://github.com/Soul-Brews-Studio/arra-oracle-skills-cli --skill workon-soul-brews-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often need to work on GitHub issues without contaminating the main branch and require a way to resume previously aborted worktree sessions.

Core Features & Use Cases

  • Isolated Worktree Creation: Generates a dedicated Git worktree for each issue, keeping the main branch untouched.
  • Cross-repo Issue Handling: Supports working on issues from other repositories by creating tracking issues.
  • Session Resume: Detects and restores killed worktrees, recreating the environment and loading the previous AI session.
  • Workflow Automation: Guides through issue reading, worktree setup, commit, PR creation, and notification.

Quick Start

Ask the assistant to start work on issue #435 in the current repository.

Frequently Asked Questions about workon

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

FAQPage Schema
How do I isolate GitHub issue work without contaminating the main branch?

To isolate GitHub issue work, you create a dedicated Git worktree for each issue. This keeps your main branch untouched by generating a separate working directory tied to the specific issue context.

Can I resume a killed Git worktree session if my development environment crashed?

Yes, you can resume a killed Git worktree session by detecting and restoring the previous worktree. The session resume feature recreates the environment and loads your previous AI session to continue work.

Do I need the GitHub CLI to manage issue-driven development with Git worktrees?

Yes, you need the GitHub CLI to manage issue-driven development with Git worktrees. The workflow requires Git and GitHub CLI to read issues, set up worktrees, create commits, and open pull requests.

How can I work on a GitHub issue from a different repository using a local worktree?

You can work on a GitHub issue from a different repository by creating a tracking issue in your current repository. This cross-repo handling sets up the isolated worktree using the tracking issue context.

What is the best way to automate the workflow from reading a GitHub issue to opening a pull request?

The best way to automate this workflow is using an issue-driven development process that reads the issue, sets up a Git worktree, commits changes, creates a PR, and sends a notification automatically.