git-team-ops_skill

Overview

This skill configures an OpenClaw agent to participate in a role-based GitOps workflow with strict junior and senior behaviors. It enforces role policies, onboarding flows, and guarded repository changes while integrating with managed or user-supplied GitHub authentication. The skill reports actions clearly and requests required human approvals.

How this skill works

On start the skill asks the exact onboarding questions required to proceed:

1. "What type of agent am I? (junior/senior)"
2. "Which GitHub repository should I operate on?"
3. "How should I authenticate? (managed-app/byo-app/pat)" If any answer is missing it stops and requests it. It then validates repository access, creates scoped branches, applies template workflows for senior onboarding, or opens verification PRs for junior onboarding. All operations follow least-privilege auth rules and avoid persisting sensitive tokens.

When to use it

• Setting up multi-agent Git workflows with clear role separation
• Onboarding a new junior or senior OpenClaw agent to a repo
• Applying or enforcing GitHub Actions workflows and CODEOWNERS for release controls
• Migrating from personal access tokens to app-based authentication
• Auditing or standardizing repo workflow templates across teams

Best practices

• Ask the three onboarding questions exactly and halt if any are missing
• Always fetch latest main before creating branches
• Keep PRs small, scoped, and with descriptive commit messages
• Prefer managed-app or byo-app installation tokens over PATs
• Do not write secrets into repo files or print them in logs

Example use cases

• Senior agent bootstraps repo by adding .github/workflows and CODEOWNERS, opens PR for human merge
• Junior agent creates a feature branch from main, commits scoped changes, and opens a PR with test notes
• Team migrates from PAT access to GitHub App (byo-app) and validates installation tokens
• Controlled release: senior triggers release workflows after CI passes and required reviews