OpeItcLoc03/skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(project-create): правки по review-субагенту — шаг 4 (где+имя), шаг 5 (локальная ФС) [1304]

Browse Source
This commit is contained in:
vitya
2026-08-26 22:58:27 +03:00
parent 621eacc808
commit cf8d574c9f
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
skills/project-create/SKILL.md
View File

@@ -1,7 +1,7 @@
--- ---
name: project-create name: project-create
author: ours author: ours
version: 0.1.0 version: 0.1.1
description: > description: >
Mappa-side cycle of creating a new project: ask the operator for the hosting Mappa-side cycle of creating a new project: ask the operator for the hosting
address (platform + user/org) FIRST — never derive it from neighbouring address (platform + user/org) FIRST — never derive it from neighbouring
@@ -49,8 +49,8 @@ Before any `projects_register` / gitea repo creation for a **new** project.
3. **Create SIMULTANEOUSLY** (not one before the other): 3. **Create SIMULTANEOUSLY** (not one before the other):
- `mcp__mappa__projects_register` — mappa registration (id returned). - `mcp__mappa__projects_register` — mappa registration (id returned).
- repo via `.admin` — `task_create` in `.admin` (**priority P0** — it blocks the project chain) + covering letter via `inbox_send` (a task on the board doesn't ping a live session). The repo task is an **ops task → NO paired review** (mappa-delegation: skip review for ops). Acceptance: repo created private, answer letter with clone URLs + which token is needed for push. - repo via `.admin` — `task_create` in `.admin` (**priority P0** — it blocks the project chain) + covering letter via `inbox_send` (a task on the board doesn't ping a live session). The repo task is an **ops task → NO paired review** (mappa-delegation: skip review for ops). Acceptance: repo created private, answer letter with clone URLs + which token is needed for push.
4. **Ask the operator: where on disk** the project folder goes and what it's named — do not guess the path. 4. **Ask the operator: where on disk the project folder goes and what it's named** (location AND folder name — both are the operator's call) — do not guess the path or the name.
5. **Create the folder** on disk. 5. **Create the folder** on the agent's local filesystem (the operator's workstation, not a remote host).
6. **Hand over to bootstrap** — `project-bootstrap` (general skill) does git init, .gitignore, README, AGENTS.md, remote connect, push. Separate step, after the repo exists. 6. **Hand over to bootstrap** — `project-bootstrap` (general skill) does git init, .gitignore, README, AGENTS.md, remote connect, push. Separate step, after the repo exists.
## Why the repo goes through `.admin` ## Why the repo goes through `.admin`