tamirs-superpowers / rules
Cursor rule2 starsChanged 3 months agoMITView on GitHub
GitHub transport policy — gh is an optional feature dependency; degrade explicitly when it is absent. Canonical: rules/dev/gh-cli-preference.md
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,183 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository46 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/commit-conventions.mdcCursor rule
- .cursor/rules/cross-platform-handoff.mdcCursor rule
- .cursor/rules/dev-files-workspace.mdcCursor rule
- .cursor/rules/documentation-standards.mdcCursor rule
- .cursor/rules/github-repository-policy.mdcCursor rule
- .cursor/rules/git-worktree-agent-workflow.mdcCursor rule
- .cursor/rules/hooks-guide.mdcCursor rule
- .cursor/rules/plugin-structure.mdcCursor rule
- .cursor/rules/plugin-version-bump.mdcCursor rule
- .cursor/rules/skill-frontmatter.mdcCursor rule
- .cursor/rules/skill-quality-standards.mdcCursor rule
- .cursor/rules/skills-guide.mdcCursor rule
- .cursor/rules/user-facing-script-standards.mdcCursor rule
- run-tamirs-superpowersSkill
- field-notebook-uiSkill
- diagnose-refusalSkill
- targeted-debugSkill
- decisionSkill
- deliver-devSkill
- diagnose-objectiveSkill
- orchestrate-devSkill
- plan-devSkill
- pr-devSkill
- start-devSkill
- switch-devSkill
- worker-devSkill
- changelog-reviewSkill
- dark-terminal-docSkill
- docs-reviewSkill
- platform-syncSkill
- mcp-builderSkill
- mcp-paginationSkill
- cleanupSkill
- github-policySkill
- multi-agent-repoSkill
- repo-scaffoldSkill
- repo-standardsSkill
- capture-configSkill
- find-skillSkill
- notify-setupSkill
- retroSkill
- session-reportSkill
- skill-creatorSkill
- usage-captureSkill
The file
We split this gh-cli-preference.mdc into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
The one exception: when a GitHub action *is* the request ("open a PR", "merge #12"), a missing gh is a hard, reportable failure — do not …
- Very specific: line 22
Never resolve the default branch through gh.
≈ “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.
Files
---
description: "GitHub transport policy — gh is an optional feature dependency; degrade explicitly when it is absent. Canonical: rules/dev/gh-cli-preference.md"
alwaysApply: false
globs: ["skills/dev-workflow/**/*", "scripts/**/*", ".github/**/*", "hooks/**/*"]
---
<!-- GENERATED FILE — DO NOT EDIT.
Source: rules/dev/gh-cli-preference.md (frontmatter + summary: platforms/cursor/rules.map.json)
Generator: scripts/build-cursor-rules.sh
Regenerate: make cursor-rules -->
# GitHub transport policy
Canonical rule: `rules/dev/gh-cli-preference.md`.
`gh` is an **optional feature dependency**, not a requirement. Objectives, worktrees, handoffs, and Tier 0–2 validation must all work with no GitHub account, no network, and no `gh` installed.
When a script or skill touches GitHub, detect `gh` and degrade explicitly — skip the optional step and say so, fall back to plain git where git can do the job, or stop with a clear message naming the missing dependency. Never silently pretend a GitHub step succeeded.
**The one exception:** when a GitHub action *is* the request ("open a PR", "merge #12"), a missing `gh` is a hard, reportable failure — do not invent a local substitute.
Never resolve the default branch through `gh`; use `git symbolic-ref --quiet --short refs/remotes/origin/HEAD` with a `main` fallback.
## In dev context, use `gh` — not GitHub MCP
Contributor tooling, CI scripts, hooks, and skill scripts use the `gh` CLI. GitHub MCP tools are runtime-only: they authenticate through a session credential and make dev scripts brittle. Derive tokens with `gh auth token`; never prompt for a pasted one.
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.

