agentleFS
Sign inStart free
NickMoignardNickMoignard/agent-workspace-template/.agents/skills/add-project/SKILL.md

add-project

Skill0 starsChanged 2 months agoMITView on GitHub

Add a new project to the agent workspace by recording its clone URL in projects.yaml, cloning it into the shared source dir, and symlinking it into projects/. Wires it into the VS Code workspace and issue tracker. Use when the user wants to add, include, or pull a repo/project into the workspace.

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. palmcivet/awesome-arknights-endfield★ 111same name
    2. dmzoneill/skills★ 2same name
    3. blueOctopusAI/intel-hub★ 0same name
    4. leomancini/claude-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this when a new project should join the workspace.

    line 8
  2. Very specific:

    If the env var is unset, run /setup-projects first.

    line 18
  3. Very specific:

    Never edit the folders block of the .code-workspace by hand — always regenerate it with make sync-workspace.

    line 45
  4. Very specific:

    If make is unavailable, call bash scripts/add-project.sh <url> directly.

    line 49

“Common” is measured: kept by at least 6 in 10 of the 4 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Add a project to the workspace

Use this when a new project should join the workspace. Projects are referenced as symlinks to shared clones, not git submodules (see docs/adr/0004-projects-as-symlinks-not-submodules.md).

Procedure

  1. Gather inputs. You need the git clone URL. The symlink name is derived from the repo basename automatically.
  2. Confirm prerequisites. $AGENTS_GIT_SRC_DIR must be set and yq present. If the env var is unset, run /setup-projects first.

  3. Run the make target from the workspace root:

    make add-project URL=<git-url>

    This wraps scripts/add-project.sh, which:

    • appends the URL to projects.yaml (if not already listed),
    • clones it into $AGENTS_GIT_SRC_DIR/<name> and symlinks projects/<name>,
    • regenerates the *.code-workspace folder list (sync-workspace.mjs),
    • installs the project's dependencies if a manifest is present,
    • files a beads onboarding issue (if bd is installed).
  4. Verify the project's folder appears in the .code-workspace folders array and projects/<name> resolves to the clone.

  5. Commit the workspace change (the symlink is git-ignored — do not add it):

    git add projects.yaml workspace.code-workspace
git commit -m "Add <name> project"

Rules

  • Never edit the folders block of the .code-workspace by hand — always regenerate it with make sync-workspace.
  • Work on the project's code from inside its clone (its own git repo). The workspace pins no commits; there is no parent pointer to update.
  • If make is unavailable, call bash scripts/add-project.sh <url> directly.

Removing a project

# 1. Remove the URL line from projects.yaml (edit, or with yq):
yq -i 'del(.projects[] | select(. == "<git-url>"))' projects.yaml
# 2. Drop the symlink (leaves the shared clone intact for other workspaces):
rm -f projects/<name>
# 3. Refresh the VS Code folders:
make sync-workspace

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