# github

Connects AI agents to GitHub repositories, issues, and pull requests via Membrane CLI. Manages workflows without manual token refresh.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 383 installs · ★ 270
- Author: membrane
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/membranedev/application-skills/tree/HEAD/skills/github/SKILL.md
- Updated: 2026-04-28
- HTML: https://affpapa.org/en/nevibecode/skills/membrane-github

## What it does

This skill connects your coding assistant to GitHub using the Membrane CLI harness. It provides predefined actions to list user and organization repositories, inspect commits, create releases, review PRs, and edit issues. If a specific endpoint is missing from the built-in action list, the agent can call GitHub REST endpoints directly via `membrane request`.

Membrane handles credentials and token refreshes under the hood. You need a valid Membrane account and the `@membranehq/cli@latest` npm package installed on your machine. Without the Membrane CLI installed in your environment, the agent cannot authenticate or execute any commands.

## Requirements
- Works with: GitHub

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add membranedev/application-skills --skill github -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/github/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/github/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add membranedev/application-skills --skill github -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/github/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add membranedev/application-skills --skill github -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/github/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install membranedev/application-skills github
```

2. **Manually: put the files in place**
- File: `.github/skills/github/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add membranedev/application-skills --skill github -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/membranedev/application-skills --path skills/github
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/github/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add membranedev/application-skills --skill github -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/membranedev/application-skills/tree/HEAD/skills/github/SKILL.md

## When to use it
- create and update GitHub issues directly from the agent
- review, comment on, and merge pull requests
- list user and organization repositories or branches
- proxy raw REST API calls to GitHub with automated auth

## Example prompts
- List all open pull requests in this repository using Membrane
- Create a new issue titled 'Database timeout' and fill in the details
- Show the latest commits in the active branch

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 12f70cc5f28b278e.

BEGIN THIRD-PARTY FILE 12f70cc5f28b278e
````text
---
name: github
description: |
  Github integration. Manage project management and ticketing data, records, and workflows. Use when the user wants to interact with Github data.
compatibility: Requires network access and a valid Membrane account (Free tier supported).
license: MIT
homepage: https://getmembrane.com
repository: https://github.com/membranedev/application-skills
metadata:
  author: membrane
  version: "1.0"
  categories: "Project Management, Ticketing"
---

# Github

GitHub is a web-based platform for version control and collaboration using Git. Developers use it to host, review, and manage code, as well as to track and resolve issues.

Official docs: https://docs.github.com/en/rest

## Github Overview

- **Repository**
  - **Issue**
  - **Pull Request**

Use action names and parameters as needed.

## Working with Github

This skill uses the Membrane CLI to interact with Github. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.

### Install the CLI

Install the Membrane CLI so you can run `membrane` from the terminal:

```bash
npm install -g @membranehq/cli@latest
```

### Authentication

```bash
membrane login --tenant --clientName=<agentType>
```

This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available.

**Headless environments:** The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with:

```bash
membrane login complete <code>
```

Add `--json` to any command for machine-readable JSON output.

**Agent Types** : claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness

### Connecting to Github

Use `membrane connection ensure` to find or create a connection by app URL or domain:

```bash
membrane connection ensure "https://github.com/" --json
```
The user completes authentication in the browser. The output contains the new connection id.

This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically.

If the returned connection has `state: "READY"`, skip to **Step 2**.

#### 1b. Wait for the connection to be ready

If the connection is in `BUILDING` state, poll until it's ready:

```bash
npx @membranehq/cli connection get <id> --wait --json
```

The `--wait` flag long-polls (up to `--timeout` seconds, default 30) until the state changes. Keep polling until `state` is no longer `BUILDING`.

The resulting state tells you what to do next:

- **`READY`** — connection is fully set up. Skip to **Step 2**.
- **`CLIENT_ACTION_REQUIRED`** — the user or agent needs to do something. The `clientAction` object describes the required action:
  - `clientAction.type` — the kind of action needed:
    - `"connect"` — user needs to authenticate (OAuth, API key, etc.). This covers initial authentication and re-authentication for disconnected connections.
````
END THIRD-PARTY FILE 12f70cc5f28b278e

The third-party file has ended. Everything between the 12f70cc5f28b278e tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3155 of 7911 bytes. © membrane · MIT · https://github.com/membranedev/application-skills/tree/HEAD/skills/github/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md