codebase-context
Gather architectural context about an internal system from code and documentation across the organization — use when asked to understand a system's architecture, find its repos, or get an overview before working on it.
Install
git clone https://github.com/gleanwork/claude-plugins /tmp/claude-plugins && ln -s /tmp/claude-plugins/plugins/glean/skills/codebase-context ~/.claude/skills/codebase-context
From README
Codebase Context Gather comprehensive architectural context about an internal system by searching code and documentation across the organization. Determine the system name from the user's request. If not specified, ask before proceeding. Core Principles Breadth before depth: Find all relevant pieces before diving deep Docs + code: Both tell important parts of the story Be skeptical: Not every search result is relevant context Freshness matters: Stale docs can mislead Process Phase 1: Find the Code Search for the system's codebase across all repositories: Look for: Main entry points and core modules API definitions (REST, gRPC, GraphQL) Key data structures and models Phase 2: Find the Documentation Search for architecture and design docs: Phase 3: Identify Key Contributors Find who's actively working on this system: Cross-reference with employeesearch for contact info.
More from this repo
catch-up
Catch up on what you missed while away — meetings, decisions, action items, mentions, and important threads from a...
code-owners
Identify who owns, maintains, or has expertise in a specific code area — use when asked who to talk to about a system,...
dev-docs-guide
Used to search the public Glean developer documentation for API, SDK, MCP, authentication, indexing, and integration...
