import-project
Bring an existing project into projects/ — clone through scripts/forge-clone.py, which reports the commit identity git resolves
Install
npx skills add https://github.com/pche-broken-artist/forge-of-thought/tree/main/.claude/skills/import-project
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install pche-broken-artist-forge-of-thought@llmmart
git clone https://github.com/pche-broken-artist/forge-of-thought.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole pche-broken-artist/forge-of-thought collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Bring the project at $0 into the forge (POS.1060). Git is done by
scripts/forge-clone.py only (CLAUDE.md, Persistence).
- Require the URL. The target directory is
projects/<repository name>— the name falls out of the URL (no slug parameter); if the directory already exists, stop and report. - On the principal's word run
python scripts/forge-clone.py <url>. The commit identity is git's, resolved per host from his own configuration (CLAUDE.md, Persistence); the script sets none and reports the one the clone resolves. - Relay what the script prints (its header says what); a project
file missing is said as
templates/project.mdsays. When git resolves no identity, say in plain words what that means: git has no name and e-mail to sign commits on this host — the login that cloned the repository is a different thing — andforge-savecommits nothing until git resolves one. The usual causes and the ways out are the identity step of/setup's; the forge writes none. - Finish by recommending
/forge <slug>as the first act of work: the engine does not track the project and cannot guess it, so the project is selected by naming it.
Nothing is written into the imported project by this command.
/import-project clones. A project already on this machine, in a
repository of its own, in another's or in none, is copied or linked
into projects/<slug> by hand, and the forge knows it from
/forge <slug> on (POS.0550).
Files (forge-of-thought)
-
SKILL.md 1.7 KB
--- description: Bring an existing project into projects/ — clone through scripts/forge-clone.py, which reports the commit identity git resolves argument-hint: "<git-url>" disable-model-invocation: true --- Bring the project at `$0` into the forge (POS.1060). Git is done by `scripts/forge-clone.py` only (CLAUDE.md, Persistence). 1. Require the URL. The target directory is `projects/<repository name>` — the name falls out of the URL (no slug parameter); if the directory already exists, stop and report. 2. On the principal's word run `python scripts/forge-clone.py <url>`. The commit identity is git's, resolved per host from his own configuration (CLAUDE.md, Persistence); the script sets none and reports the one the clone resolves. 3. Relay what the script prints (its header says what); a project file missing is said as `templates/project.md` says. When git resolves no identity, say in plain words what that means: git has no name and e-mail to sign commits on this host — the login that cloned the repository is a different thing — and `forge-save` commits nothing until git resolves one. The usual causes and the ways out are the identity step of `/setup`'s; the forge writes none. 4. Finish by recommending `/forge <slug>` as the first act of work: the engine does not track the project and cannot guess it, so the project is selected by naming it. Nothing is written into the imported project by this command. `/import-project` clones. A project already on this machine, in a repository of its own, in another's or in none, is copied or linked into `projects/<slug>` by hand, and the forge knows it from `/forge <slug>` on (POS.0550).
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.