LaunchThatBot
LaunchThatBot
Docs/skills

skills

launchthatbot/git-ops

Role-based junior/senior GitOps skill for multi-agent coding teams.

Updated Feb 18, 2026

gitopsgithubjuniorsenior

What is LaunchThatBot

LaunchThatBot is a platform for operating OpenClaw agents with a managed control plane, security defaults, and real-time visibility while still keeping your agents on your infrastructure.

What this skill is for

launchthatbot/git-team-ops is for users who want multiple coding agents working safely in a single GitHub repository with clear role boundaries.
This skill supports:
  • junior agents for coding and PR creation
  • senior agents for review, merge, release, and repository workflow control

File Explorer

Git Team Ops Package Files

These files define role-based junior/senior GitOps behavior and ship reusable workflow templates.

Runtime path: /home/node/.openclaw/skills/launchthatbot-git-team-ops

5 files
Select a file to view content.

Instructions

  1. Install skill:
npx clawhub@latest install launchthatbot-git-team-ops
  1. During onboarding, configure:
  • Agent type: junior or senior
  • Target repository owner/name
  • Auth mode: managed app (default), bring-your-own app, or fallback PAT
  1. For senior role, bootstrap GitOps templates into the target repository:
  • .github/workflows/junior-pr-validate.yml
  • .github/workflows/senior-release-control.yml
  • .github/CODEOWNERS
  1. For junior role, create a test onboarding branch and open an initial PR to validate branch/PR permissions.
Managed app limits:
  • No-login usage is allowed by default.
  • Anonymous usage is capped at 3 active bots per source IP.
  • Authenticated LaunchThatBot users get a higher per-IP cap.

Security

  • Enforce least-privilege access and protected main.
  • Prefer short-lived GitHub App installation tokens over long-lived PATs.
  • Do not print secrets in logs or store them in repository files.
  • Keep merge/release authority in senior role only.