agentleFS
Sign inStart free
dmzoneilldmzoneill/skills/add-project/SKILL.md

add-project

Skill2 starsChanged 19 days agoApache-2.0View on GitHub

Add a new project to config.json with auto-detection and validation. Detects settings from directory, validates GitLab/Jira access, optionally configures Quay/Bonfire, generates initial knowledge. Use when user says "add project", "configure new repo".

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    If gitlab: gitlab_mr_list(project, state="opened") — verify access

    line 37

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

Adds a project to config.json with auto-detection, validation, and optional knowledge generation.

Inputs

InputTypeRequiredPurpose
pathstringyesPath to project directory
namestringnoProject name (default: dir name)
gitlabstringnoGitLab path (auto-detect)
jira_projectstringyesJira key (e.g., AAP, KONFLUX)
jira_componentstringnoJira component
konflux_namespacestringnoKonflux tenant namespace
setup_quayboolfalseConfigure Quay
setup_bonfireboolfalseConfigure Bonfire
generate_knowledgebooltrueGenerate initial knowledge

Workflow

1. Load Persona

  • persona_load("project") or developer for project tools

2. Check Known Issues

  • check_known_issues("gitlab_project_info")

3. Detect Settings

  • project_detect(path) — language, branch, gitlab, lint/test commands, scopes

4. Validate

  • Verify path exists
  • If gitlab: gitlab_mr_list(project, state="opened") — verify access
  • jira_search or project tools — verify Jira access

5. Add Project

  • project_add(name, path, gitlab, jira_project, jira_component, konflux_namespace, auto_detect=true)

6. Optional Setup

  • Quay: Output instructions for config.json quay.repositories
  • Bonfire: Output instructions for bonfire.apps

7. Generate Knowledge (if requested)

  • knowledge_scan(project, persona="developer")
  • code_index(project)
  • code_watch(project, action="start")

8. Detect/Learn Failures

  • "no such host" → learn_tool_fix("gitlab_project_info", "no such host", "VPN", "vpn_connect()")
  • "project not found", "project does not exist" → record patterns

9. Log & Track

  • memory_session_log("Added project {name}", "Path: ... GitLab: ...")
  • memory_append("state/projects", "configured_projects", {...})

Output

Project name, config_updated, knowledge_generated, vector_index_created, watcher_running.

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