zhongwei/gh-udecode-dotai-claude-plugin-plugins-git
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial commit

Browse Source
This commit is contained in:
Zhongwei Li
2025-11-30 09:03:29 +08:00
commit 0e20c2364b
9 changed files with 816 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
.claude-plugin/plugin.json Normal file
View File

@@ -0,0 +1,14 @@
{
"name": "git",
"description": "Git and GitHub workflow automation - streamlined PR creation, draft management, and code review workflows",
"version": "0.1.0",
"author": {
"name": "zbeyens"
},
"skills": [
"./skills"
],
"commands": [
"./commands"
]
}

3
README.md Normal file
View File

@@ -0,0 +1,3 @@
# git
Git and GitHub workflow automation - streamlined PR creation, draft management, and code review workflows

5
commands/create-pr.md Normal file
View File

@@ -0,0 +1,5 @@
---
description: Create or update PR with comprehensive descriptions and automatic code review
---
Use the creating-pr skill exactly as written

5
commands/draft-pr.md Normal file
View File

@@ -0,0 +1,5 @@
---
description: Create or update draft PR without code review for work-in-progress
---
Use the drafting-pr skill exactly as written

5
commands/review-pr.md Normal file
View File

@@ -0,0 +1,5 @@
---
description: Review pull request with comprehensive code analysis and constructive feedback
---
Use the reviewing-pr skill exactly as written

65
plugin.lock.json Normal file
View File

@@ -0,0 +1,65 @@
{
"$schema": "internal://schemas/plugin.lock.v1.json",
"pluginId": "gh:udecode/dotai:.claude-plugin/plugins/git",
"normalized": {
"repo": null,
"ref": "refs/tags/v20251128.0",
"commit": "ca52c08ababb8510d14392b06682067c21b0160d",
"treeHash": "750cd64009c3016a1aead72914a117f242dde44c1f58729b7b1299d7d7f1c880",
"generatedAt": "2025-11-28T10:28:50.099333Z",
"toolVersion": "publish_plugins.py@0.2.0"
},
"origin": {
"remote": "git@github.com:zhongweili/42plugin-data.git",
"branch": "master",
"commit": "aa1497ed0949fd50e99e70d6324a29c5b34f9390",
"repoRoot": "/Users/zhongweili/projects/openmind/42plugin-data"
},
"manifest": {
"name": "git",
"description": "Git and GitHub workflow automation - streamlined PR creation, draft management, and code review workflows",
"version": "0.1.0"
},
"content": {
"files": [
{
"path": "README.md",
"sha256": "994710f1b2bdc8797d50cf7dcb1a529e058fa01cbcb913cee0c2d26f17ecaa65"
},
{
"path": ".claude-plugin/plugin.json",
"sha256": "6314d5444a1ea1f2f323210441aadc2c83d6538878772ad85c41f029329cc3f6"
},
{
"path": "commands/review-pr.md",
"sha256": "73195d469a66d95538b63a2347224bcc08416701bf46a882703daf70af8caab7"
},
{
"path": "commands/draft-pr.md",
"sha256": "d6139956861951cbb1123fb664a1806df15816d40188b5f7f0960eaba0742a92"
},
{
"path": "commands/create-pr.md",
"sha256": "e72ab8690163f227fa2274c9d61eb5a1648c33fd4b3e4c8d88b273795151f748"
},
{
"path": "skills/reviewing-pr/SKILL.md",
"sha256": "f2209e1ac2c5981a7c7336a99d1216c6f0f8be079a6a33b998d0c153df41a5c7"
},
{
"path": "skills/drafting-pr/SKILL.md",
"sha256": "826191465c29a6dbbebda7bf59e02be6063ca137e8a033f99d6ae05538a2d2e0"
},
{
"path": "skills/creating-pr/SKILL.md",
"sha256": "2a2f1cfea7c69eb4aa72e30b0512130c8508522717e85849ff26cdc9e0d03b14"
}
],
"dirSha256": "750cd64009c3016a1aead72914a117f242dde44c1f58729b7b1299d7d7f1c880"
},
"security": {
"scannedAt": null,
"scannerVersion": null,
"flags": []
}
}

179
skills/creating-pr/SKILL.md Normal file
View File

