agentleFS
Sign inStart free
rakaarwakyrakaarwaky/agents-arwaky/skills/git/repo-manager/SKILL.md

repo-manager

Skill0 starsChanged 4 days agoMITView on GitHub

Clone/create/fork repos; manage remotes, releases, settings, secrets, and Actions CI via gh.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill 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
  1. Very specific:

    Create, clone, fork, configure, and manage GitHub repositories.

    line 10
  2. Very specific:

    Prefer gh: Use gh commands; fall back to git + curl only where gh lacks coverage.

    line 17

≈ “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

GitHub Repository Management

Create, clone, fork, configure, and manage GitHub repositories. Prefer gh; fall back to git + curl only where gh lacks coverage.

Global Rules

Rules that apply to every repo-manager operation. Reference files cite these; they never restate them.

  • Auth prerequisite: Authenticated with GitHub first (see github-auth skill). Auth, username, and repo detection live in github-auth's helper — source it rather than re-implementing the fallback chain.
  • Prefer gh: Use gh commands; fall back to git + curl only where gh lacks coverage.
  • Single source of auth: Source gh-env.sh from github-auth; it resolves from ~/.hermes, ~/.qwen, ~/.config/opencode, or agents-arwaky/skills roots.

Routing

StepReferencePurpose
Setupgithub-auth skillSource gh-env.sh for auth and repo detection (formerly setup.md).
Clonereferences/clone.mdgit clone <url> and gh repo clone owner/repo (HTTPS, SSH, shallow, branch).
Createreferences/create.mdgh repo create NAME --public|--private --clone (user, org, template).
Forkreferences/fork.mdgh repo fork owner/repo --clone, then gh repo sync for keeping in sync.
.gitignore coveragereferences/gitignore-audit.mdThree-way diff (tracked / untracked / on-disk) + git check-ignore -v to find gaps and add rules.
Inforeferences/info.mdgh repo view, gh repo list, gh search repos.
Settingsreferences/setting.mdgh repo edit (description, visibility, topics, default branch) + branch protection REST.
Actions & releasesreferences/action.mdgh workflow / gh run / gh secret / gh release (includes NaCl secrets fallback).

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