Skip to main content
skill CX Codex

github-workflow · transilienceai — Claude Code skill: branching, commits, PRs

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.

MIT 195 installs ★ 632 updated 2026-07-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add transilienceai/communitytools --skill github-workflow -a claude-code
Open on GitHub

What github-workflow 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.

What it helps with

  • 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 for the agent

  • 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

How to install github-workflow

1Skills CLI (Vercel)

npx skills add transilienceai/communitytools --skill github-workflow -a claude-code

2Manually: put the files in place

~/.claude/skills/github-workflow/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/github-workflow/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about github-workflow

How do I install github-workflow in Claude Code?

Run npx skills add transilienceai/communitytools --skill github-workflow -a claude-code, then verify the skill appears at ~/.claude/skills/github-workflow/SKILL.md.

What does github-workflow do?

It automates GitHub operations: branch creation with naming rules, commits in conventional format, pushing with -u on first push, creating and reviewing pull requests, and managing issues. The skill checks repo state before each action and enforces safety rules—no force-push to main, no secrets committed, no blind git add -A.

What do I need for github-workflow to work?

GitHub CLI (gh) must be installed and authenticated. The skill runs all commands through gh; without it, operations will fail.

Source text

SKILL.md · MIT
---
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

- **NEVER** force-push to main/master without explicit user approval
- **NEVER** commit secrets, `.env` files, or credentials
- **NEVER** use `git add -A` without reviewing what's staged
- **NEVER** skip pre-commit hooks (`--no-verify`) unless user explicitly asks
- **NEVER** amend published commits — create new commits instead
- **ALWAYS** use conventional commit format: `type(scope): description`
- **ALWAYS** link PRs to issues
- **ALWAYS** check `git status` before committing
- **ALWAYS** pull before pushing to avoid conflicts
- **ALWAYS** create branches from up-to-date main

© transilienceai · MIT · transilienceai/communitytools

Similar skills

All skills for Git and GitHub →

github-workflow by other authors comes first.

github-workflow Mindrally github-workflow — a rule set that tells your agent how to work with GitHub: pull requests, review comments, Actions workflows, issue templates and branch protection. Useful whenever the agent touches a repo. CX Codex +1 829installs create-draft-pr jnsahaj create-draft-pr is a Claude Code skill that commits changes, pushes a branch, and creates a draft PR with a structured description and optional UX context. CX Codex +1 107installs github-dev Fatih C. Akyon github-dev prepares clear commits, issues, and pull requests while assisting with code reviews and feedback resolution in your Git workflow. CX Codex ★ 1,216repo stars github-workflow-automation ruvnet github-workflow-automation automates GitHub Actions with AI agent coordination. Generates optimised pipelines, manages pull requests, analyzes failed runs, and deploys updates with risk assessment. CX Codex +1 1,300installs cyrus-setup-github cyrusagents The cyrus-setup-github skill wires up gh CLI and git so Cyrus can open branches, commits and pull requests, and optionally answer @mentions in PR comments. CX Codex +1 1,100installs github-agile jwynia github-agile diagnoses GitHub-driven agile workflow problems and walks you through feature branch development, issues and pull requests. CX Codex +1 316installs git-workflow ruvnet git-workflow is a Claude Code skill for branch management, merge conflicts, and PR coordination. It activates for complex Git work, including release branches and pull request workflows. CX Codex +1 743installs

From the same set42

The whole set →
dfir dfir — a skill for analyzing Windows event logs, network captures, and filesystem artifacts during security incident investigations. Reconstructs Active Directory attack chains and builds timelines across multiple evidence sources. CX Codex +1 202installs essential-tools essential-tools — a skill for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode that loads pentesting methodology, Burp Suite, Playwright, Nuclei, and reporting standards into the agent context. CX Codex +1 202installs coordination coordination — a skill for coordinating agents in security testing workflows. Manages executor and validator spawning, holds engagement state in a single context, and avoids delegating thinking to sub-subagents. CX Codex +1 198installs cloud-containers The cloud-containers skill checks AWS, Azure, GCP, Docker, and Kubernetes for security flaws. Use it to test a cloud target or review configuration with read-only credentials. CX Codex +1 197installs mobile-security mobile-security is a Claude Code skill that assesses Android and iOS apps against OWASP MASVS/MASTG through artifact review, runtime tests, and privacy checks. CX Codex +1 194installs system Skill for system-level security testing: Active Directory attacks, privilege escalation on Linux and Windows, exploit development. Built for penetration testers and security researchers. CX Codex +1 194installs firewall-review firewall-review is a Claude Code skill for auditing firewall configurations and producing an evidence-based report. It handles ruleset reviews, including FortiGate checks. CX Codex +1 186installs cve-risk-score The cve-risk-score skill looks up CVE records in NVD and reports CVSS score, severity, CWE, and description. It runs when a CVE ID appears in the conversation. CX Codex +1 185installs

Project sponsors

Companies that keep this analytics open