using-glean-code
/using-glean-code
Przeszukuje wewnętrzny kod firmy w repozytoriach: jak coś działa, gdzie leży kod systemu i jak robią to inne zespoły.
- Autor
- gleanwork ↗
- Repozytorium
- claude-plugins ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 29.09.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 3
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 29.09.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Przeszukuje wewnętrzny kod firmy w repozytoriach: jak coś działa, gdzie leży kod systemu i jak robią to inne zespoły.
Oryginalny opis (EN)
Search and analyze internal source code across the organization's repositories — use when asked how something is implemented, where the code for a system lives, who has been working on a codebase, or to find similar patterns across teams. Trigger phrases include how is X implemented, where is the code for, find the implementation of, what repos contain, who wrote the code for, how do other teams handle, find similar code to, examples of using, prior art for. Do not use for code in the current working directory (prefer local Grep/Glob), for design docs (use the using-glean skill's search refere
Jak działa
- When to reach for this
- The tool you'll mostly use
- Vetting
- Key differentiator
- Tool selection
- Output expectations
- Related skills
Podgląd SKILL.md
--- name: using-glean-code description: Search and analyze internal source code across the organization's repositories — use when asked how something is implemented, where the code for a system lives, who has been working on a codebase, or to find similar patterns across teams. Trigger phrases include how is X implemented, where is the code for, find the implementation of, what repos contain, who wrote the code for, how do other teams handle, find similar code to, examples of using, prior art for. Do not use for code in the current working directory (prefer local Grep/Glob), for design docs (use the using-glean skill's search reference), or for finding people without code context (use the using-glean skill's employee-search reference). --- # Using Glean for Code Exploration Glean indexes source code across the organization's connected repositories. Local tools (`Grep`, `Glob`, `Read`) see only the current repo; this skill is for everything else. ## When to reach for this - **Finding the system** — "Where does our payments code live?" - **Finding the patterns** — "How do other teams handle rate limiting?" - **Finding the people** — combining code authorship with `employee_search` reveals real owners (not just titled ones) - **Prior art before designing** — see [reference/plan-prep.md](reference/plan-prep.md) for the research-before-plan workflow - **Cross-repo exploration** — understanding systems, mapping breadth, finding contributors across the organization ## The tool you'll mostly use This skill drives the `code_search` MCP tool. For full param shape, inline filter syntax, and pitfalls (quoting names, the `app:` filter not applying, recency caveats), read [`../using-glean/reference/code-search.md`](../using-glean/reference/code-search.md). That is the canonical reference; this skill carries the *workflow* on top. For this skill's own workflow patterns, see: - [reference/exploration.md](reference/exploration.md) — exploring an unfamiliar system across repos: what to search for, what to filter, what to present - [reference/plan-prep.md](reference/plan-prep.md) — gathering enterprise context before entering plan mode for architectural / strategic work ## Vetting Not every match is worth surfacing. Code in `legacy/`, `deprecated/`, `archive/`, abandoned repos, or files with extensive `TODO/FIXME` comments will mislead the user. Apply the criteria in [`../using-glean/reference/vetting.md`](../using-glean/reference/vetting.md) and prefer 3 high-quality matches over 10 unfiltered ones. **Quality test** - Is this good code to reference? - GOOD: Clean, tested, actively maintained - ACCEPTABLE: Works but has caveats - POOR: Hacky, deprecated, abandoned **Recency test** - Is this code maintained? - ACTIVE: Commits in past 3 months - SLOWING: 3–12 months since last commit - STALE: 12+ months — likely outdated patterns **Relevance test** - Does this actually answer the question? - RELEVANT: Directly addresses what was asked - RELATED: Similar but different context - TANGENTIAL: Keyword match only Filter out: code in `/deprecated/`, `/old/`, `/legacy/` paths; abandoned repositories; prototype/experimental code; code with extensive TODO/FIXME comments. Quality over quantity — 3 good examples beat 10 mediocre ones. ## Key differentiator Local tools (grep, glob) search only the current repo. Glean searches across all repositories in the organization. This is powerful for: - Finding examples: "How do other teams handle authentication?" - Understanding systems: "What repos touch the billing service?" - Finding owners: "Who's been active in the payments codebase?" ## Tool selection | User intent | Glean tool | |-------------|------------| | Find code by content, pattern, or file | `code_search` | | Find related design docs or specs | `search` | | Identify code owners/contributors | `code_search` + `employee_search` | | Read full file content | `read_document` | ## Output expectations When presenting code findings: 1. **Cite each file with its full URL** so the user can open it directly 2. **Note last-update date** when a result depends on currency (active patterns vs. archaeological digs) 3. **Group by repo** when results span many repos — it shows the user the shape of the answer 4. **Flag drift** when implementations disagree across teams — don't pretend consensus exists if it doesn't ## Related skills - `codebase-context` — structured architecture rundown for an unfamiliar system - `similar-code` — find similar implementations - `find-examples` — usage examples for an internal API or library - `code-owners` — maintainers and contributors - `plan-prep` — the workflow described in [reference/plan-prep.md](reference/plan-prep.md)
Pliki w paczce (3)
- SKILL.md 5 KB
- reference/exploration.md 3 KB
- reference/plan-prep.md 3 KB
Wersje
W bazie nie ma innych skilli o nazwie using-glean-code.
Identyczna treść występuje jeszcze w 1 innych folderach na GitHubie. Tu pokazujemy jedną, najlepiej ocenioną kopię.
Migawka bazy z 13.11.2026 · wersja paczki 04f17438332b (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100dev-docs-guide
Przeszukuje publiczną dokumentację deweloperską Glean pod kątem API, SDK, MCP, uwierzytelniania, indeksowania i integracji, gdy ktoś buduje rozwiązanie na Glean. - 100using-glean
Odpowiada na pytania z dokumentów firmowych, wiki, polityk, RFC, kalendarza i maili przez Glean MCP, gdy odpowiedź jest w systemach firmy. - 100glean-cli
Opisuje użycie CLI glean do dostępu do wiedzy i dokumentów firmy w Glean: wyszukiwanie w Confluence, Slacku i plikach Google Drive. - 90connector-push
Pisze logikę wysyłania danych do Glean dla konektorów Indexing SDK: mapowanie dokumentów, tożsamości i grup. - 100connector-builder
Buduje konektory Glean Indexing SDK na podstawie dokumentacji systemu źródłowego: planuje, generuje, waliduje i ocenia własny konektor. - 100glean-webhooks
Odbiera i weryfikuje webhooki wyzwalaczy Glean z podpisami Standard Webhooks, w tym obsługę sekretu podpisu.