メニュー
Use to register a project in the Raven registry so it gets included in future raven-registry-sync updates. Run from inside the project directory, or pass the path explicitly. Also supports listing all registered projects and removing stale entries.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Initialize Raven for a new project. Andie-conversational — auto-scans project, asks at most 2 questions, generates manifest.json, validates, and commits with audit trail.
USE PROACTIVELY whenever the user asks for: planning, design, architecture decision, tradeoff analysis, comparing approaches, strategy, system design, refactor scope, deciding what to build, or any non-trivial request needing clarification. Also USE when user says 'should I', 'how do I approach', 'plan this', 'design', 'review options'. Compact plan-first orchestration. Routes work, runs triad (Functional/Technical/Data), HITL gated, OODA loop. Hands off plans, never implements. Brownfield bugs → andie-jr.
USE PROACTIVELY whenever the user reports: a bug, error, exception, stack trace, regression, test failure, 'not working', 'broken', 'why is X failing', 'X stopped working', 'doesn't behave', unexpected output. Brownfield debug assistant. Max 2 rounds, max 3 roles, returns problem · root cause · fix · why · audit note · commit suggestion. Do NOT use for greenfield design — that goes to andie.
USE PROACTIVELY whenever the user asks for: planning, design, architecture decision, tradeoff analysis, comparing approaches, strategy, system design, refactor scope, deciding what to build, or any non-trivial request needing clarification. Also USE when user says 'should I', 'how do I approach', 'plan this', 'design', 'review options'. Compact plan-first orchestration. Routes work, runs triad (Functional/Technical/Data), HITL gated, OODA loop. Hands off plans, never implements. Brownfield bugs → andie-jr.
Tool and product registry for Andie pre-flight. Maps problem types to tool options with tradeoffs. Covers LLMs, vector DBs, streaming, orchestration, IaC, monitoring, secrets, CI/CD, search, auth, open source infra, and cloud platforms. Load when a tool selection decision is in scope.
Tool and product registry for Andie pre-flight. Maps problem types to tool options with tradeoffs. Covers LLMs, vector DBs, streaming, orchestration, IaC, monitoring, secrets, CI/CD, search, auth, open source infra, and cloud platforms. Load when a tool selection decision is in scope.
| name | raven-registry-register |
| description | Use to register a project in the Raven registry so it gets included in future raven-registry-sync updates. Run from inside the project directory, or pass the path explicitly. Also supports listing all registered projects and removing stale entries. |
| allowed-tools | Bash |
Registers a project in the Raven registry (~/.raven/registry.json), enabling
/raven-registry-sync to keep it updated automatically.
Registry: ~/.raven/registry.json (backed up to giggsoinc/raven-registry)
/raven-registry-register → register current directory
/raven-registry-register --path /abs/path → register a specific project
/raven-registry-register --list → list all registered projects
/raven-registry-register --remove NAME → remove a project from registry
Locate raven-core
RAVEN_CORE=~/projects/raven-core
REGISTER_SCRIPT="$RAVEN_CORE/registry/raven-register.py"
If not found → STOP with: "raven-core not found. Check ~/projects/raven-core"
Determine target path
--path was provided → use that pathRun registration:
python3 "$REGISTER_SCRIPT" --path "$TARGET_PATH"
Show result — expected output:
✅ Registered: my-service
path: /Users/you/projects/my-service
remote: https://github.com/yourorg/my-service.git
version: unknown (no .raven/raven_version found — run /raven-registry-sync)
scripts: ✅
mcp: ✅
skills: raven-core, raven-security, andie
After registering, suggest running /raven-registry-sync --project NAME
to immediately stamp the project with the current version.
python3 "$REGISTER_SCRIPT" --list
Output shows all registered projects with installed vs current version and sync status:
Raven Registry — 3 project(s) [current: v2.8.0]
Name Installed Status Remote
────────────────────────────────────────────────────────────────────────────
my-project 2.8.0 ✅ current https://github.com/...
my-service unknown ⚠️ stale (unknown→2.8.0) local only
Dev-Claude-Arch 2.7.0 ⚠️ stale (2.7.0→2.8.0) local only
After listing, if stale projects found → suggest: "Run /raven-registry-sync --all to update them."
python3 "$REGISTER_SCRIPT" --remove NAME
Confirm with user before removing:
Remove 'my-service' from registry?
Path: /Users/you/projects/my-service
This does NOT delete the project or its Raven files — only the registry entry.
Confirm? [y/N]:
| Field | How detected |
|---|---|
name | Directory name |
path | Absolute path |
remote | git remote get-url origin |
installed_version | .raven/raven_version (or "unknown") |
components.scripts | .claude/scripts/ exists |
components.mcp | .claude/mcp/ exists |
components.skills | Skill directories under .claude/skills/ |
The project appears in ~/.raven/registry.json and the giggsoinc/raven-registry
GitHub backup. It will be included in all future /raven-registry-sync runs.
To immediately sync the new project to current version:
/raven-registry-sync --project NAME
Raven Registry v1.0 — raven-core/registry/raven-register.py