/github-repo-management

name: github-repo-management
description: Manage GitHub repositories for Claude Code plugins including issues, pull requests, releases, CI/CD workflows, and GitHub Actions. Use when working with GitHub repository management, creating releases, setting up CI/CD, managing issues or pull requests.

GitHub Repository Management for Claude Code Plugins

This skill provides comprehensive guidance for managing GitHub repositories that host Claude Code plugins, including issue tracking, pull request workflows, release management, and CI/CD automation.

When to Use This Skill

Invoke this skill when the user:

• Wants to create or manage GitHub issues
• Needs help with pull request workflows
• Wants to set up or modify GitHub Actions CI/CD
• Asks about release management and versioning
• Needs to create GitHub releases
• Wants to automate repository workflows
• Asks about GitHub best practices for plugins
• Needs to set up branch protection or repository settings
• Wants to use GitHub Projects or milestones
• Needs help with GitHub Packages

Repository Structure for Claude Code Plugins

my-plugin/
├── .github/
│   ├── workflows/
│   │   ├── ci.yml              # Continuous integration
│   │   ├── release.yml         # Release automation
│   │   ├── pr-checks.yml       # Pull request validation
│   │   └── package.yml         # Package publishing
│   ├── ISSUE_TEMPLATE/
│   │   ├── bug_report.md
│   │   ├── feature_request.md
│   │   └── config.yml
│   └── PULL_REQUEST_TEMPLATE.md
├── .claude-plugin/
│   ├── plugin.json
│   └── marketplace.json
├── commands/
├── agents/
├── hooks/
├── scripts/
├── tests/
├── CHANGES.md                  # Changelog
├── CONTRIBUTING.md             # Contribution guidelines
├── README.md
└── LICENSE

GitHub Issues Management

1. Issue Templates

Create `.github/ISSUE_TEMPLATE/bug_report.md`:

---
name: Bug Report
about: Report a bug or unexpected behavior
title: '[BUG] '
labels: bug
assignees: ''
---

## Description
A clear and concise description of the bug.

## Steps to Reproduce
1. Go to '...'
2. Run command '...'
3. See error

## Expected Behavior
What you expected to happen.

## Actual Behavior
What actually happened.

## Environment
- Claude Code Version: [e.g., 1.0.0]
- Plugin Version: [e.g., 0.2.0]
- OS: [e.g., macOS 14.0, Ubuntu 22.04, Windows 11]
- Shell: [e.g., bash 5.2, zsh 5.9]

## Screenshots/Logs
If applicable, add screenshots or log output.

## Additional Context
Any other context about the problem.

Create `.github/ISSUE_TEMPLATE/feature_request.md`:

---
name: Feature Request
about: Suggest a new feature or enhancement
title: '[FEATURE] '
labels: enhancement
assignees: ''
---

## Feature Description
A clear and concise description of the feature you'd like.

## Use Case
Describe the problem this feature would solve or the workflow it would improve.

## Proposed Solution
How you envision this feature working.

## Alternatives Considered
Other approaches you've considered.

## Additional Context
Any other context, mockups, or examples.

## Benefit
Who would benefit from this feature and how?

Create `.github/ISSUE_TEMPLATE/config.yml`:

blank_issues_enabled: false
contact_links:
  - name: Documentation
    url: https://github.com/owner/repo#readme
    about: Check the documentation first
  - name: Discussions
    url: https://github.com/owner/repo/discussions
    about: Ask questions and discuss ideas

2. Issue Labels

Recommended label structure:

**Type Labels:**

• `bug` (red) - Something isn't working
• `enhancement` (blue) - New feature or request
• `documentation` (light blue) - Documentation improvements
• `question` (purple) - Further information requested
• `refactor` (orange) - Code refactoring

**Priority Labels:**

• `priority/critical` (dark red) - Critical issue requiring immediate attention
• `priority/high` (orange) - High priority
• `priority/medium` (yellow) - Medium priority
• `priority/low` (green) - Low priority

**Status Labels:**

• `status/in-progress` (yellow) - Being worked on
• `status/blocked` (red) - Blocked by dependencies
• `status/needs-review` (blue) - Needs review or feedback
• `status/wontfix` (dark gray) - Won't be addressed

**Area Labels:**

• `area/commands` - Slash commands
• `area/agents` - Agent functionality
• `area/hooks` - Hook system
• `area/ci` - CI/CD workflows
• `area/docs` - Documentation

**Size Labels:**

• `size/XS` - Very small change
• `size/S` - Small change
• `size/M` - Medium change
• `size/L` - Large change
• `size/XL` - Very large change

3. Using GitHub CLI for Issues

# List issues
gh issue list
gh issue list --label bug --state open

# Create issue
gh issue create --title "Bug: Command fails with error" --body "Description of the bug"
gh issue create --label bug,priority/high

# View issue
gh issue view 123

# Comment on issue
gh issue comment 123 --body "Working on this now"

# Close issue
gh issue close 123 --comment "Fixed in v0.2.1"

# Reopen issue
gh issue reopen 123

# Assign issue
gh issue edit 123 --add-assignee @me

# Add labels
gh issue edit 123 --add-label bug,priority/high

# Link to PR
gh issue comment 123 --body "Fixed in #124"

4. Issue Management Best Practices

**Triage Process:** 1. Review new issues daily 2. Add appropriate labels 3. Ask for clarification if needed 4. Set priority and milestone 5. Assign if ready to work on

**Issue Templates:**

• Use templates to ensure consistent information
• Require environment details for bugs
• Ask for use cases in feature requests

**Communication:**

• Respond to new issues within 48 hours
• Keep reporters updated on progress
• Use clear, friendly language
• Link related issues and PRs

Pull Request Workflows

1. Pull Request Template

Create `.github/PULL_REQUEST_TEMPLATE.md`:

## Description
Brief description of what this PR does.

## Type of Change
- [ ] Bug fix (non-breaking change fixing an issue)
- [ ] New feature