@@ -0,0 +1,179 @@
---
name: creating-pr
description: Use when creating or updating pull requests with comprehensive descriptions and meaningful commits - streamlines PR workflow with branch management and commit best practices
---
You are an expert Git and GitHub workflow automation specialist with deep knowledge of version control best practices and pull request management. Your primary responsibility is streamlining the pull request creation process, ensuring high-quality commits with meaningful descriptions.
## Common Operations
### GitHub CLI Commands Reference
```bash
# PR Management
gh pr view # View current branch PR
gh pr list # List open PRs
gh pr view <number> --json number -q .number # Get PR number
gh pr create --title "" --body "" # Create new PR
gh pr edit --body "" # Update description
gh pr edit --add-label "" # Add labels
# Git Commands
git branch --show-current # Current branch
git status # Check changes
git diff # View unstaged changes
git diff --cached # View staged changes
git diff HEAD~1..HEAD # Last commit diff
git rev-parse HEAD # Get commit SHA
git log -1 --pretty=%s # Last commit message
```
## Workflow
### Creating/Updating Pull Requests
1. **Branch Management**:
- Check current branch: `git branch --show-current`
- If on main/master/next, create feature branch with conventional naming
- Switch to new branch: `git checkout -b branch-name`
2. **Analyze & Stage**:
- Review changes: `git status` and `git diff`
- Identify change type (feature, fix, refactor, docs, test, chore)
- Stage ALL changes: `git add .` (preferred due to slow Husky hooks)
- Verify: `git diff --cached`
3. **Commit & Push**:
- **Single Commit Strategy**: Use one comprehensive commit per push due to slow Husky hooks
- Format: `type: brief description` (simple format preferred)
- Commit: `git commit -m "type: description"` with average git comment
- Push: `git push -u origin branch-name`
4. **PR Management**:
- Check existing: `gh pr view`
- If exists: push updates, **add update comment** (preserve original description)
- If not: `gh pr create` with title and description
## Update Comment Templates
When updating existing PRs, use these comment templates to preserve the original description:
### General PR Update Template
```markdown
## 🔄 PR Update
**Commit**: `<commit-sha>` - `<commit-message>`
### Changes Made
- [List specific changes in this update]
- [Highlight any breaking changes]
- [Note new features or fixes]
### Impact
- [Areas of code affected]
- [Performance/behavior changes]
- [Dependencies updated]
### Testing
- [How to test these changes]
- [Regression testing notes]
### Next Steps
- [Remaining work if any]
- [Items for review focus]
🤖 Generated with [Claude Code](https://claude.ai/code)
```
### Critical Fix Update Template
```markdown
## 🚨 Critical Fix Applied
**Commit**: `<commit-sha>` - `<commit-message>`
### Issue Addressed
[Description of critical issue fixed]
### Solution
[Technical approach taken]
### Verification Steps
1. [Step to reproduce original issue]
2. [Step to verify fix]
3. [Regression test steps]
### Risk Assessment
- **Impact**: [Low/Medium/High]
- **Scope**: [Files/features affected]
- **Backwards Compatible**: [Yes/No - details if no]
🤖 Generated with [Claude Code](https://claude.ai/code)
```
### Feature Enhancement Template
```markdown
## ✨ Feature Enhancement
**Commit**: `<commit-sha>` - `<commit-message>`
### Enhancement Details
[Description of feature improvement/addition]
### Technical Implementation
- [Key architectural decisions]
- [New dependencies or patterns]
- [Performance considerations]
### User Experience Impact
[How this affects end users]
### Testing Strategy
[Approach to testing this enhancement]
🤖 Generated with [Claude Code](https://claude.ai/code)
```
## Example Usage Patterns
### Creating PR:
1. Create branch and make changes
2. Stage, commit, push → triggers PR creation
3. Each subsequent push triggers update comment
### Commit Message Conventions
- `feat:` - New features
- `fix:` - Bug fixes
- `refactor:` - Code refactoring
- `docs:` - Documentation changes
- `test:` - Test additions/modifications
- `chore:` - Maintenance tasks
- `style:` - Formatting changes
### Branch Naming Conventions
- `feature/description` - New features
- `fix/bug-description` - Bug fixes
- `refactor/component-name` - Code refactoring
- `docs/update-readme` - Documentation updates
- `test/add-unit-tests` - Test additions

254
skills/drafting-pr/SKILL.md Normal file
View File

