GitHub Development Skill

Structured PR code reviews, issue management, branch workflows, and release coordination for AI agents — orchestrates mcp-github tools into proven development workflows.

What This Skill Does

This skill turns raw GitHub API access into structured development workflows. The key insight: a good code review isn't just reading a diff — it's a systematic checklist applied with specific file/line references.

Workflow	Tool Calls	What It Achieves
PR Code Review	3-5	Structured review with inline comments and checklist
Issue Management	1-2	Well-formatted issues with repro steps and labels
Branch Management	2-3	Safe branch creation/cleanup with naming conventions
Release Coordination	3-4	Verified merge with CI checks and notifications
Code Search	1-2	Find code with file paths and context

Without this skill:

• Reviews are vague ("looks good") without specific line references
• Issues lack reproduction steps and proper labels
• Branches accumulate without cleanup
• Merges happen without CI verification
• No cross-system notifications (Slack, Jira)

With this skill:

• Every review comment references a specific file and line
• Security and quality patterns auto-detected in diffs
• Branch naming conventions enforced
• CI status verified before every merge
• Cross-MCP notifications (Slack, Jira, CI/CD)

Installation

# Claude Code
git clone https://github.com/zavora-ai/skill-github-development.git \
  ~/.skills/skills/github-development

# ADK-Rust
cp -r github-development /path/to/project/.skills/skills/

Requirements

Required:

• mcp-github server connected with GitHub PAT

Optional:

• mcp-slack — PR notifications and merge alerts
• mcp-jira — issue linking and status updates
• mcp-cicd — deployment coordination post-merge

Folder Structure

github-development/
├── SKILL.md                     # Main skill (loaded on trigger)
├── scripts/
│   └── analyze_diff.py          # Security/quality pattern detection in diffs
├── assets/
│   └── pr-review-report.md      # Structured review output template
├── references/
│   ├── tool-sequences.md        # Exact tool call patterns
│   ├── cross-mcp-workflows.md   # GitHub + Slack + Jira + CI/CD
│   └── examples.md              # 4 real-world scenarios with traces
├── README.md
└── LICENSE

Example

User: "Review PR #42 on the auth service"

Agent behavior:

1. Fetches PR metadata (author, CI status, merge state)
2. Gets the full diff
3. Analyzes for security/quality patterns
4. Submits structured review with inline comments

Result:

## PR #42 Review: feat(auth): add OAuth2 support
Verdict: REQUEST CHANGES (2 blocking issues)

🔒 Security: Token stored in plain text
   File: src/oauth.rs:67

⚡ Reliability: Missing HTTP timeout
   File: src/middleware.rs:23

✅ What's Good: Clean separation, good test coverage

Success Criteria

Metric	Target
Trigger rate	90% on GitHub-related queries
Review quality	Specific file:line references on every comment
Workflow completion	2-5 tool calls
Safety	Never merge with failing CI

MCP Server Compatibility

Designed for mcp-github v1.3.0+:

Capability	Tools Used
PR Review	get_pull_request, get_pr_diff, create_review
Issues	create_issue, update_issue
Branches	list_branches, create_branch, delete_branch
Merge	merge_pull_request (squash/merge/rebase)
Search	search_repos, search_code, get_file_contents

Contributors

James Karanja Maina

License

Apache-2.0

---

Part of the ADK-Rust Enterprise skills ecosystem.

Built with ❤️ by Zavora AI