development-workflow

Automate Git worktree workflows for PR creation, CI monitoring, and merging.

1|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/silenvx/flow-development-program --skill development-workflow-silenvx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: development-workflow
Source: https://github.com/silenvx/flow-development-program/tree/main/examples/dekita/.claude/skills/development-workflow
Command: npx skills add https://github.com/silenvx/flow-development-program --skill development-workflow-silenvx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill codifies a repeatable development workflow using Git worktrees, PR creation, and CI monitoring to prevent mainline drift and accelerate code review and merging.

Core Features & Use Cases

  • Worktree-driven development: Use git worktree to isolate feature work from main.
  • PR orchestration: Create PRs, manage reviews, and enforce merge discipline.
  • CI monitoring: Proactively monitor CI and trigger merges or retries.

Quick Start

Create a new worktree with git worktree add --lock .worktrees/<name> -b <branch>. Run the setup script to install dependencies: .claude/scripts/setup_worktree.sh .worktrees/<name>. Move into the worktree, fetch latest main, run tests and lint, then create a PR with gh pr create.

Frequently Asked Questions about development-workflow

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

FAQPage Schema
How do I use git worktree to isolate feature branches from main?

Use git worktree to isolate feature branches by creating a locked worktree directory with `git worktree add --lock .worktrees/<name> -b <branch>`, keeping your main branch clean while working on features in separate directories.

How do I automate PR creation and CI monitoring in a git worktree workflow?

Automate PR creation and CI monitoring by running `setup_worktree.sh` for dependencies, then use `gh pr create` to open pull requests and `ci_monitor.py` to proactively track CI status and trigger merges.

What is the best way to prevent mainline drift when managing multiple feature branches?

Prevent mainline drift by using git worktree-driven development to isolate feature work, fetching latest main within the worktree, running local lint and tests, and enforcing merge discipline through coordinated PR reviews.

Does the development-workflow skill require any external dependencies or tools?

The skill operates with no external dependencies, relying only on standard git worktree commands, GitHub CLI (`gh`), and included shell scripts like `setup_worktree.sh` and `ci_monitor.py` to execute the workflow.

What steps should I follow to set up a new worktree for feature development?

Set up a new worktree by running `git worktree add --lock .worktrees/<name> -b <branch>`, executing `.claude/scripts/setup_worktree.sh` to install dependencies, then fetching latest main and running tests before creating a PR.

When should I avoid using a git worktree-based development workflow?

Avoid git worktree workflows if your project lacks CI integration or GitHub CLI support, as the skill relies on `gh pr create` and `ci_monitor.py` to orchestrate reviews, merges, and fast feedback across branches.