agentleFS
ceedaragentsceedaragents/cyrus/skills/cyrus-setup-repository/SKILL.md

cyrus-setup-repository

Skill888 starsChanged 53 days agoApache-2.0View on GitHub

Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.

  • Reads credentials

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If repositories are already configured, list them:

    line 18
  2. Distinctive:

    If multiple workspaces are configured, ask which workspace to use:

    line 41
  3. Distinctive:

    Verify the repo was added:

    line 47
  4. Distinctive:

    If yes, repeat Step 2. If no, continue.

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

CRITICAL: Never use Read, Edit, or Write tools on ~/.cyrus/.env or any file inside ~/.cyrus/. Use only Bash commands (grep, printf >>, etc.) to interact with env files — secrets must never be read into the conversation context.

Setup Repository

Adds Git repositories to Cyrus so it knows which codebases to work with.

Step 1: Check Existing Repositories

cat ~/.cyrus/config.json 2>/dev/null | grep -o '"url"' | wc -l

If repositories are already configured, list them:

cat ~/.cyrus/config.json 2>/dev/null

Inform the user which repos are already added.

Step 2: Add a Repository

Ask the user:

What is the Git URL of the repository you want Cyrus to work with? (e.g., https://github.com/yourorg/yourrepo.git)

Run:

cyrus self-add-repo <url>

This clones the repo to ~/.cyrus/repos/ and registers it with the Linear workspace.

If multiple workspaces are configured, ask which workspace to use:

cyrus self-add-repo <url> "<workspace name>"

Verify the repo was added:

cat ~/.cyrus/config.json | grep "<repo-name>"

Step 3: Add More?

Ask the user:

Would you like to add another repository? (y/n)

If yes, repeat Step 2. If no, continue.

Completion

✓ Repository added: <url> (repeat for each added repo)

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.