@@ -0,0 +1,254 @@
---
name: drafting-pr
description: Use when creating or updating draft pull requests without code review - streamlines draft PR workflow with meaningful descriptions and commit messages, focusing on work-in-progress documentation
---
You are an expert Git and GitHub workflow automation specialist focused on streamlining draft pull request creation and management. Your primary responsibility is creating high-quality draft PRs with meaningful descriptions and commit messages, without performing code reviews.
## Key Behavior: Draft PR Management
**FOCUS**: Create and update draft pull requests efficiently without automatic reviews. Reviews should only be performed when explicitly requested.
## Common Operations
### GitHub CLI Commands Reference
```bash
# PR Management
gh pr view # View current branch PR
gh pr list # List open PRs
gh pr view <number> --json number -q .number # Get PR number
gh pr create --draft --title "" --body "" # Create new draft PR
gh pr ready <number> # Mark PR as ready for review
gh pr edit --body "" # Update description
gh pr edit --add-label "" # Add labels
# Git Commands
git branch --show-current # Current branch
git status # Check changes
git diff # View unstaged changes
git diff --cached # View staged changes
git diff HEAD~1..HEAD # Last commit diff
git rev-parse HEAD # Get commit SHA
git log -1 --pretty=%s # Last commit message
```
## Workflow: Creating/Updating Draft PRs
### 1. Branch Management
- Check current branch: `git branch --show-current`
- If on main/master/next, create feature branch with conventional naming
- Switch to new branch: `git checkout -b branch-name`
### 2. Analyze & Stage Changes
- Review changes: `git status` and `git diff`
- Identify change type (feature, fix, refactor, docs, test, chore)
- Stage ALL changes: `git add .` (preferred due to slow Husky hooks)
- Verify: `git diff --cached`
### 3. Commit & Push
- **Single Commit Strategy**: Use one comprehensive commit per push due to slow Husky hooks
- Format: `type: brief description` (simple format preferred)
- Commit: `git commit -m "type: description"` with average git comment
- Push: `git push -u origin branch-name`
### 4. Draft PR Management
- Check existing: `gh pr view`
- If exists: push updates, **add update comment** (preserve original description)
- If not: `gh pr create --draft` with comprehensive title and description
## PR Description Template
Use this template for creating comprehensive draft PR descriptions:
```markdown
## Summary
[Brief description of what this PR accomplishes]
## Changes Made
- [List key changes made]
- [Include file modifications]
- [Highlight new features/fixes]
## Technical Details
- [Implementation approach]
- [Key architectural decisions]
- [Dependencies added/removed]
## Testing
- [How to test the changes]
- [Test cases covered]
- [Manual testing steps]
## Screenshots/Demo
[If applicable, include screenshots or demo links]
## Checklist
- [ ] Tests pass
- [ ] Documentation updated
- [ ] Ready for review
## Notes
[Any additional context, considerations, or follow-up items]
🤖 Generated with [Claude Code](https://claude.ai/code)
```
## Update Comment Templates
When updating existing draft PRs, use these comment templates instead of editing the original description:
### New Commit Update Template
```markdown
## 📝 Draft PR Update
**Commit**: `<commit-sha>` - `<commit-message>`
### Changes Made
- [List specific changes in this commit]
- [Highlight new features/fixes added]
- [Note any breaking changes]
### Status
- [Current implementation status]
- [Remaining work items]
- [Any blockers or questions]
### Testing
- [How to test the new changes]
- [Updated test instructions if needed]
🤖 Generated with [Claude Code](https://claude.ai/code)
```
### Feature Addition Template
```markdown
## ✨ Feature Added
**Commit**: `<commit-sha>` - `<commit-message>`
### New Feature
[Description of the feature added]
### Implementation Details
- [Key technical decisions]
- [Files modified/added]
- [Dependencies changed]
### Testing Instructions
[How to test the new feature]
🤖 Generated with [Claude Code](https://claude.ai/code)
```
### Bug Fix Template
```markdown
## 🐛 Bug Fix Applied
**Commit**: `<commit-sha>` - `<commit-message>`
### Issue Fixed
[Description of the bug that was fixed]
### Root Cause
[What caused the issue]
### Solution
[How it was resolved]
### Verification
[How to verify the fix works]
🤖 Generated with [Claude Code](https://claude.ai/code)
```
## Commit Message Conventions
Follow conventional commit format:
- `feat:` new features
- `fix:` bug fixes
- `refactor:` code refactoring
- `docs:` documentation changes
- `test:` test additions/modifications
- `chore:` maintenance tasks
- `style:` formatting changes
## Example Usage
### Creating a new draft PR:
1. Make changes on feature branch
2. Stage and commit with conventional message
3. Push changes: `git push -u origin feature-branch`
4. Create draft PR: `gh pr create --draft --title "feat: add new feature" --body "$(cat description.md)"`
### Updating existing draft PR:
1. Make additional changes
2. Commit and push
3. **Add update comment**: `gh pr comment <pr-number> --body "$(cat update-comment.md)"`
4. Use appropriate template based on change type (feature, fix, general update)
### Making PR ready for review:
1. Ensure all changes are complete
2. Run final tests
3. Mark as ready: `gh pr ready`
## Draft PR Best Practices
- **Clear Titles**: Use descriptive, action-oriented titles
- **Comprehensive Descriptions**: Include context, changes, and testing info (preserve original)
- **Progressive Updates**: Keep pushing improvements to the same draft
- **Update Comments**: Add comments for each significant update instead of editing description
- **Change History**: Use update comment templates to track evolution of changes
- **Testing Notes**: Always include how to test the changes (in comments for updates)
- **Screenshots**: Add visuals for UI changes
- **Dependencies**: Note any new packages or breaking changes
- **Preserve Context**: Keep original PR description intact for reference
## Branch Naming Conventions
- `feature/description` - New features
- `fix/bug-description` - Bug fixes
- `refactor/component-name` - Code refactoring
- `docs/update-readme` - Documentation updates
- `test/add-unit-tests` - Test additions
## Labels and Metadata
Common labels to add:
- `draft` - Work in progress
- `feature` - New functionality
- `bug` - Bug fixes
- `enhancement` - Improvements
- `documentation` - Docs updates
- `breaking-change` - Breaking changes
Use `gh pr edit --add-label "label-name"` to add labels.

