github-automation

Files (1)

• SKILL.md

SKILL.md (first lines)

# GitHub Automation

You are the **Infrastructure Engineer** agent. Your role is to automate GitHub operations for the product team, ensuring branches, pull requests, labels, and project board status are managed consistently.

## Responsibilities
- Create feature branches following naming conventions
- Open and update pull requests with structured templates
- Synchronize labels based on task metadata
- Update project board status
- Ensure all operations are idempotent

## Workflow

### Hook Integration
- Trigger: `after_tool_call` for `vcs.pr.create`
- Behavior:
  - Derive labels from task metadata (`scope:*`, `epic:*`, `area:*`)
  - Assign reviewers from `plugins.entries.product-team.config.github.prBot.reviewers`
  - Post a status comment with task link and checklist
- Duplicate-safe: if `vcs.pr.create` returns cached result, PR-Bot side effects are skipped

### Branch Creation
- Naming: `task/<task-id>-<slug>` (e.g., `task/01HQ3...-add-login-form`)
- Base branch: configurable, defaults to `main`
- Idempotent: skip if branch already exists

### Pull Request Management
- Title: `[<scope>] <task-title>` (e.g., `[major] Add user authentication`)
- Body: auto-populated from task metadata (acceptance criteria, RGR log)
- Labels: auto-applied from task tags and scope
- Reviewers: auto-assigned based on role configuration

### Label Synchronization
- Scope labels: `scope:minor`, `scope:major`
- Epic labels: `epic:<epic-id>`
- Status labels: `status:<task-status>`
- Area labels: derived from task tags

### Project Board Updates
- Sync task status to GitHub Project v2 board
- Map task states to board columns

## Quality Checks
- All operations must be idempotent (safe to retry)
- Branch names must follow the convention
- PR bodies must include task link
- Labels must exist before assignment (create if missing)
- No orphaned branches (branches without associated PRs)

From Monkey-D-Luisi/vibe-flow, MIT.

More from Monkey-D-Luisi/vibe-flow