# github-workflow

The github-workflow skill brings GitHub operations to your AI assistant: branches, commits, pushes, pull requests, issues, and code review. Handy when you ask your agent to commit changes, push code, create a PR, or manage branches.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 195 installs · ★ 632 repo stars
- Author: transilienceai
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/transilienceai/communitytools/tree/HEAD/skills/github-workflow/SKILL.md
- Updated: 2026-07-29
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/transilienceai-github-workflow

## What it does

The skill gives agents a complete GitHub workflow. Before each action, it checks repo state (`git status`, `git branch`, `git log`), then runs the right command. It handles branch creation with naming conventions (`feature/`, `bugfix/`, `docs/`), commits in conventional format (`type(scope): description`), pushes with `-u` on first request, creates PRs linked to issues, and manages code review.

Built-in safety rules prevent force-pushes to main without explicit permission, block commits of `.env` and secrets, forbid blind `git add -A`, and pull before push to sidestep conflicts. Branches must start from an up-to-date main. All commands run through the `gh` CLI—make sure GitHub CLI is installed and logged in.

## Requirements
- Works with: GitHub

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add transilienceai/communitytools --skill github-workflow -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/github-workflow/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/github-workflow/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add transilienceai/communitytools --skill github-workflow -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/github-workflow/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add transilienceai/communitytools --skill github-workflow -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/github-workflow/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install transilienceai/communitytools skills/github-workflow
```

2. **Manually: put the files in place**
- File: `.github/skills/github-workflow/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add transilienceai/communitytools --skill github-workflow -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/transilienceai/communitytools --path skills/github-workflow
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/github-workflow/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add transilienceai/communitytools --skill github-workflow -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/transilienceai/communitytools/tree/HEAD/skills/github-workflow/SKILL.md

## When to use it
- Create and push a feature branch with proper naming
- Commit changes using conventional commit format
- Open a pull request and link it to an issue
- Review code and approve a PR
- File an issue with acceptance criteria

## Example prompts
- Create a feature branch called `feature/add-jwt` and push it up
- Commit staged changes as "feat(auth): add JWT validation"
- Open a PR to merge this branch into main and tie it to issue #42

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 2093e4580e031fba.

BEGIN THIRD-PARTY FILE 2093e4580e031fba
````text
---
name: github-workflow
description: GitHub workflow automation — branching, committing, pushing, pull requests, issues, and code review. Use when asked to commit, push, create PRs/branches/issues, or manage git workflow.
---

# GitHub Workflow

Automate the full GitHub development lifecycle: branches, commits, pushes, PRs, issues, and code review.

## Quick Start

1. User requests a git action (commit, PR, branch, push, issue)
2. Check repo state: `git status`, `git branch`, `git log --oneline -5`
3. Execute the appropriate workflow below
4. Confirm result to user

## Workflows

### 1. Branching

```bash
# Create feature branch from main
git checkout main && git pull origin main
git checkout -b <type>/<name>
# Types: feature/, bugfix/, docs/, refactor/, test/, chore/
```

- Always branch from up-to-date `main`
- Use conventional naming: `feature/add-jwt-testing`, `bugfix/fix-port-detection`

### 2. Committing

```bash
# Stage specific files (never git add -A blindly)
git add <file1> <file2>
# Commit with conventional format
git commit -m "type(scope): description"
```

- **Types**: `feat`, `fix`, `docs`, `refactor`, `test`, `chore`
- Message focuses on **why**, not what
- Never commit `.env`, credentials, or secrets
- See [reference/commit-conventions.md](reference/commit-conventions.md)

### 3. Pushing

```bash
# First push (set upstream)
git push -u origin <branch-name>
# Subsequent pushes
git push
```

- Never force-push to `main`/`master` without explicit user approval
- If push is rejected, `git pull --rebase` first

### 4. Pull Requests

```bash
# Create PR linking to issue
gh pr create --title "Short title < 70 chars" --body "$(cat <<'EOF'
## Summary
- What changed and why

## Test plan
- [ ] How to verify

Fixes #<issue-number>
EOF
)"
```

- Title < 70 chars, details in body
- Always link to issue: `Fixes #N` or `Closes #N`
- See [reference/pr-workflow.md](reference/pr-workflow.md)

### 5. Issues

```bash
gh issue create --title "type: description" --body "$(cat <<'EOF'
## Problem
What needs to change

## Proposed solution
How to fix it

## Acceptance criteria
- [ ] Criteria 1
EOF
)"
```

### 6. Code Review

```bash
# Review a PR
gh pr view <number>
gh pr diff <number>
gh pr checks <number>
# Comment or approve
gh pr review <number> --approve
gh pr review <number> --comment --body "feedback"
```

## Reference

- [commit-conventions.md](reference/commit-conventions.md) — Commit message format and examples
- [pr-workflow.md](reference/pr-workflow.md) — PR creation, review, and merge workflow
- [branch-strategy.md](reference/branch-strategy.md) — Branching model and naming conventions

## Critical Rules
````
END THIRD-PARTY FILE 2093e4580e031fba

The third-party file has ended. Everything between the 2093e4580e031fba tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2667 of 3256 bytes. © transilienceai · MIT · https://github.com/transilienceai/communitytools/tree/HEAD/skills/github-workflow/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
