Git and GitHub operations for EPA. Use when cloning repos, branching, committing, opening PRs, or handling review feedback. Trigger with /epa-github-operations.
npx claudepluginhub emasoft/emasoft-plugins --plugin emasoft-programmer-agentThis skill uses the workspace's default tool permissions.
This skill provides the Emasoft Programmer Agent (EPA) with standardized procedures for all Git and GitHub operations. It covers the full lifecycle from cloning a repository, creating feature branches, committing code changes with conventional commit messages, opening pull requests via the gh CLI, and responding to EIA code review feedback. All operations use the gh CLI tool and follow the Emas...
Automates GitHub workflow: branching, committing, pushing, PRs, issues, and code review. Use when managing git operations or GitHub development lifecycle.
Guides Git operations with conventional commits, PR workflows, squash merges, branch management, and conflict resolution. Useful for version control tasks like commits, branches, and pull requests.
Uses gh CLI for GitHub PR creation, squash/rebase merges, stacked PR workflows, branching strategies, and repo automation. For PR management and merging tasks.
Share bugs, ideas, or general feedback.
This skill provides the Emasoft Programmer Agent (EPA) with standardized procedures for all Git and GitHub operations. It covers the full lifecycle from cloning a repository, creating feature branches, committing code changes with conventional commit messages, opening pull requests via the gh CLI, and responding to EIA code review feedback. All operations use the gh CLI tool and follow the Emasoft ecosystem conventions for branch naming, commit formatting, and PR descriptions. This skill is used during workflow Steps 19 (create PR), 21 (respond to review), and 22 (push fixes after rejection).
This skill provides procedures for Git and GitHub operations within the Emasoft Programmer Agent workflow. Use these operations for repository management, branching, commits, and pull request lifecycle.
gh auth status to verifygh auth status. If not authenticated, run gh auth login and follow the prompts.gh repo clone <owner>/<repo> or gh repo fork <owner>/<repo> --clone. See op-clone-repository.md for details.<type>/<issue-number>-<short-description>. Example: git checkout -b feature/123-add-user-auth main. See op-create-feature-branch.md.git commit -m "feat(scope): description". See op-commit-changes.md.git push -u origin <branch-name>.gh pr create --title "<type>(scope): description" --body "..." with a clear description linking to the relevant issue. See op-create-pull-request.md.gh pr view <number> --comments, address each comment, commit fixes, and push updates. See op-respond-to-review.md.gh pr edit <number> --add-reviewer <reviewer>. See op-update-pr-with-fixes.md.| Operation | File | When to Use |
|---|---|---|
| Clone Repository | op-clone-repository.md | Initial project setup, forking upstream repos |
| Create Feature Branch | op-create-feature-branch.md | Starting work on a new task |
Table of Contents - op-clone-repository.md:
Table of Contents - op-create-feature-branch.md:
| Operation | File | When to Use |
|---|---|---|
| Commit Changes | op-commit-changes.md | Saving progress with meaningful messages |
Table of Contents - op-commit-changes.md:
| Operation | File | When to Use |
|---|---|---|
| Create Pull Request | op-create-pull-request.md | Submitting completed task for review (Step 19) |
| Respond to Review | op-respond-to-review.md | Addressing EIA review comments (Step 21) |
| Update PR with Fixes | op-update-pr-with-fixes.md | Pushing fixes after rejection (Step 22) |
Table of Contents - op-create-pull-request.md:
Table of Contents - op-respond-to-review.md:
Table of Contents - op-update-pr-with-fixes.md:
<type>/<issue-number>-<short-description>
Examples:
feature/123-add-user-authfix/456-resolve-memory-leakrefactor/789-extract-utils<type>(<scope>): <subject>
<body>
<footer>
Types: feat, fix, docs, style, refactor, test, chore
<type>(<scope>): <short description>
Example: feat(auth): add OAuth2 login support
When this skill is applied correctly, the following artifacts are produced:
<type>/<issue-number>-<short-description> convention, pushed to the remote.# Clone the repository
gh repo clone Emasoft/svgbbox
# Create feature branch
git checkout -b feature/42-add-viewbox-parser main
# Make changes, commit with conventional format
git add src/parser.py
git commit -m "feat(parser): add viewBox attribute parsing"
# Push and create PR
git push -u origin feature/42-add-viewbox-parser
gh pr create --title "feat(parser): add viewBox attribute parsing" --body "Closes #42. Adds parsing support for the viewBox SVG attribute."
# Read the review comments on PR #15
gh pr view 15 --comments
# Address the feedback by fixing the code
git add src/parser.py tests/test_parser.py
git commit -m "fix(parser): handle missing viewBox gracefully per review"
# Push the fix and notify reviewer
git push origin feature/42-add-viewbox-parser
gh pr comment 15 --body "Addressed review feedback: added null check for missing viewBox. Ready for re-review."
# Read rejection reason
gh pr view 15 --comments
# Fix the issues identified in the review
git add src/parser.py
git commit -m "fix(parser): validate viewBox dimensions are positive numbers"
# Push fixes and update PR description
git push origin feature/42-add-viewbox-parser
gh pr edit 15 --body "Updated: Added dimension validation per reviewer feedback. Closes #42."
gh pr edit 15 --add-reviewer eia-feature-reviewer
Copy this checklist and track your progress:
| Error | Cause | Solution |
|---|---|---|
gh: command not found | gh CLI not installed | Install with brew install gh |
gh auth login required | Not authenticated | Run gh auth login |
Permission denied | No write access | Request access or fork repository |
Branch already exists | Branch name collision | Delete old branch or use different name |
Merge conflicts | Diverged from main | Rebase or merge main into branch |