메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | codebase-context |
| description | 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. |
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.
Search for the system's codebase across all repositories:
code_search "[system] main OR core updated:past_month"
code_search "[system] service handler"
Look for:
Search for architecture and design docs:
search "[system] architecture OR design doc"
search "[system] RFC OR proposal"
search "[system] runbook OR playbook"
Find who's actively working on this system:
code_search "[system] owner:* updated:past_month"
Cross-reference with employee_search for contact info.
For each piece of content, evaluate:
| Test | ✅ Include | ⚠️ Note | ❌ Reject |
|---|---|---|---|
| Relevance | Core component, directly relevant | Mentions system but not central | Keyword coincidence |
| Currency | <6 months, matches code | 6-12 months | 12+ months with no activity |
| Authority | Approved RFC, design doc, official runbook | Team wiki, notes, drafts | Outdated proposals, abandoned work |
| Doc/Code consistency | Docs reflect current state | Note discrepancy, prefer code | Doc significantly wrong — warn user |
Repository Health:
# Codebase Context: [System Name]
## Freshness Check
| Component | Last Updated | Status |
|-----------|--------------|--------|
| Main repo | [date] | Active / Slowing / Stale |
| Design doc | [date] | Current / Aging / Outdated |
## Overview
[1-2 paragraph summary synthesized from current docs — note age of sources]
## Key Repositories
| Repository | Purpose | Last Active | Status |
|------------|---------|-------------|--------|
| [repo] | [what it does] | [date] | Active / Stale |
## Architecture Highlights
[Only include if from recent/authoritative sources]
- **API Layer**: [description] (source: [doc], updated [date])
- **Data Model**: [description]
- **Key Dependencies**: [list]
## Documentation (Vetted)
### Current & Authoritative
| Doc | Type | Updated | Summary |
|-----|------|---------|---------|
| [Title] | RFC | [date] | [summary] |
### Use With Caution (Aging)
| Doc | Type | Updated | Caveat |
|-----|------|---------|--------|
| [Title] | Design doc | [date] | May not reflect current implementation |
## Key Contributors
| Name | Role | Last Active | Contact |
|------|------|-------------|---------|
| [Name] | [Title] | [date] | [email] |
## Related Systems
- **Upstream**: [systems that call this one]
- **Downstream**: [systems this one calls]
## Warnings
- [ ] [Any concerns about the system's state]
# Codebase Context: [System Name]
## Limited Context Available
Found limited authoritative information about this system.
**What was found:** [code/docs summary]
**Gaps:** No recent design documentation, no clear architectural overview
**Suggested next steps:**
1. Check with [suggested team/person]
2. Explore the code directly: [suggested entry points]
Search the public Glean developer documentation for API, SDK, MCP, authentication, indexing, and integration details. Use when the user is building with Glean rather than searching internal company knowledge — trigger phrases include Glean API, Glean SDK, integrate with Glean, indexing API, Glean Python or JavaScript SDK, and how to authenticate with Glean. Don't use it for internal company knowledge, which the using-glean skill covers.
Catch up on what you missed while away — meetings, decisions, action items, mentions, and important threads from a defined time window. Trigger phrases include "what did I miss", "catch me up", "I was out", "I'm back from PTO", "summarize while I was away", "what happened last week while I was off", "I just got back", "fill me in on what I missed".
Identify who owns, maintains, or has expertise in a specific code area — use when asked who to talk to about a system, who to request a code review from, or who has been actively working in a codebase area.
Help the user connect a Glean MCP server so the Glean skills have tools to call — use when setting up Glean for the first time, adding another Glean server, checking whether Glean is connected, or troubleshooting missing Glean tools. Trigger phrases include "set up Glean", "connect Glean", "configure Glean MCP", "add a Glean server", "is Glean connected", "check Glean status", "Glean isn't working", "no Glean tools", "the Glean tools aren't showing up", "I installed the Glean plugin but nothing happens". Don't use it for actual enterprise queries once connected (use the using-glean skill); this skill only sets up and verifies the connection.
Find usage examples of an API, library, or code pattern across internal repositories — use when looking for how other teams use an internal API, library, or pattern before implementing something new.
Find subject matter experts on a topic, technology, or internal system by combining real expertise signals (code contributions, document authorship, and meeting or discussion activity) rather than relying on job titles. Use this whenever the user wants to know who to ask about something — phrasings such as who knows about, who is the expert on, the go-to person for, who has worked on, who can I ask about, or subject matter expert for. Use it even when the user does not say the word expert but clearly needs a person with deep, demonstrated knowledge of an area. Do not use it for plain directory lookups (an email address, manager, or org placement with no expertise angle), which is a simple employee lookup.