team-init

Team Init — Onboard a New Team Member

Help a developer who just cloned a repo that already has .omniscitus/ set up. Ensures the plugin is installed, git identity is configured for attribution, and optionally generates a CLAUDE.md block so future team members get auto-guided.

When to Use

• User types /team-init
• User says "onboard", "팀 초기화", "omniscitus setup"
• You detect .omniscitus/ exists but plugin hooks aren't firing

Instructions

Pre-check: Already Initialized?

Run a quick check:

ls -d .omniscitus/blueprints/ 2>/dev/null && git config user.name 2>/dev/null

If blueprints/ exists AND git user.name is set AND the plugin is installed:

✅ omniscitus is already set up for this project.

  👤 Identity: {git user.name}
  📁 Blueprints: {count of .yaml files} files

  Nothing to do. If you're having issues, try restarting Claude Code.

Stop here. Do NOT re-run setup.

Step 1: Check Current State

Run these checks:

# 1. Does .omniscitus/ exist?
ls -d .omniscitus/ 2>/dev/null

# 2. Does blueprints/ directory exist?
ls -d .omniscitus/blueprints/ 2>/dev/null

# 3. Is git user.name configured?
git config user.name

# 4. Check if omniscitus plugin is installed
claude plugins list 2>/dev/null | grep omniscitus

Step 2: Guide Installation (if needed)

If the omniscitus plugin is not installed:

📦 This project uses omniscitus for codebase tracking.

Install it (run these inside Claude Code):
  /plugin marketplace add DanialDaeHyunNam/omniscitus
  /plugin install omniscitus@omniscitus

After installing, restart Claude Code for hooks to activate.

Step 3: Verify Git Identity

If git config user.name is empty:

⚠️ Git user.name is not set. Omniscitus uses it to attribute changes to you.

Set it:
  git config user.name "Your Name"
  git config user.email "[email protected]"

This is how your edits show up in blueprints (e.g., source: claude:YourName).

Step 4: Verify Hooks

Check that PostToolUse hooks are active by examining the plugin state. If hooks aren't firing, suggest: