onboard-repo

Sterne18

Forks1

Aktualisiert2. Juli 2026 um 13:54

Link a new repo into the hub and document it — manifest entry, symlink, Tier-1 reference doc with the dev loop, catalog row. Use when the project grows a repo or an existing repo isn't wired in yet.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

PakhomovAlexander

PakhomovAlexander/project-hub

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	onboard-repo
description	Link a new repo into the hub and document it — manifest entry, symlink, Tier-1 reference doc with the dev loop, catalog row. Use when the project grows a repo or an existing repo isn't wired in yet.
argument-hint	<repo> [kind]

Onboard a repo into the hub

Manifest. Add a line to repos.manifest: canonical:clone_dir:github_repo:kind (kind: service | infra | web | lib | …).
Link it. make repos (clones if missing, then symlinks into repos/<name>), then make status and confirm the repo shows up with a branch. Report what actually happened — don't claim a link you didn't see.
Write the Tier-1 reference: copy docs/repos/_template.md to docs/repos/<name>.md and fill it from the repo's own source (README, CI config, Makefile/package scripts):
- The Dev loop first — how to build, test, lint, and run. This is the single most valuable section for any agent that will touch the repo.
- Role, deploy target, and which hub invariants apply (link the ADR).
- Mark every fact confirmed (read from source, dated) or inferred. Cite paths as inline code, not links — repos/ is gitignored, so links into it break docs CI.
Catalog + front door. Add a row to docs/service-catalog.md (status ☐, pick a priority) if the hub has one, and to the key-repos table in README.md.
Verify. scripts/verify.sh — links and placeholders must come back clean.

Mehr aus diesem Repository

gleiches Repository

update-hub

PakhomovAlexander/project-hub

Pull the latest template improvements into this hub — fetch the template recorded in .hub-meta.yml, diff since the recorded commit, re-apply with this hub's values, verify. Use when asked to update or upgrade the hub from its template.

2026-07-0218

adr

PakhomovAlexander/project-hub

Record an architecture decision as a new ADR — numbered, honest about the rejected options, and wired into the index, the plan, and the invariants. Use when a significant decision was just made or needs recording.

2026-07-0218

resume

PakhomovAlexander/project-hub

Pick up an in-flight workstream cold — load its design doc, verify its claimed state against reality, and continue from the "resume here" list. Use when returning to interrupted work or taking over someone else's stream.

2026-07-0218

tracker

PakhomovAlexander/project-hub

Refresh docs/tracker.md — the live status board — so it is true right now. Use at the start or end of a work session, when the session brief flags the snapshot as stale, or after anything lands.

2026-07-0218

verify

PakhomovAlexander/project-hub

Self-check the hub — leftover placeholders, broken internal links, links into gitignored repos/, non-executable hooks, stale tracker. Run before pushing doc changes or after any bulk edit.

2026-07-0218

name	onboard-repo
description	Link a new repo into the hub and document it — manifest entry, symlink, Tier-1 reference doc with the dev loop, catalog row. Use when the project grows a repo or an existing repo isn't wired in yet.
argument-hint	<repo> [kind]

Onboard a repo into the hub

Manifest. Add a line to repos.manifest: canonical:clone_dir:github_repo:kind (kind: service | infra | web | lib | …).
Link it. make repos (clones if missing, then symlinks into repos/<name>), then make status and confirm the repo shows up with a branch. Report what actually happened — don't claim a link you didn't see.
Write the Tier-1 reference: copy docs/repos/_template.md to docs/repos/<name>.md and fill it from the repo's own source (README, CI config, Makefile/package scripts):
- The Dev loop first — how to build, test, lint, and run. This is the single most valuable section for any agent that will touch the repo.
- Role, deploy target, and which hub invariants apply (link the ADR).
- Mark every fact confirmed (read from source, dated) or inferred. Cite paths as inline code, not links — repos/ is gitignored, so links into it break docs CI.
Catalog + front door. Add a row to docs/service-catalog.md (status ☐, pick a priority) if the hub has one, and to the key-repos table in README.md.
Verify. scripts/verify.sh — links and placeholders must come back clean.