git-github
Skill0 starsChanged 7 months agoMITView on GitHub
Auto-activate when user mentions: git, github, PR, pull request, issue, branch, commit, diff, merge, clone, push, repo, repository, review. This plugin provides two MCP servers for complete Git + GitHub workflow coverage. Full GitHub API integration via MCP. Capabilities: Issues - create_issue — create new issue with title, body, labels, assignees - list_issues — list issues for a repository with filters (state, labels, assignee) - get_issue — get issue details by number - update_issue — update issue title, body, state,…
- Deletes or force-pushes
- Commits and pushes
6 other projects use a version of this.
Adopted by
Most recently taken up by
- lukashouthoofd/cenekathontheir own version, first seen Nov 8, 2026
- SwastikPandey1024/agentic-engineering-ostheir own version, first seen Oct 20, 2026
- siemens/elementtheir own version, first seen Oct 8, 2026
- alumpe/skillstheir own version, first seen Sep 11, 2026
- scitex-ai/claude-code-telegrammertheir own version, first seen Jun 14, 2026
- G-HunterAi/openclaw-skillstheir own version, first seen Apr 5, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- siemens/element★ 83same name
- lukashouthoofd/cenekathon★ 1same name
- scitex-ai/claude-code-telegrammer★ 1same name
- SwastikPandey1024/agentic-engineering-os★ 1same name
- alumpe/skills★ 0same name
- G-HunterAi/openclaw-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repositoryOne other file it gives its agents.
- CLAUDE.mdCLAUDE.md
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 73
Use git MCP for local operations (status, diff, commit, branch)
- Very specific: line 74
Use github MCP for remote operations (issues, PRs, repo management)
- Very specific: line 106
After merge: git_checkout base=main + CLI: git pull origin main
- Very specific: line 126
Use --force-with-lease instead of --force — it fails if someone else pushed to the branch.
- Distinctive: line 134
After merge: delete hotfix branch
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Git + GitHub Skill
Trigger
Auto-activate when user mentions: git, github, PR, pull request, issue, branch, commit, diff, merge, clone, push, repo, repository, review.
MCP Servers
This plugin provides two MCP servers for complete Git + GitHub workflow coverage.
1. GitHub MCP (@modelcontextprotocol/server-github)
Full GitHub API integration via MCP. Capabilities:
Issues
create_issue— create new issue with title, body, labels, assigneeslist_issues— list issues for a repository with filters (state, labels, assignee)get_issue— get issue details by numberupdate_issue— update issue title, body, state, labels, assigneesadd_issue_comment— add comment to an issuesearch_issues— search issues across repositories
Pull Requests
create_pull_request— create PR with title, body, head, base branchlist_pull_requests— list PRs with filters (state, head, base)get_pull_request— get PR details by numberget_pull_request_files— list files changed in a PRget_pull_request_comments— get PR review commentsget_pull_request_reviews— get PR reviewsget_pull_request_status— get PR CI/check statuscreate_pull_request_review— submit a PR review (approve, comment, request changes)merge_pull_request— merge a PR (merge, squash, or rebase)update_pull_request_branch— update PR branch with base branch
Repositories
create_repository— create new repo (public/private)search_repositories— search repos by queryfork_repository— fork a repositoryget_file_contents— read file or directory contents from a repocreate_or_update_file— create or update a file in a repopush_files— push multiple files in a single commit
Branches
create_branch— create branch from a reflist_commits— list commits on a branch
Users
search_users— search GitHub users
Code Search
search_code— search code across GitHub repositories
2. Git MCP (mcp-server-git)
Local git repository operations via MCP. Capabilities:
git_status— show working tree status (staged, unstaged, untracked files)git_diff— show full diff of all changesgit_diff_staged— show diff of staged changes onlygit_diff_unstaged— show diff of unstaged changes onlygit_log— show commit log with optional max countgit_branch— list all branchesgit_show— show contents of a specific commitgit_commit— create a commit with a messagegit_add— stage files for commitgit_reset— unstage filesgit_checkout— switch branches or restore filesgit_create_branch— create and optionally checkout a new branch
Usage Guidelines
- Prefer MCP tools over
ghCLI orgitCLI when available - Use
gitMCP for local operations (status, diff, commit, branch) - Use
githubMCP for remote operations (issues, PRs, repo management) - Fall back to
ghCLI for operations not covered by MCP (e.g.,gh auth status,gh run watch) - Fall back to
gitCLI for operations not covered by MCP (e.g.,git rebase,git stash)
Common Workflows
Create a PR
git_status— check current stategit_add— stage changesgit_commit— commit with conventional message- Push via CLI:
git push -u origin <branch> create_pull_request— open PR on GitHub
Review a PR
get_pull_request— read PR detailsget_pull_request_files— see changed filesget_pull_request_comments— check existing feedbackcreate_pull_request_review— submit review
Issue Triage
list_issues— see open issuesget_issue— read issue detailsadd_issue_comment— respond or ask for infoupdate_issue— add labels, assign, close
Feature Branch Workflow (end-to-end)
git_checkoutbase=main— ensure you're on main- CLI:
git pull origin main— get latest git_create_branch— createfeature/<name>branch- Work, then:
git_add+git_commit(repeat) - CLI:
git push -u origin feature/<name> create_pull_request— open PR, set base=main- After merge:
git_checkoutbase=main+ CLI:git pull origin main
Stash Workflow (CLI-only — MCP has no stash tool)
git stash push -m "wip: description"
git stash list # see all stashes
git stash pop # re-apply latest stash
git stash apply stash@{2} # re-apply specific stash
git stash drop # discard top stashRebase Workflow (CLI-only — MCP has no rebase tool)
git fetch origin main
git rebase origin/main # rebase feature branch on main
git rebase --continue # after resolving conflicts
git rebase --abort # abort if something goes wrong
git push --force-with-lease # push rebased branch (safer than --force)Use --force-with-lease instead of --force — it fails if someone else pushed to the branch.
Hotfix Workflow
git_create_branchname=hotfix/<issue>from=main- Fix the issue
git_add+git_commitwithfix:prefix- CLI:
git push -u origin hotfix/<issue> create_pull_request— base=main, titlefix: ...- After merge: delete hotfix branch
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

