using-glean-code

Included with Lifetime

$97 forever

Search and analyze internal source code across the user's organization's repositories. Use when the user asks how something is implemented, where the code for a system lives, who has been working on a codebase, or wants to find similar patterns across teams — i.e., questions that need visibility beyond the local working directory.

General

What this skill does


# Using Glean for Code Exploration

Glean indexes source code across the user's 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

## 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`](../../../../glean-core/skills/using-glean/reference/code-search.md) in the `glean-core` plugin. That's 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`](../../../../glean-core/skills/using-glean/reference/vetting.md) and prefer 3 high-quality matches over 10 unfiltered ones.

## 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 commands

- `/glean-code:codebase-context <system>` — structured architecture rundown for an unfamiliar system
- `/glean-code:similar-code <pattern>` — find similar implementations
- `/glean-code:find-examples <api>` — usage examples
- `/glean-code:code-owners <component>` — maintainers and contributors
- `/glean-code:plan-prep <task>` — the workflow described in [reference/plan-prep.md](reference/plan-prep.md)

Files: 3

Size: 8.9 KB

Complexity: 30/100

Category: General

Source: https://github.com/gleanwork/claude-plugins/tree/main/plugins/glean-code/skills/using-glean-code

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts