agentleFS
spiriMirrorspiriMirror/libuipc/.cursor/skills/repository-setup/SKILL.md

repository-setup

Skill351 starsChanged 3 months agoApache-2.0View on GitHub

Guide for setting up repository remotes when working with forks

The file

We split this skill 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:

    When working with a forked repository, GitHub CLI (gh) commands may fail to find issues and PRs because they default to the fork's …

    line 8
  2. Very specific:

    Add the upstream repository as a remote (you can name it anything, upstream is conventional):

    line 12
  3. Very specific:

    All Cursor commands use --repo spiriMirror/libuipc to reference the upstream repository, ensuring they work correctly in:

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
SKILL.md

Repository Setup for Forks

When working with a forked repository, GitHub CLI (gh) commands may fail to find issues and PRs because they default to the fork's repository instead of the upstream repository.

Setup

Add the upstream repository as a remote (you can name it anything, upstream is conventional):

git remote add upstream https://github.com/spiriMirror/libuipc

How Commands Work

All Cursor commands use --repo spiriMirror/libuipc to reference the upstream repository, ensuring they work correctly in:

  • The upstream repository
  • A forked repository
  • A repository with custom remote names

This ensures issues and PRs are always referenced from the upstream repository where they actually exist.

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.