「codebase-analysis」の検索結果

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.

日本語の概要は準備中です。原文の説明を表示しています。

Findings-driven targeted code review. Understands the patch via patch-explainer and surrounding code via codebase-analysis, then consults a catalog of bug patterns (~11 categories under references/categories/). Picks only categories whose diff-signals match the patch and items whose "look for" hints match actual code shapes, groups them by review focus (function/file/feature), and spawns parallel subagents — each with a tight scope and selective checklist. Use for medium-to-large patches (50-1000 LOC) as a focused alternative to whole-patch ensemble or whole-file deep review. Triggers on: "review this patch/diff/change", "find bugs in this change", "scoped review", "what could go wrong here", "review using findings", or proactive PR review.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。