cyrus-setup-repository — Claude Code skill: add a repo to Cyrus
Registers Git repositories in Cyrus so the agent knows which codebases to work with. Handy on first setup or when a new project joins the queue.
npx skills add cyrusagents/cyrus --skill cyrus-setup-repository -a claude-codeWhat cyrus-setup-repository does
The skill walks the agent through the whole flow. It first counts and lists the repositories already present in ~/.cyrus/config.json. Then it asks for a Git URL, clones the code into ~/.cyrus/repos/ and registers the repo with the Linear workspace.
Registration happens through cyrus self-add-repo <url>. With more than one workspace configured, the same call takes the workspace name: cyrus self-add-repo <url> "<workspace name>". The skill then greps the config to confirm the entry and offers to add another repository.
One hard rule applies to everything under ~/.cyrus/. The agent must not point Read, Edit or Write at ~/.cyrus/.env or its neighbours; only Bash commands such as grep and printf >> are allowed there. Secrets stay out of the conversation context, which is also why you cannot just ask the agent to print the env file.
What it helps with
- wire a new repository into Cyrus without touching the config by hand
- list the repositories Cyrus already knows about
- bind a repository to a specific Linear workspace
- confirm a repository landed in
~/.cyrus/config.json - add several repositories one after another
Example prompts for the agent
- Add
https://github.com/yourorg/yourrepo.gitto Cyrus - List the repositories currently configured in Cyrus
- Register this repo under the
my-workspaceworkspace
How to install cyrus-setup-repository
1Skills CLI (Vercel)
npx skills add cyrusagents/cyrus --skill cyrus-setup-repository -a claude-code2Manually: put the files in place
~/.claude/skills/cyrus-setup-repository/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/cyrus-setup-repository/
1Skills CLI (Vercel)
npx skills add cyrusagents/cyrus --skill cyrus-setup-repository -a codex2Manually: put the files in place
.agents/skills/cyrus-setup-repository/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add cyrusagents/cyrus --skill cyrus-setup-repository -a cursor2Manually: put the files in place
.cursor/skills/cyrus-setup-repository/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install cyrusagents/cyrus cyrus-setup-repository2Manually: put the files in place
.github/skills/cyrus-setup-repository/SKILL.md1Skills CLI (Vercel)
npx skills add cyrusagents/cyrus --skill cyrus-setup-repository -a gemini-cli2Platform CLI
gemini skills install https://github.com/cyrusagents/cyrus --path skills/cyrus-setup-repositoryManually: put the files in place
.devin/skills/cyrus-setup-repository/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add cyrusagents/cyrus --skill cyrus-setup-repository -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about cyrus-setup-repository
How do I install cyrus-setup-repository in Claude Code?
Run npx skills add cyrusagents/cyrus --skill cyrus-setup-repository -a claude-code. The skill then sits at ~/.claude/skills/cyrus-setup-repository/SKILL.md.
What does cyrus-setup-repository do?
It adds Git repositories to the Cyrus configuration so the agent can process issues from them. The code gets cloned to ~/.cyrus/repos/ and registered with the Linear workspace.
Why can't the agent read ~/.cyrus/.env with normal file tools?
Secrets must not enter the conversation context. Only Bash commands like grep and printf >> are permitted on files inside ~/.cyrus/.
Source text
SKILL.md · Apache-2.0
--- name: cyrus-setup-repository description: Add one or more Git repositories to Cyrus configuration so it can process issues from those repos. --- **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 ```bash cat ~/.cyrus/config.json 2>/dev/null | grep -o '"url"' | wc -l ``` If repositories are already configured, list them: ```bash 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: ```bash 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: ```bash cyrus self-add-repo <url> "<workspace name>" ``` Verify the repo was added: ```bash 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)
© cyrusagents · Apache-2.0 · cyrusagents/cyrus