Review Changes
Review code changes using detected modifications and their effects on dependent code.
These skills help an agent learn an unfamiliar codebase before editing it. They cover structural code search, dependency and call graphs, change impact analysis and packing a repo into context.
23 skillsReview code changes using detected modifications and their effects on dependent code.
Compare design documents and READMEs with the current codebase.
Answer project questions using the existing knowledge graph and relevant source files.
Turn a code search request into an ast-grep pattern or rule, test it against an example, and search the project.
Explain Git diffs or pull requests, affected components and potential change risks.
Build and incrementally update the dependency graph used by code-review-graph.
Build or incrementally update a codebase knowledge graph with architecture and dependency relationships.
Use a repository knowledge graph to locate relevant code and investigate reported issues.
Pack local or remote repositories with Repomix, then inspect structure, patterns, and token usage.
Produce a ranked repository audit covering bugs, risky untested code, slow paths and code bloat.
Trace real triggers, call chains, payloads and state changes into compact ASCII flow diagrams.
Use Trail Code's graft index to inspect repository structure, relevant context and change impact.
Refresh a local repository mirror and search across authorized public and private repositories with ripgrep.
Analyze a repository’s structure, documentation, dependencies and contribution patterns.
Turn code and documents into a persistent knowledge graph for architecture questions and exploration.
Use ast-grep for structural code search and compact source outlines.
Explore a codebase with tree-sitter search, outlines, and selective symbol expansion instead of loading every file.
Map file and directory structure, imports, exports and direct members with ast-grep outline.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Plan refactoring with dependency relationships and change impact analysis.
Explore repository structure, symbols, and dependencies through the code review knowledge graph.
Generate an onboarding guide that introduces a project using its knowledge graph.
Explain a specific file, function or module with graph context and source evidence.
Use ast-grep or graph skills to answer specific questions, impact analysis before a risky change, and repo packing when you need the whole project in context.