github
v1.0.6
Manage repositories, users, releases, and automate GitHub workflows
Use cases/Code review & GitHub
Fetch PRs, read diffs, manage issues—code review, release notes, CI triage.
32,630 resources matched · Page 1 of 680
GitHub MCP puts the AI inside your collaboration loop: review PR diffs, search issue history for known bugs, read CI logs, and roll commits into changelogs. The official github-mcp-server authenticates via GitHub API or a PAT; Gitee and GitLab have equivalent servers.
Review practice: encode your team's checklist as a Skill (race conditions, edge cases, error handling, severity-ranked output), let the AI triage each PR through GitHub MCP, and have humans focus on flagged risks—faster reviews with fewer trivial misses.
Permissions: use fine-grained PATs scoped to target repos (contents / pull-requests), start read-only on org repositories, and require confirmation before the agent comments or merges.
v1.0.0
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
连接GitHub的MCP服务器,支持仓库管理、问题跟踪、代码搜索等功能
v1.2.4
GitHub API integration with managed OAuth. Access repositories, issues, pull requests, commits, branches, and users. Use this skill when users want to interact with GitHub repositories, manage issues and PRs, search code, or automate workflows. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a GitHub connection into automation, in the order they are used: the connection (the first step), a hosted function th
v1.0.12
Commits, branches, merges, and rebases Git repositories, resolves conflicts, and recovers lost history. Use when the work touches a repo, commit, branch, merge, rebase, stash, tag, or submodule; when Git refuses a command — index.lock exists, push rejected as non-fast-forward, detached HEAD, dubious ownership, unrelated histories, conflict markers left behind; when something looks lost after a hard reset, a bad rebase, a deleted branch, or a dropped stash; when splitting a mixed change, wording commit messages, cleaning history before review, or force-pushing without wrecking a teammate's work; when a credential or a huge file got committed; when setting up worktrees, hooks, LFS, sparse checkout, signing, or separate work and personal identities. Not for CI pipeline YAML (github-actions, gitlab) or for composing the pull request description itself (pull-request).
GitLab的MCP服务器,支持GitLab的读取和写入
v1.0.5
Work with GitHub repositories, issues, pull requests, commits, branches, releases, and workflows via the GitHub REST and GraphQL APIs.
v1.0.5
Work with GitLab projects, issues, merge requests, commits, branches, pipelines, and groups via the GitLab API.
Connect your AI agents to GitHub — manage repos, issues, PRs, workflows, and more
v1.0.0
Interact with GitLab using the `glab` CLI. Use when Claude needs to work with GitLab merge requests, CI/CD pipelines, issues, releases, or make API requests. Supports gitlab.com and self-hosted instances.
v1.0.0
Professional reviewer and critic.
v1.0.0
Avoid common GitLab CI/CD mistakes — rules gotchas, silent failures, and YAML merge traps.
Gitee的MCP服务器,支持代码仓库管理、问题跟踪等功能
v1.13.0
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
v0.1.6
GitHub MCP — wraps the GitHub public REST API (no auth required for public endpoints)
v0.1.2
GitLab MCP — wraps the GitLab REST API v4 (BYO API key)
v0.6.0
Connect AI assistants to GitHub - manage repos, issues, PRs, workflows, and git operations.
v0.2.0
Local Git via MCP: status, log, diff, file history, branches, and gated stage/commit. Pure-JS.
v0.2.0
GitHub via MCP: search, repos, issues, PRs, files, notifications. OAuth device flow or token.
v1.0.3
Manage projects, groups, branches, merge requests, and CI/CD pipelines
v1.0.0
GitHub MCP Server - List PRs, issues, repo info, and search code
v1.0.1
GitHub analytics - repos, PRs, issues, releases, contributors
v1.0.1
Git log, diff, blame, branch stats for AI agents
v0.7.1
MCP server for GitHub operations (PRs, issues, actions) with structured, token-efficient output
v0.8.0
Structured git operations (status, log, diff, branch, show) as typed JSON.
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
GitHub CLI for issues, PRs, CI/check logs, comments, reviews, releases, repos, and gh api queries.
Review changed code for correctness, security, code quality, and performance. Use when the user asks to review code changes, a PR, or specific files. Invoke with `/review`, `/review <pr-number>`, `/review <file-path>`, or `/review <pr-number> --comment` to post inline comments on the PR. Add `--effort low|medium|high` to trade depth for speed (defaults to high for PRs, medium for local changes).
Review a ClickHouse Pull Request for correctness, safety, performance, and compliance. Use when the user wants to review a PR or diff.
Repository-specific guidance for the AI code review agent reviewing this repo
Review code for common issues. Use when reviewing PRs, suggesting code changes, or when user asks to review code.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
Pre-landing PR review. (gstack)
Analyze auto-memory for promotion candidates, stale entries, consolidation opportunities, and health metrics. Use when the user runs /si:review or asks what has been learned and what should be promoted or pruned.
Reviews code changes and provides constructive feedback. Should be used when a review is requested to provide a consistent review behavior and output format. This skill can be used for code reviews in general, not just for GitHub pull requests.
Use when applies to product pages, local business pages, recipes, apps, books, and any page that aggregates user reviews. Use when auditing rich result eligibility for e-commerce or review sites.
vdevel
Review an Ansible PR following the project's standardized process from CLAUDE.md
Use gh for GitHub issues, PR status, CI/logs, comments, reviews, releases, and API queries.
Deprecated standalone review skill
Use the `gh` CLI for issues, pull requests, Actions runs, and GitHub API queries.
Review Playwright tests for quality. Use when user says "review tests", "check test quality", "audit tests", "improve tests", "test code review", or "playwright best practices check".
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Use when user asks to review contracts, detect contract risks, or perform compliance checks. 合同智能审核 - 对合同扫描件、图片合同、双语合同进行完整审核。 覆盖 OCR 识别、条款分析、风险检测、合规校对、翻译摘要全流程。 适用于法务审核、采购合同审查、供应链合规检查等场景。 关键词:合同审核、风险检测、条款分析、合规校对、contract review、risk detection。
当需要开始与当前工作区隔离的功能开发,或在执行实现计划之前使用——通过原生工具或 git worktree 回退机制确保隔离工作区存在
完成任务、实现重要功能或合并前使用,用于验证工作成果是否符合要求
收到代码审查反馈后、实施建议之前使用,尤其当反馈不明确或技术上有疑问时——需要技术严谨性和验证,而非敷衍附和或盲目执行
国内 Git 平台配置参考——Gitee、Coding.net、极狐 GitLab、CNB 的 SSH/HTTPS/凭据/CI 接入差异与镜像同步配置。仅在用户显式 /chinese-git-workflow 时调用,不要根据上下文自动触发。
A fine-grained PAT is simplest for local stdio use; GitHub App / OAuth matters for multi-user hosted deployments. Env vars are on each resource page.
Sometimes. Treat it as a first-pass filter—good at semantic defects, but keep human audit for supply-chain and authorization logic.
Depends on the model provider and token scope. Enterprises often pair local models with read-only, short-lived, least-scope PATs and rotate them.