GitHub Plugin for Claude Code
GitHub automation plugin for CI/CD, pull requests, and code review workflows.
Features
- 🔍 Auto-detect CI context - Works with PRs, feature branches, and main/master
- 📊 Intelligent log parsing - Identifies lint, test, type, and build errors
- 🔧 Automated fixes - Applies targeted fixes for common CI failures
- 🛡️ Safety checks - Warns about main branch changes and uncommitted work
- 🎯 Specialized agents - Dedicated agents for log analysis and error fixing
- 📝 PR creation - Generate well-formatted pull requests from GitHub issues
- 💬 PR comment resolution - Interactive or autonomous review comment resolution
- 🤖 AI confidence scoring - Smart prioritization of review comments (0-100 score)
- 🔄 Rollback safety - Auto-stash changes in autonomous mode for easy undo
Installation
-
Copy this plugin to your Claude Code plugins directory:
cp -r github-plugin ~/.claude/plugins/
-
Install dependencies:
cd ~/.claude/plugins/github-plugin
bun install
-
Restart Claude Code to load the plugin
Prerequisites
- GitHub CLI (
gh) installed and authenticated
- Bun for TypeScript runtime
- Python projects: uv for package management
- TypeScript projects: Bun already installed
Commands
/fix-ci
Auto-detect, analyze, and fix CI/CD failures.
Usage:
/fix-ci # Fix CI on current branch
/fix-ci 123 # Fix CI for PR #123
/fix-ci https://... # Fix CI for PR URL
What it does:
- Detects context: Identifies whether you're on a PR, feature branch, or main branch
- Fetches logs: Downloads failed CI job logs using GitHub CLI
- Analyzes errors: Uses
ci-log-analyzer agent to parse logs and identify:
- Lint/format errors (Ruff, ESLint)
- Test failures (pytest, jest)
- Type errors (mypy, TypeScript)
- Build errors (syntax, imports)
- Applies fixes: Uses
ci-error-fixer agent to automatically fix issues
- Reports results: Shows diffs and completion summary
Safety checks:
- Warns when operating on main/master branch
- Alerts about uncommitted changes
- Flags unclear fixes for manual review
- Asks about priorities when multiple failure types exist
/create-pr
Create GitHub Pull Request with proper formatting and SDLC best practices.
Usage:
/create-pr <issue_number> # Basic PR from issue
/create-pr <issue_number> path/to/plan.md # PR with implementation plan
What it does:
- Fetches issue details: Uses
gh issue view to get issue info
- Generates PR title: Format:
<issue_type>: #<issue_number> - <issue_title>
- Examples:
feat: #123 - Add user authentication, bug: #456 - Fix login error
- Creates PR body with SDLC best practices:
- Summary: Explains the "why" and business context
- Review Focus: Highlights architectural decisions, gotchas, and file review order
- Testing Notes: Only for manual scenarios beyond CI automation
- References: Links to issue, plan, and related documentation
- Explicitly avoids redundant commit listings and generic testing documentation
- Reviews changes: Shows git diff and commit history
- Pushes and creates: Pushes branch and creates PR with
gh pr create
- Returns PR URL: Outputs only the PR URL for easy access
Example:
$ /create-pr 123 docs/implementation-plan.md
# Reviews changes, creates PR with best-practice formatting, returns:
https://github.com/user/repo/pull/456
Best Practices (Enforced in Instructions):
- ✅ Explains the "why" and business rationale
- ✅ Summarizes changes without listing every commit
- ✅ Highlights review focus: files, architecture decisions, gotchas
- ✅ Includes testing notes only for non-obvious scenarios
- ❌ No redundant commit sections (visible in PR's Commits tab)
- ❌ No generic testing documentation (CI/CD pipeline is authoritative)
- ❌ No boilerplate or placeholder sections
See research/pr-description-best-practices.md for research-backed guidance and authoritative sources.
/create-issue-from-plan
Convert implementation plans into GitHub Issues with automatic checkboxes and linking.
Usage:
/create-issue-from-plan plans/feature-name.md
What it does:
laurigates
rohitg00
trailofbits
jeremylongshore
devsforge
Jeffallan