Analyze codebase graphs to identify class responsibilities and ownership.
npx skills add https://github.com/BarrettLowe/dotfiles --skill orient-barrettlowe
Please help me install this Agent Skill. Skill: orient Source: https://github.com/BarrettLowe/dotfiles/tree/main/claude/skills/orient Command: npx skills add https://github.com/BarrettLowe/dotfiles --skill orient-barrettlowe
Orient Barrett to complex code structures without reading them line by line, enhancing his understanding and enabling quicker comprehension through interactive exploration.
/orient src/parser/
High-intent search queries and answers about installing and using this skill.
To understand a new codebase without reading it line by line, use graph-based visualizations to explore code architecture and pinpoint class responsibilities through an interactive learning process.
Codebase exploration using graph-based analysis is a technique that maps code structure to assist in understanding code architecture, pinpointing class responsibilities and ensuring claims are evidence-backed and confidence-assessed.
To pinpoint class ownership for a specific behavior in a large codebase, use an interactive process that prompts you to predict component ownership, enhancing retention through active codebase exploration.
Yes, interactive codebase exploration works for analyzing modified code modules by utilizing graph-based visualizations to quickly learn which part of the code owns a specific behavior or feature after system modifications.
Yes, you need the graphify dependency to perform code ownership analysis, as it provides the structured analysis of a codebase's graph required to assist in understanding code architecture and pinpointing ownership.
The limitation of AI-assisted learning for codebase exploration is that every claim regarding code architecture and ownership must be evidence-backed and confidence-assessed, requiring structured graph analysis rather than unverified assumptions.
JeromyJSmithGenerate a codebase knowledge graph introduction with communities, hotspots, and dependency paths.
notqueRuns five Roast personas to identify evidence-backed issues in docs, code, or architecture with file:line citations.
mkrueger12Read project session context from .sessions/index.md.
icyzhIndex source code repositories into a knowledge graph with interactive web visualization.
