'codebase-analysis' 검색 결과

Review medium to large code changes using checks selected for the actual patch. Analyze the change and surrounding code, assign focused reviews by function, file, or feature, and combine findings with locations, confidence levels, and supporting evidence.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing patches of roughly 50 to 1,000 lines
• Checking risks specific to a changed feature
• Reviewing changes alongside callers and related implementations

Analyze a codebase to create project-specific AGENTS.md instructions and supporting rule files. Detect the package manager and relevant conventions, preview proposed changes, or update existing guidance when the project’s tools change.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create agent instructions tailored to an existing project
• Generate a minimal AGENTS.md file
• Refresh instructions after changing development tools

Generate project-specific AGENTS.md and companion rules by analyzing a codebase. Supports full, minimal, update, and dry-run modes with package-manager detection, monorepos, backups, managed blocks, confidence scoring, and command validation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use for architecture review, dependency graphs, coupling analysis, or circular dependency detection. Establishes project module namespaces and traces imports plus Claude plugin hook, skill, script, PEP 723, and MCP boundaries. Emits partitioned Mermaid graphs with cycle, coupling, and ownership signals; verifies contract and consequence before assigning severity. Registers diagrams as codebase-analysis artifacts.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Register a plan artifact via the MCP backlog server. Use when you produce a document or report that downstream agents or worktree-isolated environments need to retrieve — feature-context, codebase-analysis, architect, T0-baseline, TN-verification, or research artifacts. Triggers include "store an artifact", "register a plan artifact", "write a report to the backlog", "upload artifact content".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Produce a structured codebase analysis report with architecture overview, critical files, patterns, and actionable recommendations. Use when asked to "analyze codebase", "explore codebase", "understand this codebase", "map the codebase", "give me an overview of this project", "what does this codebase do", "codebase report", "project analysis", "audit this codebase", or "how is this project structured".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Produce a structured codebase analysis report with architecture overview, critical files, patterns, and actionable recommendations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze codebases using a graph database instead of reading source files. Use when understanding code architecture, finding functions or call patterns, tracing data flow, checking dependencies, or answering "where is X used?" questions. Grafema builds a queryable code graph from static analysis — prefer querying the graph over reading files manually.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a project has no docs/ directory or needs initial documentation generated from codebase analysis. Triggers on "init docs", "create documentation", "generate docs", "docs init", or when docs/ is empty. Do NOT use for updating existing docs (use mk:document-release).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate project-specific AGENTS.md and companion rules by analyzing a codebase. Supports full, minimal, update, and dry-run modes with package-manager detection, monorepos, backups, managed blocks, confidence scoring, and command validation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.