Skip to main content
command CX Codex

instinct-import — Claude Code slash command: import instincts

instinct-import pulls instincts from a file or URL, checks them against the ones you already have, and files the keepers with a note of where they came from.

MIT ★ 880 updated 2026-09-03

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/instinct-import.md
Open on GitHub

What instinct-import does

/instinct-import drops a set of instincts into ~/.claude/homunculus/instincts/inherited/. The file can sit on disk or behind a URL. Sources include a teammate's export, a community bundle, a backup from an older machine, or a repository analysis from Skill Creator.

Underneath it runs python3 ~/.claude/skills/continuous-learning-v2/scripts/instinct-cli.py import <file-or-url>. Before anything is written the command parses the file, compares entries with your local set and prints a summary split into new, duplicate and conflicting. Higher confidence wins a duplicate, and observation counts get combined.

Flags: --dry-run previews the import, --force pushes past conflicts, --merge-strategy <higher|local|import> sets the duplicate rule, --min-confidence <n> drops weaker entries. None of it runs without the continuous-learning-v2 skill installed, because the CLI script lives inside it. Imported entries are stamped source: "inherited" along with the file they arrived in.

What it helps with

  • carry instincts over from an old machine
  • load a teammate's exported instincts
  • preview an import before it touches the store
  • cut weak entries with a confidence threshold
  • pull instincts from a Skill Creator repo analysis

Example prompts for the agent

  • Import the instincts in team-instincts.yaml and show me what gets added or skipped
  • Run /instinct-import https://github.com/org/repo/instincts.yaml with --dry-run first
  • Grab instincts from the acme/webapp repo analysis using --from-skill-creator

How to install instinct-import

Manually: put the files in place

.claude/commands/instinct-import.md

Call it with /instinct-import. For all projects use ~/.claude/commands/

Questions about instinct-import

How do I install instinct-import in Claude Code?

Copy .claude/commands/instinct-import.md into your project. The command then appears as /instinct-import.

What does instinct-import do?

It reads an instinct file or a link to one, validates the format, compares entries against your local set and saves the new ones under ~/.claude/homunculus/instincts/inherited/ with their origin recorded.

What happens if an imported instinct contradicts a local one?

By default it is skipped and both entries get flagged for manual review. Passing --force imports it anyway.

Source text

instinct-import.md · MIT
---
name: instinct-import
description: Import instincts from teammates, Skill Creator, or other sources
command: /instinct-import
implementation: python3 ~/.claude/skills/continuous-learning-v2/scripts/instinct-cli.py import <file>
---

# Instinct Import Command

## Implementation

```bash
python3 ~/.claude/skills/continuous-learning-v2/scripts/instinct-cli.py import <file-or-url> [--dry-run] [--force] [--min-confidence 0.7]
```

Import instincts from:
- Teammates' exports
- Skill Creator (repo analysis)
- Community collections
- Previous machine backups

## Usage

```
/instinct-import team-instincts.yaml
/instinct-import https://github.com/org/repo/instincts.yaml
/instinct-import --from-skill-creator acme/webapp
```

## What to Do

1. Fetch the instinct file (local path or URL)
2. Parse and validate the format
3. Check for duplicates with existing instincts
4. Merge or add new instincts
5. Save to `~/.claude/homunculus/instincts/inherited/`

## Import Process

```
📥 Importing instincts from: team-instincts.yaml
================================================

Found 12 instincts to import.

Analyzing conflicts...

## New Instincts (8)
These will be added:
  ✓ use-zod-validation (confidence: 0.7)
  ✓ prefer-named-exports (confidence: 0.65)
  ✓ test-async-functions (confidence: 0.8)
  ...

## Duplicate Instincts (3)
Already have similar instincts:
  ⚠️ prefer-functional-style
     Local: 0.8 confidence, 12 observations
     Import: 0.7 confidence
     → Keep local (higher confidence)

  ⚠️ test-first-workflow
     Local: 0.75 confidence
     Import: 0.9 confidence
     → Update to import (higher confidence)

## Conflicting Instincts (1)
These contradict local instincts:
  ❌ use-classes-for-services
     Conflicts with: avoid-classes
     → Skip (requires manual resolution)

---
Import 8 new, update 1, skip 3?
```

## Merge Strategies

### For Duplicates
When importing an instinct that matches an existing one:
- **Higher confidence wins**: Keep the one with higher confidence
- **Merge evidence**: Combine observation counts
- **Update timestamp**: Mark as recently validated

### For Conflicts
When importing an instinct that contradicts an existing one:
- **Skip by default**: Don't import conflicting instincts
- **Flag for review**: Mark both as needing attention
- **Manual resolution**: User decides which to keep

## Source Tracking

Imported instincts are marked with:
```yaml
source: "inherited"
imported_from: "team-instincts.yaml"
imported_at: "2025-01-22T10:30:00Z"
original_source: "session-observation"  # or "repo-analysis"
```

## Skill Creator Integration

When importing from Skill Creator:

```
/instinct-import --from-skill-creator acme/webapp
```

This fetches instincts generated from repo analysis:
- Source: `repo-analysis`
- Higher initial confidence (0.7+)
- Linked to source repository

## Flags

- `--dry-run`: Preview without importing
- `--force`: Import even if conflicts exist
- `--merge-strategy <higher|local|import>`: How to handle duplicates
- `--from-skill-creator <owner/repo>`: Import from Skill Creator analysis
- `--min-confidence <n>`: Only import instincts above threshold

## Output

After import:
```
✅ Import complete!

Added: 8 instincts
Updated: 1 instinct
Skipped: 3 instincts (2 duplicates, 1 conflict)

New instincts saved to: ~/.claude/homunculus/instincts/inherited/

Run /instinct-status to see all instincts.
```

© sangrokjung · MIT · sangrokjung/claude-forge

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

From the same set44

The whole set →
eval This command defines eval criteria, runs checks, and builds reports. Use it to track a feature’s capabilities and catch regressions against a baseline. CX Codex +1 ★ 880repo stars refactor-cleaner refactor-cleaner — a subagent that hunts down code nobody calls: unused files, exports and npm packages. Each hit gets a reference search before anything is deleted. CX Codex ★ 880repo stars task-grade-routing task-grade-routing sets documentation and review lane obligations for task sizes S, M, L, and XL based on workflow classification. CX Codex +1 ★ 880repo stars frontend-code-review The frontend-code-review skill checks frontend files against a checklist and formats findings in a fixed review structure. Use it for pending changes or specific files you name. CX Codex +1 ★ 880repo stars database-reviewer database-reviewer — a Claude Code subagent for reviewing SQL migrations, schema types, and RLS policies in PostgreSQL and Supabase projects. It spots N+1 queries and runs EXPLAIN ANALYZE. CX Codex ★ 880repo stars observer observer — a background subagent that mines session observations for repeating patterns and saves each one as a short instinct rule with a confidence score. CX Codex ★ 880repo stars verify-agent verify-agent runs a fresh-context validation pipeline in Claude Code. It executes typecheck, lint, build, and test steps while safely auto-fixing trivial errors. CX Codex ★ 880repo stars evolve The evolve command turns related instincts into commands, skills, or agents. Use it when repeated patterns in your Claude Code work need a clearer structure. CX Codex +1 ★ 880repo stars

Project sponsors

Companies that keep this analytics open