agentleFS
Sign inStart free
metagit-aimetagit-ai/metagit-cli/.cursor/rules/github-cli.mdc

metagit-cli / rules

Cursor rule4 starsChanged 11 days agoMITView on GitHub

GitHub CLI (gh) auth — unset stale token env vars before API calls

  • Reads credentials
  • Commits and pushes

The file

We split this github-cli.mdc into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    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
  1. Very specific:

    Before any gh command (gh pr create, gh issue, gh run, etc.), unset stale token environment variables that override the keyring login:

    line 8
  2. Very specific:

    If auth still fails: gh auth status then gh auth login if needed.

    line 22
  3. Very specific:

    Do not export GH_TOKEN for local gh unless intentionally using that token for the session.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
github-cli.mdc
---
description: GitHub CLI (gh) auth — unset stale token env vars before API calls
alwaysApply: true
---

# GitHub CLI authentication

Before any `gh` command (`gh pr create`, `gh issue`, `gh run`, etc.), **unset stale token environment variables** that override the keyring login:

```bash
env -u GH_TOKEN -u GITHUB_TOKEN gh <subcommand> ...
```

## Why

An invalid or expired `GH_TOKEN` / `GITHUB_TOKEN` in the shell environment causes `HTTP 401: Bad credentials` even when `gh auth status` shows a valid keyring account (with "Active account: false" on the keyring entry).

## Checklist for PRs

1. Push branch: `git push -u origin HEAD` (SSH/git creds are separate from `gh`).
2. Create PR: `env -u GH_TOKEN -u GITHUB_TOKEN gh pr create ...`
3. If auth still fails: `gh auth status` then `gh auth login` if needed.

Do **not** export `GH_TOKEN` for local `gh` unless intentionally using that token for the session.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free