agentifind-init（Agent 查找初始化）

Agentifind Init

Set up AI-powered codebase indexing for better code navigation.

What This Does

1. Runs npx agentifind init --skip-conventions to generate:

- index.json - Symbol graph (functions, classes, references) - test-map.json - Source file → test file mappings - entrypoints.json - API handlers, CLI commands, main functions - boundaries.md - Dependency impact analysis

1. Uses your intelligence to generate conventions.md by analyzing the actual codebase

Instructions

Step 1: Run the indexer

Execute this command in the repo root:

npx agentifind init --skip-conventions

Wait for it to complete. This creates the .agent/ folder with the structural analysis.

Step 2: Generate conventions.md

Now use your intelligence to analyze the codebase and document its coding conventions.

Read 10-15 representative files across different parts of the codebase:

1. Look for files in these categories:

- Core business logic (services, models, handlers) - Tests (to understand testing patterns) - Configuration files (to understand tooling) - Entry points (main.py, index.ts, cmd/main.go)

1. Analyze these aspects:

- Error handling: How are errors created, propagated, and logged? - Logging: What library? What format? What levels? - Testing: What framework? How are mocks used? Fixture patterns? - Naming: snake_case vs camelCase? File naming patterns? - File organization: How is code structured into directories? - Configuration: Environment variables? Config files? Patterns?

1. Write the findings to .agent/conventions.md using this format:

# Repository Conventions

*Auto-generated on [DATE]*

---

## 1. Error Handling

[Document patterns found]

## 2. Logging

[Document patterns found]

## 3. Testing

[Document patterns found]

## 4. Naming Conventions

[Document patterns found]

## 5. File Organization

[Document patterns found]

## 6. Configuration

[Document patterns found]

Step 3: Verify setup

After completion, the .agent/ folder should contain:

• index.json (largest file - symbol graph)
• test-map.json
• entrypoints.json
• boundaries.md
• conventions.md (you just created this)

Step 4: Inform the user

Tell the user:

Agentifind setup complete! Restart your coding agent to enable the MCP tools. You now have access to: - find_callers - Find all callers of a function - trace_path - Trace call paths between functions - get_tests_for - Find tests for a file - get_conventions - Query coding conventions - get_boundaries - Check module boundaries

Usage Notes

• Run this once per repository
• Re-run if you add significant new code or change project structure
• The MCP server (agentifind serve) is auto-configured in .mcp.json