LaunchKit · 2026
Back to Skills

launchthatbot-git-team-ops

Role-based GitOps skill for OpenClaw agents with junior and senior operating modes.

2
254 downloads
by @launchthatbot

Setup & Installation

openclaw skills install @launchthatbot/launchthatbot-git-team-ops

Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:

npx clawhub install launchthatbot-git-team-ops

Version History

v1.0.4Feb 25, 2026 - Version note by skill developer:

- Added CODEOWNERS.md template under templates/github/ for improved repository code ownership management. - Updated SKILL.md and README.md to reference the new CODEOWNERS.md template location. - Corrected template copy path from CODEOWNERS to CODEOWNERS.md in senior onboarding documentation. - Bumped version and updated package metadata.

What This Skill Does

Configures OpenClaw agents to operate in a multi-agent Git workflow with two distinct roles: junior (branch, commit, push, open PR) and senior (review, merge, release, repo management). Each role has explicit permissions and guardrails enforced at the skill level. Supports three GitHub authentication modes: managed app, bring-your-own app, and personal access token.

Enforces role separation between agents at the skill layer rather than relying on repo-level permissions alone, reducing the risk of agents accidentally merging or force-pushing protected branches.

When to use it

  • Assigning a junior agent to open PRs without merge access
  • Having a senior agent enforce CI checks before merging
  • Bootstrapping GitHub Actions workflows into a new repo via senior onboarding
  • Running parallel agents on the same repo with different permission scopes
  • Auditing which agent made which branch or PR change

Example Workflow

Here's how your AI assistant might use this skill in practice.

INPUT

User asks: Set up a junior agent on my-org/my-repo using managed-app auth

AGENT
  1. 1Ask user for role (junior), repository (my-org/my-repo), and auth mode (managed-app)
  2. 2Call POST /github/install/start to begin managed app onboarding and retrieve short-lived token
  3. 3Call POST /github/agent/onboard to register the agent against the target repository
  4. 4Fetch latest main, create branch test/junior-onboarding-<agent-name>
  5. 5Add a verification commit under .agent-work/ and open a PR, then wait for senior review
OUTPUT

PR opened on my-org/my-repo from test/junior-onboarding-<agent-name> with onboarding verification commit, awaiting senior approval

Requirements

Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.

GitHub App ID, Installation ID, and private key PEM (byo-app mode only)GitHub personal access token (pat mode fallback only)