메뉴
Register a new sub-repo in the knowledge base.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | add-repo |
| description | Register a new sub-repo in the knowledge base. |
Adds a new sub-repo to the harness: updates local repos/repos.json (gitignored), clones, generates knowledge YAML.
If repos/repos.json is missing, copy repos/repos.json.example to repos/repos.json and edit entries there. Do not commit repos/repos.json.
Accept HTTPS, SSH URL, or local path. Extract repo name from URL (last segment without .git).
cat repos/repos.json | jq '.repos[] | select(.name == "<repo-name>")'
If already exists: report and stop.
Add: {"name":"<name>","url":"<url>","defaultBranch":"main"}
bun run repo init --repo <repo-name> --human
/sync-knowledge <repo-name>
Run red-green-refactor in vertical slices, emphasizing behavior-first tests and harness quality gates.
Break a plan/PRD into independent vertical-slice Beads issues with explicit dependencies.
Synthesize current context into a PRD and file it as a Beads feature/epic issue.
Phase 2 of the Forge pipeline. Turn a research document into an implementation plan that is built around Beads issues and TDD. Reads plans/research/<slug>.md, designs the build, sets up red-green-refactor test strategy using the tdd skill, materializes a Beads epic/feature/tasks with dependencies and priorities, and defines demo/test checkpoints. Use when starting /forge-plan or the plan step of /forgemaster.
Fact-check an implementation plan against the real codebase and first-party documentation, flagging inaccuracies with what / why / evidence and a severity tier. Use when the user wants a plan reviewed or validated for accuracy, runs /review-plan, or wants a plan checked against real code before implementing. Accepts a Beads issue, a filesystem path, or a plan pasted into chat.
Phase 3 of the Forge pipeline. Execute the plan's Beads tasks with red-green-refactor TDD, committing per checkpoint and pausing at each natural stopping point so the user can run a live demo or test and see the work themselves. Use when starting /forge-implement or the implement step of /forgemaster.