agentleFS
Sign inStart free
JarvusInnovationsJarvusInnovations/agent-skills/skills/repo-setup/SKILL.md

repo-setup

Skill1 starsChanged 3 months agoNo licenceView on GitHub

Stand up a new Jarvus repository the house way — the one-time bootstrap that wires `develop` as the default branch, `main` as the release target, merge-commit-only merge policy, branch rulesets that keep auto-delete from eating `develop`, and the `JarvusInnovations/infra-components` Release-PR workflows. Use when creating a new repo, running `gh repo create`, pushing an existing local project to GitHub for the first time, adopting the develop→main release flow in a repo that lacks it, or auditing an existing repo against house conventions. Also use when something in the branch/merge plumbing misbehaves: `develop` vanished after a release merged, a release PR reports "No commits between main and develop", PR checks sit at `action_required` on a new repo, someone squash-merged, or a first npm publish fails from CI. Triggers: "new repo", "create a repo", "set up a repo", "gh repo create", "push this to GitHub", "repo settings", "branch protection", "rulesets", "default branch", "develop branch is gone", "set up the release flow", "make this repo standard". Scope is the repo shell — cutting releases belongs to `release-flow`, pre-merge lint/test gates to `ci-quality-gates`.

  • Reads credentials
  • Commits and pushes

8 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use pr-review.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    pr-review

    Verify the technical accuracy of a vscode-docs pull request against the VS Code source code in microsoft/vscode. Use when reviewing a docs PR for factual correctness: setting names, command IDs, default values, API shapes, keybindings, versioned availability, and described behavior.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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