create-or-clone-repository
Skill4 starsChanged 4 months agoMITView on GitHub
Create or clone Git repositories into the configured ghq layout. Use whenever a task requires initializing a new repository or obtaining a local clone, before choosing a directory or running git init or git clone.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- build-incrementalSkill
- code-simplifySkill
- design-firstSkill
- implementation-workflowSkill
- manage-git-worktreesSkill
- plan-driven-developmentSkill
- setup-wiki-backed-project-skillsSkill
- subagent-supervisionSkill
- task-briefSkill
- test-driven-debugSkill
- tidy-firstSkill
- write-personal-wikiSkill
- write-project-wikiSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use ghq so repositories follow the configured root and host/owner/repository layout.
- Distinctive: line 9
Do not choose an arbitrary clone directory or use git init or git clone directly unless the user explicitly requests a different location …
- Very specific: line 14
Create a new local repository with ghq create HOST/OWNER/REPOSITORY.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
Create or Clone Repository
Use ghq so repositories follow the configured root and host/owner/repository layout.
Do not choose an arbitrary clone directory or use git init or git clone directly
unless the user explicitly requests a different location or method.
- Confirm the repository identity and check
ghq list -pfor an existing clone. Reuse it when available; do not relocate an existing repository. - Clone a remote repository with
ghq get -p HOST/OWNER/REPOSITORY(SSH), orghq get URLwhen a specific URL is provided. - Create a new local repository with
ghq create HOST/OWNER/REPOSITORY. If the identity is unknown, ask rather than inventing a host or owner. - Resolve the resulting path with
ghq list -p -e HOST/OWNER/REPOSITORYand run subsequent commands there.
ghq create does not create a hosted repository or configure origin. When worktrees
are needed, register the intended remote URL and make the initial commit first.
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
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.

