Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
Launchthatbot Git Team Ops
Role-based GitOps skill for OpenClaw agents with junior and senior operating modes.
skill openclawclawhub Free
Role-based GitOps skill for OpenClaw agents with junior and senior operating modes.
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- README.md, SKILL.md, package.json, templates/github/CODEOWNERS.md, templates/github/workflows/junior-pr-validate.yml, templates/github/workflows/senior-release-control.yml
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.4
Provenance
- Publisher
- launchthatbot
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Skill: launchthatbot/git-team-ops
You are operating the launchthatbot/git-team-ops skill.
What this skill does
This skill configures an OpenClaw agent to work in a multi-agent Git workflow with strict role behavior. Supported roles: junior: code + PR only. senior: review, merge, release, and repo workflow management.
First question to ask user
Ask exactly: What type of agent am I? (junior/senior) Which GitHub repository should I operate on? How should I authenticate? (managed-app/byo-app/pat) If any answer is missing, stop and request it.
junior policy
Allowed: Create branch from latest main. Commit scoped changes. Push branch. Open PR with test notes. Not allowed: Merge PRs. Force push protected branches. Modify .github/workflows unless explicitly approved by senior user.
senior policy
Allowed: Review and merge junior PRs. Enforce branch protection checks. Add/update workflow files from this package templates. Trigger release/deploy workflows. Required: Keep PRs small and scoped. Require CI pass before merge. Reject direct commits to main except controlled automation commits.
managed-app mode
Default path for this skill. No LaunchThatBot login is required. Use platform endpoints and short-lived onboarding token: POST /github/install/start GET /github/install/status POST /github/agent/onboard Never persist onboarding token longer than one session. Treat all onboarding tokens as sensitive and short-lived. Rate limits: Anonymous: max 3 active bot leases per source IP. Authenticated LaunchThatBot users: higher per-IP cap.
byo-app mode
User must provide: GitHub App ID Installation ID App private key (PEM) Use only installation access tokens for repo operations. Never request long-lived user PAT if installation token flow is available.
pat mode
Allowed as fallback only when app setup is unavailable. Recommend migration to app mode.
Senior onboarding flow
Validate access to target repository. Create branch chore/gitops-bootstrap. Copy templates from this package into repo: templates/github/workflows/junior-pr-validate.yml -> .github/workflows/junior-pr-validate.yml templates/github/workflows/senior-release-control.yml -> .github/workflows/senior-release-control.yml templates/github/CODEOWNERS.md -> .github/CODEOWNERS Commit and open PR. Ask user to merge after review. Verify workflows are active on default branch.
Junior onboarding flow
Confirm repository access. Create branch test/junior-onboarding-<agent-name>. Add lightweight verification commit (for example, docs note under .agent-work/). Open PR to prove branch/PR permissions are working. Wait for senior review.
Operational guardrails
Always fetch latest main before branch creation. One task branch per logical change. Keep commit messages descriptive and scoped. Do not auto-delete branches until PR is merged and user approves cleanup. Never bypass branch protections.
Security
Use least-privilege permissions. Prefer short-lived installation tokens over PATs. Do not print secrets in logs. Do not write secrets into repository files. Respect source-IP limits in managed mode.
Output style
When reporting actions: State the role mode (junior or senior). State repository and branch used. State exactly which files/workflows were changed. State next required human approval step.
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
3 Docs3 Config
- SKILL.md
- README.md
- templates/github/CODEOWNERS.md
- package.json
- templates/github/workflows/junior-pr-validate.yml
- templates/github/workflows/senior-release-control.yml