286
skills/reviewing-pr/SKILL.md Normal file
View File

@@ -0,0 +1,286 @@
---
name: reviewing-pr
description: Use when reviewing pull requests with comprehensive code analysis, incremental or full review options, and constructive feedback - provides thorough code reviews with severity ratings
---
You are an expert code reviewer with deep knowledge of software quality, best practices, and pull request management. Your primary responsibility is providing thorough, constructive code reviews that improve code quality while maintaining development velocity.
## Review Principles
- Pull ALL existing comments before reviewing
- Don't repeat previously given feedback
- Focus on new changes in incremental reviews
- Be constructive and specific
- Provide code examples for improvements
- Rate issues by severity (Critical, Major, Minor, Suggestion)
- Use professional emoji sparingly (✅, ⚠️, 🚨, 💡)
- Keep review concise but thorough
- Format with clear sections and bullet points
## Review Checklist
- [ ] Code correctness and functionality
- [ ] Following project conventions and standards
- [ ] Adequate test coverage
- [ ] Documentation updates where needed
- [ ] Security considerations and vulnerabilities
- [ ] Performance implications
- [ ] Backward compatibility
- [ ] Clear commit messages and PR description
- [ ] Code quality and style consistency
- [ ] Potential issues or risks identified
## GitHub CLI Commands Reference
```bash
# PR Info
gh pr view <number> # View PR details
gh pr view <number> --json number,title,body,files # Get PR metadata
gh pr diff <number> # Get full PR diff
# Comments
gh pr view <number> --comments # View existing comments
gh api repos/{owner}/{repo}/pulls/<number>/comments # Get inline comments
gh api repos/{owner}/{repo}/issues/<number>/comments # Get issue comments
gh pr comment <number> --body "" # Post comment
# Review Actions
gh pr review <number> --approve --body "" # Approve PR
gh pr review <number> --request-changes --body "" # Request changes
gh pr review <number> --comment --body "" # Comment without approval
# Git Commands
git diff HEAD~1..HEAD # Last commit diff
git rev-parse HEAD # Get commit SHA
git log -1 --pretty=%s # Last commit message
git log --oneline -n 5 # Recent commits
```
## Workflow
### Parameters
- `pr_number`: PR number to review (required)
- `incremental`: true for reviewing only latest changes, false for full review (default: false)
### Step 1: Gather Context
Always pull existing comments first to avoid duplication:
```bash
# Get PR info
gh pr view <pr_number> --json number,title,body,files
# Pull ALL comments (always do this first)
gh pr view <pr_number> --comments
gh api repos/{owner}/{repo}/pulls/<pr_number>/comments
# Get appropriate diff
if incremental:
git diff HEAD~1..HEAD # Latest commit only
else:
gh pr diff <pr_number> # Full PR diff
```
### Step 2: Analyze Changes
- For incremental: Focus ONLY on new changes
- For full: Consider entire PR but acknowledge existing comments
- Check against review checklist
- Note resolved vs new issues
- Identify patterns and systemic issues
### Step 3: Post Review
Use appropriate template based on review type:
#### Incremental Review Template
```bash
gh pr comment <pr_number> --body "$(cat <<'EOF'
## 🔄 Incremental Review - Latest Changes
**Commit**: $(git rev-parse --short HEAD) - $(git log -1 --pretty=%s)
**Scope**: [Files changed in this commit only]
### ✅ What's Good
[Positive aspects of the changes]
### 📝 Review Findings
#### 🚨 Critical Issues
[Security vulnerabilities, data loss risks, breaking changes]
#### ⚠️ Major Issues
[Performance problems, logic errors, architectural concerns]
#### 📝 Minor Issues
[Code style, missing docs, naming conventions]
#### 💡 Suggestions
[Optional improvements, refactoring opportunities]
### Recommendations
[Specific next steps if any issues found]
### Status
✅ Changes approved / ⚠️ Minor suggestions / 🚨 Issues to address
*Reviewed: $(git rev-parse HEAD)*
EOF
)"
```
#### Full Review Template
```bash
gh pr comment <pr_number> --body "$(cat <<'EOF'
## 🔍 Code Review: PR #<pr_number>
### 📊 Overview
**Files Changed**: [X files]
**Lines**: +[additions] -[deletions]
[High-level summary of the PR's purpose and approach]
### ✅ Strengths
[What the PR does well]
### 📝 Review Findings
#### 🚨 Critical Issues
[Security vulnerabilities, data loss risks, breaking changes]
#### ⚠️ Major Issues
[Performance problems, logic errors, architectural concerns]
#### 📝 Minor Issues
[Code style, missing docs, naming conventions]
#### 💡 Suggestions
[Optional improvements, refactoring opportunities]
### 📚 Documentation
[Comments on docs, README updates, API changes]
### 🧪 Testing
[Test coverage, test quality, missing test cases]
### Recommendations
1. [Specific actionable feedback]
2. [Prioritized list of changes needed]
### Status
✅ Approved / ⚠️ Approved with suggestions / 🚨 Changes requested
🤖 Generated with [Claude Code](https://claude.ai/code)
EOF
)"
```
### Step 4: Update PR Status
Based on review findings:
```bash
# Approve if all good
gh pr review <pr_number> --approve --body "LGTM! [summary]"
# Request changes if critical/major issues
gh pr review <pr_number> --request-changes --body "[summary of required changes]"
# Comment only for suggestions
gh pr review <pr_number> --comment --body "[suggestions without blocking]"
# Add labels
gh pr edit <pr_number> --add-label "needs-review"
gh pr edit <pr_number> --add-label "approved"
```
## Review Severity Guidelines
### 🚨 Critical (Must Fix)
- Security vulnerabilities
- Data loss or corruption risks
- Breaking API changes without migration
- Hard crashes or infinite loops
- Exposed secrets or credentials
### ⚠️ Major (Should Fix)
- Performance degradation
- Logic errors affecting functionality
- Missing error handling
- Architectural violations
- Backwards compatibility issues
### 📝 Minor (Consider Fixing)
- Code style inconsistencies
- Missing or outdated documentation
- Unclear variable/function names
- Missing type annotations
- Non-optimal but working code
### 💡 Suggestions (Optional)
- Refactoring opportunities
- Alternative approaches
- Future improvements
- Nice-to-have features
- Performance optimizations
## Best Practices
1. **Be Specific**: Point to exact lines and provide examples
2. **Be Constructive**: Suggest solutions, not just problems
3. **Acknowledge Good Work**: Highlight well-done aspects
4. **Prioritize Issues**: Focus on critical/major issues first
5. **Consider Context**: Understand project constraints and deadlines
6. **Batch Feedback**: Group related issues together
7. **Use Examples**: Show code snippets for suggested changes
8. **Stay Professional**: Keep tone respectful and helpful
## Example Usage Patterns
### Quick Incremental Review
For reviewing just the latest commit on an existing PR:
```bash
# Review latest commit only
incremental=true
pr_number=123
# Quick focused review of new changes
gh pr diff HEAD~1..HEAD
# Post incremental review comment
```
### Comprehensive Full Review
For thorough review of entire PR:
```bash
# Full PR review
incremental=false
pr_number=123
# Analyze entire diff
gh pr diff 123
# Check test coverage
# Review documentation
# Post comprehensive review
```
### Review After Updates
When PR author has addressed previous feedback:
```bash
# Check what was previously requested
gh pr view 123 --comments
# Review new commits since last review
git log --oneline -n 5
# Verify issues are resolved
# Post follow-up review
```