How do I install the Tools Github Integration skill?

Run npx skillmds@latest add tjboudreaux/tools-github-integration in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Tools Github Integration safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Tools Github Integration?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Tools Github Integration free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Tools Github Integration?

tjboudreaux (@tjboudreaux) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Tools Github Integration by tjboudreaux

Name: Tools Github Integration
Author: tjboudreaux

Tools Github Integration

Orchestrates the integration of multiple Git worktrees or branches into a single ephemeral preview branch. Automated strategy for merging, conflict detection, and verification of parallel development streams. ONLY applicable for projects using Git/GitHub.

tjboudreaux 5f30464 2.6 KB Updated Sep 17, 2026

File contents

Integration Orchestration

Overview

This skill provides a robust, high-frequency workflow for merging multiple active development streams (from Git worktrees or feature branches) into a disposable integration-preview branch. It is designed for fast-paced agentic environments where integration checks should happen continuously or on-demand, rather than just daily.

When to Use

Condition: The project MUST be a Git repository.
Trigger: Frequent intervals (e.g., hourly, on-demand, or after any significant agent task completion).
Goal: Rapidly verify that fast-moving parallel workstreams are compatible before they hit the main branch.

The Orchestration Workflow

1. Discovery

List Worktrees: Identify all active worktrees and their current HEAD branches. git worktree list
Filter: Exclude main, master, or maintenance branches. Focus on feature/fix branches.

2. Preparation

Fetch Latest: Ensure local repo is up to date.
Create Ephemeral Branch: Create a fresh branch from the production trunk. git checkout main && git pull git checkout -b integration-preview-YYYY-MM-DD-HHMM

3. The Merge Loop

Iterate through each discovered active branch:

Attempt Merge: git merge origin/<branch-name> --no-ff
On Success: Log success, proceed to next.
On Conflict:
- Abort: git merge --abort
- Exclude: Remove this branch from the current integration candidate list.
- Report: Note the conflict (conflicting files) for the final report.

4. Verification

Install Dependencies: Run npm install, pip install, etc., as appropriate.
Run Tests: Execute the full test suite on the combined state. npm test or pytest

5. Reporting

Generate Summary:
- ✅ Integrated: List of branches successfully merged.
- ❌ Excluded (Conflict): List of branches that failed to merge, with conflict details.
- 📊 Test Status: Pass/Fail of the combined build.
Cleanup: Offer to delete the integration-preview branch if the test fails or upon user request.

Safety Rules

NEVER resolve conflicts automatically during orchestration. If it conflicts, it is excluded.
NEVER push the integration-preview branch to production/main.
ALWAYS ensure the repo is clean (or stashed) before starting.

---name: tools-github-integrationdescription: Orchestrates the integration of multiple Git worktrees or branches into a single ephemeral preview branch. Automated strategy for merging, conflict detection, and verification of parallel development streams. ONLY applicable for projects using Git/GitHub.---# Integration Orchestration## OverviewThis skill provides a robust, high-frequency workflow for merging multiple active development streams (from Git worktrees or feature branches) into a disposable `integration-preview` branch. It is designed for fast-paced agentic environments where integration checks should happen continuously or on-demand, rather than just daily.## When to Use- **Condition:** The project **MUST** be a Git repository.- **Trigger:** Frequent intervals (e.g., hourly, on-demand, or after any significant agent task completion).- **Goal:** Rapidly verify that fast-moving parallel workstreams are compatible before they hit the main branch.## The Orchestration Workflow### 1. Discovery- **List Worktrees:** Identify all active worktrees and their current HEAD branches. `git worktree list`- **Filter:** Exclude `main`, `master`, or maintenance branches. Focus on feature/fix branches.### 2. Preparation- **Fetch Latest:** Ensure local repo is up to date.- **Create Ephemeral Branch:** Create a fresh branch from the production trunk. `git checkout main && git pull` `git checkout -b integration-preview-YYYY-MM-DD-HHMM`### 3. The Merge LoopIterate through each discovered active branch:1. **Attempt Merge:** `git merge origin/<branch-name> --no-ff`2. **On Success:** Log success, proceed to next.3. **On Conflict:** - **Abort:** `git merge --abort` - **Exclude:** Remove this branch from the current integration candidate list. - **Report:** Note the conflict (conflicting files) for the final report.### 4. Verification- **Install Dependencies:** Run `npm install`, `pip install`, etc., as appropriate.- **Run Tests:** Execute the full test suite on the combined state. `npm test` or `pytest`### 5. Reporting- **Generate Summary:** - ✅ **Integrated:** List of branches successfully merged. - ❌ **Excluded (Conflict):** List of branches that failed to merge, with conflict details. - 📊 **Test Status:** Pass/Fail of the combined build.- **Cleanup:** Offer to delete the `integration-preview` branch if the test fails or upon user request.## Safety Rules- **NEVER** resolve conflicts automatically during orchestration. If it conflicts, it is excluded.- **NEVER** push the `integration-preview` branch to production/main.- **ALWAYS** ensure the repo is clean (or stashed) before starting.

Frequently asked questions